Something
Emporium

Update

Users of IE will immediately notice that the site looks a little better here and there. It's still much more pretty in Firefox, but for all those who are too lazy to switch that should be pleasing.

You'll also notice the menu to the left has changed – it no longer does that annoying thing where it wouldn't contract until the whole page was loaded and the javascript could run. In keeping with the general theme of the changes, it looks awesome.

But I saved the best 'till last. Click that comment button to the right. You know you want to. Yep, it's a lovely javascript tree structure that makes groking the whole thread/subthread thing just oh-so-easy – you can expand and contract threads by clicking the plus () or minus (). And if you've got javascript disabled it should still degrade nicely.

Did I mention it's easy to use? When you want to reply to a comment, click the paper and pen (). This will cause your comment to appear where the icon was. So click where you want to post. Of course, there will be those seasoned SE members out there who want to create subthreads. If you're very sure that's what you want to do, click the grayed out pen (). If you're not sure what does what holding your mouse over an icon should give you a hint.

As a general rule of thumb you should reply when you want to continue a conversation and start a subthread only when your comments are no longer relevant to the current thread of conversation. So, when you're rebutting you should probably use a general reply, not a subthread. Previously, creating a subthread tended to give people the advantage of being further up the page – they could seem to be interjecting into previous conversations almost. Now this advantage is offset by the fact that you'll be inward a layer and therefore less visible.

The new sleak comment interface meant I couldn't use a combo box for comment moderation. The moderation system is now bipolar – it's either plus or minus (those with sharp eyes will notice it's minus (−) not hyphen-minus (-) – I am awesome). Anyway, this introduced a new problem because there can't be a single form for the entire page. To prevent you from having to load the page for every moderation, the comments now use some simple AJAX to send the request to the server everytime you click a link. The upshot is that (for the next while at least) clicking a moderation link does have an effect, it's just not visible until the next time you visit the page, or until you hit refresh. Also note that it's the first of your clicks that has an effect; clicking the minus link after clicking plus will be disregarded at the server.

The bipolar moderating system meant a review of the karma system. It's now much easier to understand. I works like this: for every minus rating you lose 1 karma, for every plus rating you gain on karma. There are no other rules to understand. I couldn't bring myself to get rid of (mainly Funky's) existing moderations, so if you rated someone greater than zero it counts as a plus, less than zero as a minus. Also, karma has been anti-decimated (it is now a tenth of it's previous value).

Finally (although this list of changes is not exhaustive), the lameness filter on comments has been changed. This means you don't have to worry about long words. Also; and this is my personal favourite; it means that urls in comments are automatically converted to links.

So, that's that. Welcome to 4.30.

...disassembles my despair
It never took me anywhere
It never once bought me a drink
Dominic

Comments

This right here is a subthread post. You can only create subthreads on items that don't already have subthreads – see that just makes sense!
Dominic
A sub-thread of a sub-thread.
Dominic
A sub-thread of a sub-thread of a sub-thread...?
funkymunky
Well, if you insist.
Dominic
I (sub) insist.
funkymunky
I'd appreciate your thoughts and comments on the new interface. Subthread this comment somebody.
Dominic
I can't seem to make the entire comment tree display for previous articles... e.g. "First-years listen up". Where'd it go?
robbie
Nice dashes you have there.

It's nice. The only problem I have is a personal thing which probably is fine with everyone else: I just like to be able to see what everyone has written without clicking little plus signs everywhere. Don't mind me though.

trav
aymar
I added those expand and contract links especially for you. It's still a single click to see everything, but it's better than hunting down the little icons.
Dominic
Oh yeah, and there's what robbie said too. Even clicking all the plus signs in sight doesn't show me everything!

trav
aymar
The comments are still there, they're just not being displayed.

I did the first upload of this change last night at about midnight. It didn't work. The problem, quite frankly, is PHP4 – it doesn't pass by reference unless you specifically tell it too, and even then the whole thing is dodgy. If you know what that means, you'll know why I'm frustrated. So, I changed the whole thing from objects to arrays – took till 4 – but it's still only recursing one level which means something is still f--ked up.

I'm having another go at it tonight.
Dominic
So now I've got them displaying, but the order is still messed up. Oh well - in some ways this order is kinda cool, if confusing. You'll have to put up with that for now.
Dominic
Voila! Comment order is (I think) fixed.
Dominic
I'm liking the tree view for the comments, but I am having a little trouble reading the comments, it's a little confusing - maybe if each comment was differentiated a little more from the comment before and after then it would be easier to read.
funkymunky
Oh, believe me, I've tried. But, of course, you can't add margins to inline elements, and if you make them block elements then IE has a spaz.
Dominic
How about a line across the top of each comment, from where the comment starts, right over to the right side of the screen.

Or, can you put each comment in it's own slightly grey box, from the top of the comment down to the line above the user's name.
funkymunky
Check the link on AJAX: you forgot to put "<a href="http://">http://</a>" in there.
robbie
Any chance you could get the comments to stay "open" as you had them when you write a comment...

I don't know if that made sense, so I'll try again...

So you go down and painstakingly click loads of +'s to get comments to open, then you post a comment and then it's back to square one and playing the + clicking game again.

Won't be fun if there are, say 20 or 30 comments...

Incidentally as an IE user, no, it looks pretty bad at the moment, unless you appreciate the artistic merit of the huge area of whitespace where the news should be.
funkymunky
Try unmaximising the window - seemed to work for me.
Justin
It's a polar bear in a snowstorm. Geez.

And I actually made a real effort not to use Firefox when developing this &ndash; there's no complex javascript or box model trickery to get W3C code to work with IE. Instead, I got it working in IE and then back-developed for firefox. If you can see whitespace in IE then I'm quite lost, because I'm typing this in IE right now and it looks fine at whatever window size I use.

There is a way to make it remember your tree layout, but it would involve cookies and it's not implemented upstream yet so I'm happy to wait. There's always the expand all button.
Dominic
So, basically, for the layout issue you're going to have to be a whole lot more specific to get it fixed. Like, even to the point of hunting down what's doing it. I've looked at the site in three different installations of IE with no problems.

For reference, I'm using 6.0.2900.2180.xpsp_sp2_gdr.050301-1519, whatever that means. You're using XP SP2 right?
Dominic
When I look at this news item page, the news item itself "Update..." starts where the shoutbox ends.
funkymunky
Yeah ok, unmaximising the window does appear to *work around* the problem....
funkymunky
I'm using the same build of IE Dom, and I'm having the same problem as funkymunky - v 6.0.2900.2180.xpsp_sp2_gdr.050301-1519

I'm betting the problem is that both me and funkymunky are using LCD's -> and running in the native resolution 1280x1024. The aspect ratio is different from 1024x768, and IE probably renders differently.
Justin
I'm looking at this right now in IE on an LCD monitor in 1280 by 1024. As usual, nothing wrong until you resize the window.