#musicbrainz

weird smiley

Probably the solution

I think it's the newlines within common-macros.tt

yup

that's what I think is the problem

yeah, webkit's doing all sorts of fun things, rendering the DOM entirely differently from any other engine

exsessive whitespace also wastes space

(and bytes)

looks like turning on the PRE_CHOMP and POST_CHOMP options in tt might be a good idea acid2 - I'm just not sure where you configure tt atm

lib/MusicBrainz/Server.pm

I'll try that

TRIM also

yay, webkit is happy now - and the webkit fixes also got rid of all that extra height and width nikki

What did you have to add to fix?

I'm just checking everything in the browsers now, then I'll push it to github - had to tweak a good bit with the DOM structure and css to fix some issues in 8 or 10 files

boiled down to unconstrained divs, in most cases

alright

i'm really lost as to how much you've done in what branches now :)

hopefully we can cover that in a few hours

I've not touched anything but the ES branch in a month

right

the bugs I just fixed were making the ES essentially overwrite the rest of the page in webkit

ok, pushed, but still one issue to fix - the sidebar links aren't actually functional for some reason, save in opera

hahha opera ++

oh, lol, no, opera just needed a reload - lol, sidebar links don't actually work in any browser now :D

is MOD_ADD_TRACK still used?

or does MOD_ADD_TRACK_KV take over?

the latter

cool

What about MAC_TO_SAC?

does MOVE_RELEASE take over from that? (and SAC_TO_MAC)

that one isn't as clear in my mind...

no worries, I'll leave them on the list

is github down?

doesn't matter if it is :P

chefkoch_AW is now known as chefkoch

Virgin just announced they're closing all their US stores

:/

wow

I thought that happened a few months ago. I know the local store here closed a while ago.

that was just the first wave.

I'm really looking forward to a

"normal" work week. but nothing about it looks normal so far. :-(

oh well. :)

He had a normal work week about 5 months ago and he wants another already!?

now that's just greedy

I have 2 albums (Foo and Bar), 2 discs in each (Foo1, Foo2, Bar1, Bar2). If Bar is a live performance of Foo, should Foo2 and Bar2 be linked? Or just Foo1 and Bar1?

Second question, if Foo1 and Foo2 are later released together on one disc (Baz), should Baz have an AR to both Foo1 and Foo2? Or just to Foo1?

back in 15!

(ran out of plugs and gotta unplug the router :P)

navap: 1st question. I'd link disc to disc, Foo1+Bar1, and Foo2+Bar2.

second question, I'm not sure. I think I'd link the CD to both of the earlier CDs.

Kerensky97: But doesn't that create a cluster of sorts, for the first question.

Because Foo1 and Foo2 are already linked together, and Bar1 and Bar2 are as well.

Hi all

I hope somebody can help me. Does anybody know the name of that song of SUPERTRAMP rock fashioned, that the videoclip is in 3D animation and it shows 2 guys (a fat and slim one) moving tvs ??

luks: any idea what modbot is complaining about?

I dont even understand the nature of the problem. :-(

ruaok: it's fixed in svn

I've sent you a mail

oh.

tahnks!

[20:28] <navap> Second question, if Foo1 and Foo2 are later released together on one disc (Baz), should Baz have an AR to both Foo1 and Foo2? Or just to Foo1? <-- both, i'd say

I didn't get that mail. :-(

catgroove: Thanks

hm

well, the fix is in svn anyway :)

:-)

ruaok: on the /bare thing - both regular and the ESI-version wikidocs broke in tt when the switch was made to wikidocs

luks: do you really think disc ids don't work the way they are? :o

nikki: I don't think they are useful

they aren't. tocs are.

if I had know this and that and this and that, when I started this project...

I'm not sure about that either, if we have track times and we allow +/- 5 second difference, we don't need exact CD TOCs

if only....

i like disc ids

I like having exact tocs... I often find exact matches when I put a cd in my drive

yes

its invaluable from classical

I can see the advantages of searching by times, but having an exact match a lot of the time is nice too :/

I should try to implement this track time index some time

many things couldnt even be found then

just to see if it could replace discid lookups

luks: you still would want exact matches sometimes, but i guess scoring by relevancy will just give the client as much accuracy as he wants