Rest assured my branch will definitly bring that – you have to have ids to attach a label to inputs (and you have to have labels!)
brianfreud
lol
aCiD2
I can't decide which page to work on next
brianfreud
hey, one thing I was fighting with yesterday... do you know how to have transparent overlapping <div>s without the top div blocking interaction with the lower divs?
I finally ended up just playing with the width so they didn't technically overlap
aCiD2
What did the divs contain?
as in, where's the interaction?
Jugdish
here's something i've never understood...when you view someone else's votes, why does it set all the vote options to their votes? if you just click "Enter votes" you'll vote exactly like them on everything O_o
Jugdish - I looked at that code a while back. It's actually coded to do just that, as it pretends you are that voter to pull up the votes list
Jugdish
weird
aCiD2
Have we got a bug filed?
Jugdish
don't think so
aCiD2
lol, that's neat (but in a bad way :P)
brianfreud
if voter_id= , it assumes it is you. if voter_id= has a value, it assumes that the voter is you (and thus loads their votes), but then looks at who you really are to see if you've actually voted
aCiD2 goes to look into making a new UserPreference
comes in handy sometimes :)
would actually be nice if you could go further, say, where voter_id=foo and voter_id-bar both voted yes or both voted no
hmmm, ok, "document.getElementsByTagName("input").filter is not a function"
oh... might help if I aimed at the iframe...
Jugdish
this whole "taxonomy" feature is going to add a lot of confusion. everytime someone says "tag" we'll have to clarify whether we mean a "tag" in the taxonomy sense or a "tag" as in "tagging my mp3 files"
brianfreud
I think we'll have to, at some point, specify exactly what each term means, so we're clear in what we're talking about
"album" for example, has at least 3 different uses in three different levels atm
Jugdish
heh
aCiD2
I always try to use the term "release"
Jugdish
the term "release" gets especially confusing when you start looking at the server code
brianfreud
hmmm, still having problems here acid...
"frames[0].document.getElementsByTagName("input").filter is not a function"
Jugdish
because what we call a "release event" is called a "release" in the server code, and what we call a "release" is called "album"
aCiD2
brianfreud: browser?
brianfreud
FF
aCiD2
version?
brianfreud
2.0.0.6
aCiD2
hmm
full line?
brianfreud
should be Gecko 1.6 compliant, right?
Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6
aCiD2
I get filter is not a function too
hmm
Jugdish has never heard of .filter, but that doesn't really mean anything :P
brianfreud
Implemented in: JavaScript 1.6 (Gecko 1.8b2 and later)
aCiD2
Seems getElementsByTagName dosen't return an actual array
getElementsByTagName returns an element collection or something
aCiD2
a "live NodeList"
Jugdish
an Element[]
aCiD2
"elements is a live NodeList of found elements in the order they appear in the tree."
Jugdish
The NodeList interface defines a read-only, ordered list (i.e., an array) of Node objects. The length property specifies how many nodes are in the list, and the item( ) method allows you to obtain the node at a specified position in the list. The elements of a NodeList are always valid Node objects: NodeLists never contain null elements.
aCiD2
Yea, but it's not actually an array, which sucks :P
guess you'll have to do a crappy procedural foreach if on it Brian :(
or convert it to an array
brianfreud tries to figure out how that would be done :P
I'd do this:
brianfreud
until this week, my javascript was in the x=y+z level... :P
aCiD2
var inputOriginal = document.getElementByTagName('input');
var inputNew = [];
for(var i = 0; i <= inputOriginal.length; i++) { if(inputNew.name.matches(/^labelname/) { inputNew.push(inputOriginal[i]); }}
I think that should work
brianfreud
I think I get i, up until the push, let me see if it works...
aCiD2
(This is why I use mootools and hate straight javascript. "Oh yea, this is ALMOST an array, buttttt you can't do this, this or this. Oh yea, and it doesn't work in these browsers UNLESS you do this and this")
push adds an item to the end of an array
so you're basically creating a new array, with only inputs that begin with "labelname" in their name attribute
brianfreud
so the result is then that inputOriginal becomes an array of objects returned from the loop?
aCiD2
inputOriginal is all the <input> fields
inputNew will be all the <input name="labelname..."> fields
brianfreud
oh, I see, you're copying the value of inputOriginal[i] into inputNew[inputNew.length++]
aCiD2
yea
brianfreud
got it
how is the matches working though? if inputNew is a new array, won't inputNew.name be null?
aCiD2
whoops, typo :P
That should be if(inputOriginal[i].name.matches
brianfreud
lol, ok
stochasticism has quit
aCiD2
hmm
aCiD2 wonders why his user preference doesn't set correctly
brianfreud
hmm, slowly getting there... inputOriginal.name has no properties... :P
aCiD2
inputOriginal[i]?
brianfreud
ah
aCiD2
that working?
brianfreud
no, it doesn't like the .matches() - trying it a little differently...
cooperaa joined the channel
hmmm "inputOriginal[i] has no properties" in for(var i = 0; i <= inputOriginal.length; i++) { if(/^labelname/.test(inputOriginal[i].name)) {
and inputOriginal.length = 32, so it definately is finding the <input>s...
was there already some discussion wether extra title information "instrumental" should be included in the track title, even if there seem to be no non-instrumental version?