#musicbrainz

I've added the first 30 or so already, and done the tracklists for 110 or so - still 60 of mostly opera to dig through

I've got, hmm, maybe 500 lines now to add, but the posted list is at http://www.musicbrainz.org/CSGStandard/Mozart

the opera and the beyond-obscure stuff keeps slowing me down

stuff like "Tantum ergo for 4 Voices & Orchestra in D major, K. Anh C 3.05/(K3) Anh 186e/197 (possibly spurious)

that's a lot of ARs then too. All those conductors, orchestras, instrument players, ...

yup

going to take forever to get this set entered fully

in terms of CSG though, lol... I took the easy way... Made up a complicated spreadsheet - fill in the blanks, let it put the text and punctuation in the right places :P

hence being able to copy out just the titles, let it convert them to "Die Zauberflöte, K. 620: Act II, Scene XXII - XXIII. Dialogue "Tamino! Tamino! Willst Du mich denn gänzlich verlassen?" (Papageno)"

moin leute!

good early morning to you ruaok :)

time of day! :)

still avoiding catching on fire?

well, I'm in the clear up here.

the nearest fire is about 70 miles away and its a small one.

that's good

mum seems to be out of danger in SD.

so, can I send another tech supper help issue to you?

picard's tags don't show in itunes....

meh... I'll take Buffalo snow over living with earthquakes and fires in Cali ever again :D

sure, send any you like :)

do you wanna be on the support@ alias?

lol

that way you get copies of all the incoming mails.

I guess I can do that, if you'd like

all we do is first come, first serve Reply all.

ok

zout is on the list as am i.

ok.

usual addy?

sure

its only a handful mails per week...

cool.

What's a few more MB-related emails :)

lol

MClemo - any idea what "zweiter akt" means?

second act

I'd be glad to help with german questions, in return for you MB help. :)

thanks... wonder why they switched from (act 2) to (zweiter akt) on two lines here *shrug*

lol... be careful what you wish for, I've still got 57 CDs of Mozart operas... :D

got it

sweet. thanks.

and other mail forwarded.

thought about buying a 180 disc box set, that would be some work, too

lol, well, when I finally finish this one, there's still a good bit of the Phillips 180 CD Mozart set unentered...

btw ruaok - did modbot just recently run for the first time in like a week?

modbot runs hourly.

the emptyartists script had a bug in it until yesterday.

ah, that would explain it

and then I ran it yesterday and promptly pissed you off. :)

haha

next schema release I want to add "last modified" timestamps to everything.

and then we can say, an artist that isn't referenced by anything and hasn't changed in a week can go.

fair?

just wondered why I saw a burst of artist removes... worried that someone moved track artists on one of the annoyingly complicated VA releases I added last week

nah, just fixing bugs.

and yes, a week sounds more than fair

seems to work pretty well

now I'd go with MVC like rails.

though I'm thinking there's something screwy somewhere in how the css is being handled, under some unknown set of circumstances...

there seem to be some odd cases I can't explain.

yeah - I'm thinking of the http://www.uk.musicbrainz.org/artist/008203dd-8... case

and can we please fix the random declaration where the paragraphs run into each other?

something seems to be triggering wierdness there

Which one?

(toss an "l" on the end of that url, btw)

is that the case where we had the diff we couldnt read?

no, different one someone found yesterday evening

still waiting on voice to attach his htmls, so I can look at what might be funky

well, there is this totally unintuitive paragraph decl

oh, I know the one you mean - the css <p> modification that neither of us could figure out *why* it was there

that nonsense.

dah!

hence the edit note workaround

yeah, I'd pay good chocolate to have that be gone.

honestly, when acid gets more done with the xhtml rewrite, I'm thinking a complete css reevaluation...

between the 5 or 6 css files, there's just a LOT of "isn't this duplicating that, or fixing this cause that borked it?"

and a lot of deadwood.

yep

MBChatLogger: off

is not logging

is logging

Seems like it's kind of, each new feature has added, but the accumlated additions are starting to trigger hard to trace wierdness... hence, why, when acid's done, I'm thinking the next step, before any actual redesign, should be just to clean up the code, so it's easy to manipulate during a redesign

make it clean, make it fast, make it small

code --> html/xhtml/css, not php/perl

please, please, please.

there is soo much cruft from when things had to be that way.

yup

which can THANKFULLY now go away.

well, acid's finished the main page, and the menus. He's working on the voting pages now, to try and make them work without all the funky issues they (and the inline voting) have

tossing out the need to support IE5 makes it a lot easier too

I'd like to see the a new server release pretty soon.

before the year is out, for sure.

that's my hope

non schema change release, so the process is less constricted and things are easier.

are there any actual entire pages you want to do away with?

I know of one I think can go, might be others I'm not thinking of

since the new url structure, I can't really think of any.

artist.html needs to be redone. :)

yup

only one I can think of is http://musicbrainz.org/edit/album/add.html?arti... - specifically where artist = 0

I think we need to design the artist page very carefully.

agreed

but I'm just not sure how to go about that.

my sense is, if we can get the basic code very clean, and very fast, we can componentize artist.html

I'll gladly code the JSON backend for that.

I keep thinking of the artist page, and the associated artist releases/release/track pages as OOP components, rather than HTML pages

and that's the way to do it now.

kind of the idea I guess was intended with the default release list - but doing it so it's not an awful ugly mess this time

ohhh, I have an idea.

let's create a survery of exising web pages that present the same info.

agreed

pick a few interesting cases and present them in a wiki page or so.

though, best example of the kind of thing I've been thinking of...

for people to think about, check out and brainstorm.

you ever used the google personalized page, rather than the default google page?

igoogle?

drag and drop component selection and user desired location?

yes

feh. I don't think people will know or care too much.

I'd much rather see a simple and well thought out page.

I worked for a software company in the mid-90s where the main feature, above all else, that we needed during the app rewrite was dockable toolbars.

somehow, someone got it into their head that this was the #1 requested features from customers.

lol

(I'd still like to know how that happened)

In the end, no one used the feature.

not even us.

well, I don't know that we would need to make it customizable

not even the person who wanted it.

more thinking along the lines of making it not require any js to see the basic data, but if you have js turned on, you can do transforms - the album art view under artist release list, for example

non-js to pull the basic list of releases and such, but js pulling needed data (ajax style) as needed, rather than just dumping it all to the browser all at once

should make it easier to add new things, while keeping page loading *fast*

less server load too, theoretically, as you don't need to pull/feed quite as much data at any one time

kind of like, say, the "show AZN, discogs, wiki icons" GM script currently does for the release listing

main idea always being, though, keep it clean, keep it fast, and above all, KISS

:D

but now. PTFO.

yup

simple is hard.

natta!

natta :)