or just make it easy for nit-pickers to find and correct the cases that can't be computed
nikki
hahaha.
brianfreud
LotR: easy... loadRelease WHERE id == rnd()
luks
bah, modbot is angry again
I really should finish the collection merging patch
LotR
brianfreud: WHERE title LIKE '%in%' (or In) would do the trick for that word.. I bet the nitpickers can come up with other queries for contested words
brianfreud
oh, I'm sure
nikki
there's thousands of titles with 'The' in the middle, let alone ambiguous ones
brianfreud
I'm not aiming for perfection itself. I only think, if I'm mucking about in there anyhow, why not actually clear up an open point of vagueness in the English guideline? Right now, that guideline is vague enough, such fixers wouldn't know which way was correct to "fix" it anyhow.
it's one of those guidelines where the comments and debates are ten times longer than the guideline itself...and most never got resolved or really discussed :P
LotR
nikki: so you'd limit it by date after the first pass-through
nikki
LotR: I mean there's loads and loads and loads of stuff which has blatantly incorrect capitalisation according to our guidelines, there's plenty to do before people need to start nitpicking
LotR
nikki: I wasn't trying to say there should be 'nitpicking' done, I was saying it should be made easier for more people to have machines help them do their editing/voting jobs
LotR wanders off to cook dinner
Sargun joined the channel
MClemo has quit
brianfreud
if anyone wants to try out two scripts, and give an opinion which they like better, http://brianfreud.info/1.html and http://brianfreud.info/2.html - ignore the css, the persistant "pick a country...", etc... just a very raw demo page for each I tossed together to test each
murdos has quit
MClemo joined the channel
kinda partial to #1 myself
Muz
Err the results on #1 seem to be on crack
I prefer #2 anyway.
brianfreud
#1's using a quicksilver-type selector, #2's just doing a text-narrowing approach
murdos joined the channel
Muz
Yeah, I prefer #2 by far.
docwhat joined the channel
brianfreud
seems #1 might work better for instrument lists, #2 for country / script / etc
Muz
#2 needs to empty the text field on click too
Yeah, agreed.
nikki
#1's sorting is nuts
brianfreud
yeah, ignore all that - I just tossed a quick wrapper around a select, nothing else is done on either
nikki: #1's using a context search, quicksilver style
mudskipper joined the channel
nikki
whatever quicksilver is
Muz
It's a launcher for OS X.
brianfreud
basically an adaptive search
I think #2 for most form fields, but would you agree something like #1 for instrument list ARs? (ie, find "marimba", even if it's not the first instrument in the select item listing?)
nikki
I don't like how #1 shows every single result, making the scrollbar go nuts, the top n for what you've typed would probably make more sense, I like how #2 has them sorted properly, but I like how #1 can find, say, "East Germany" when I type "Germany"
brianfreud
like I say, it's totally uncustomized, using all defaults atm
yeah, that's what I like too about #1
#1, you get Germany and East Germany. #2, you just get Germany.
odyssey joined the channel
nikki
can you use your js to make the add release event button work inline while you're adding things like that? :P
Muz sure hopes that there are fallbacks for when JS is disabled.
brianfreud
nikki: yes, it's on my to do list for when acid2 pushes his finished code for me to work with
nikki
there will be, or I'll kick up a fuss :P
brianfreud
and muz, yes - that's what acid2 is working on now
Muz
Ah, good.
nikki
it's one thing I've been meaning to make a user js for though, adding another row of inputs is hardly something that needs to be done with another page load if js is available
but I'm lazy and never got round to it :P
brianfreud
just tossed the AR and instrument list selects on those 2 pages, if you want to try those same with other types of selects
nikki
the second page isn't working...
brianfreud
1 sec, just realized the scripts aren't activating on them, fixing real quick :)
ok, both turned on now
nikki
hmm... it'd be nice if the first one went away when I clicked on the field again... I'm so used to doing that to cancel it I was like "aaah how do I make it go away" for a minute o_O
brianfreud
#1 definitely works better for ARs
nikki
#2 still isn't working
brianfreud
no, it's working, just not working well on those 2 lists :P
all the spaces in the AR list are throwing it off (<option value="515"> Practice chanter</option>)
nikki always did hate those spaces
Muz
Such mad hax.
brianfreud introduces people to the <optgroup> tag :P
nikki
somewhere I have a script which inserts the ones I use with a name I can type
brianfreud: I'm pretty sure it was done like that because IE couldn't do anything else
but we were probably supporting IE4 or something stupid back then :P
I do like that dropdown thing more for instruments than the weird search we have at the moment
brianfreud
does anyone ever actually try to find instruments via the select, or does everyone else also use the context search to find anything in there?
nikki
dunno, I rarely use it
brianfreud
yeah. My current sense is, #1 for country, instrument list, #2 for language, script, AR list
ie, things that start with what you'd be looking for anyhow, use #2, but things that context searching really helps, use #1
nikki
I'd rather just have a mixture of the two for all of them :P
brianfreud
two totally different plugins
nikki
I don't know what options they have though
brianfreud
the real difference in how they select what to show - as I said, one's using an adaptive search, the other's just useing a narrowing-selection
docwhat has quit
I can't really see a way to combine those two behaviours as one - two totally different concepts
nikki
substring searching with sorted results
brianfreud
so it's not the substring searching that's throwing you, but the lack of alphabetization in what it then displays?
nikki
yes
brianfreud
I'll have to look into that, that might be doable.
if it is, #1 could then just work for everything.
nikki
(and I don't like that it doesn't limit how many it displays at once, like I said ;))
brianfreud
well, let me look into what I can customize in #1 (or modify in the plugin itself)
nikki
k :)
sonium has quit
ruaok joined the channel
CStan joined the channel
LotR
hmm, there was a script that will update the database to the next schema version, right? where do I find that?
brianfreud
ok, any customizing, I'll be modifying the plugin itself. For how many to list, it's just showing any that match at all. If I bump it to 80%, it narrows quickly, but not *too* quickly that it eliminates useful listings. Any three characters seems to get me to 5 to 8 items, max, even on the instrument list.
LotR: I thought it was just something like upgrash.sh in the top directory of the server code
LotR
nikki: yeah, I'm stupid. thanks :)
nikki
upgrade.sh even :P
LotR
hrm, I get this:
ERROR: duplicate key value violates unique constraint "language_pkey"
nikki
apparently you can just keep running the script and it'll eventually work fine
I didn't have a problem though, it's kinda weird
LotR
ah, does more the next time you run it, yes. thanks again
brianfreud
hmm, ok, you can set a size for a option list, which controls how many lines are always shown... but can there really be no css option for option elements to control how many rows are shown at any one time without scrolling??
mezod joined the channel
nikki
the browser normally decides how many to show at once
like opera is showing me 16
LotR
hrm. I didn't update my DBDefs.pm correctly I think. now I'm getting this error:
ERROR: duplicate key value violates unique constraint "country_isocode"
brianfreud
yes, though this is actually turning the select+option into <div> <input> </div> <div> <ul> <li>s </ul></div>
yllona joined the channel
yllona has quit
ruaok looks up
LotR has quit
nikki, what's a good max number? 10?
nikki
well, give it a try, it should be easy enough to change if it's not enough/too many
brianfreud
well, I have it limiting now, on http://brianfreud.info/1.html , but it's not going to do a scrollbar or anything, at the moment
thinking the answer's not actually in limiting how many it shows, but forcing the container div to vertically scroll instead
Muz: did you ever get chance to play with the locales?
ruaok joined the channel
CatCat
brianfreud: i don't really like either, the firstis nuts, ugly and doesnt work, the second is nice but the two last forms doesnt work
brianfreud
CatCat: how does the first not work?
CatCat
i don't understadn what to o whena tousnad unrelated things fly aroudn the page when i type "u"
and what are the buttons about?
brianfreud
I'm playing with it at the moment
but for an example, try typing "sax" into the bottom one
CatCat
seriously, to be honest, the instrument chooser is the one ting i'm happy with, exept that it doesnt do unicode
brianfreud
I broke the unicode, actually :P
CatCat
yea, i get "sho"
brianfreud
oh, the other one
CatCat
nothign happens
the country one works
brianfreud
are you on 1.html or 2.html?
luks
ruaok: `svn up cgi-bin/MusicBrainz/Server/Collection.pm` should fix modbot complaining about 'duplicate key violates unique constraint "collection_has_release_join_combined_index"'
ruaok
ohh,t ahnks.
but thats not the table its complaining about is it?