August 14th, 2003


userinfo senji
2003/08/14 02:47:00
Well, I've made a start on my S2 style Grail. It's already an improvement on what I had before :).
Current Mood: [mood icon] accomplished

< | 10 glosses | comment | > )

userinfo lnr
[userpic]
2003/08/14 02:23:45
yuk yuk, S2 comments pages 5ux0r!
reply | thread )
userinfo senji
[userpic]
2003/08/14 02:25:30
Mmm, good point. I didn't think I'd turned that on...

*frob frob frob*

reply | parent | thread )
userinfo senji
[userpic]
2003/08/14 02:27:11
That better?

Actually, I think well done S2 comments pages are better than the default one. (Like Simon's for instance). But I hadn't intended to turn that on yet :.
reply | parent | thread )
userinfo lnr
[userpic]
2003/08/14 02:31:55
Yep, back to normal.

And while I like Simon's style it's not so much that it's ugly that is the problem with S2, but that it means all the comments pages are in *different* styles to each other, so even the good ones interrupt your reading and make it harder work to just skim over stuff. For me anyway.

In any day I might have most comments I'm looking at in the default style, then skip through Simon's, then Andrew's (daneel_olivaw) and ailbhe's and then back into default, in any order. And yet they're all displaying stuff which essentially has the same structure.
reply | parent | thread )
userinfo senji
[userpic]
2003/08/14 02:34:21
Hmm, yes.

I find ones like Simon's a blessing because his style has a better failure mode when the thread gets too deep.

Ones like mhw's old comments style are a pain though, because I can't read pink on purple! :)
reply | parent | thread )
userinfo simont
[userpic]
2003/08/14 03:17:36
Thanks - I spent a lot of effort on that failure mode :-)

The other failure mode I spent a lot of effort on is when one particular comment needs to be really wide (perhaps it contains <pre> text with a large minimum width requirement). The standard comments page deals with this badly - it stretches out the whole of the rest of the page so you have to scroll left and right to read everyone's comments - and the default S2 Generator comments page is if possible worse in this situation. Since I started using S2 shortly after Dan posted just such a comment in this entry, it seemed quite important to me to make sure that one was handled right...
reply | parent | thread )
userinfo simont
[userpic]
2003/08/14 03:42:46
Of course, if someone has an S2 comment style you don't like, you can always replace it with one you do like by means of adding "?s2id=<thingy>" on the end of the URL. (Mine is 11610, for what that's worth :-) See this example link.

For some reason this doesn't work on all journals - my suspicion is that any journal which isn't even eligible for S2 at all (is this still true of free accounts?) can't be told to have anything but the default comments page. But at least this trick lets you have to deal with at most two comments styles, one S2 and one original.

This comment from Brad might mean that at some point you can configure your own friends page to automatically add this suffix to all intra-LJ hrefs on it (and perhaps even recursively for pages of other people's journals rendered in your style). In fact I wouldn't be surprised if someone prepared to do some serious S2 coding could do that right now; it's quite tempting, because I agree many other people's S2 comments styles seriously suck. (Mind you, I don't think much of the default either, which is why I bothered to do my own in any case.)
reply | parent | thread )
userinfo cjwatson
[userpic]
2003/08/14 04:05:43
The only problem with yours is that for some reason it causes w3m to render all comments wider than 80 columns, so I have to keep scrolling left and right on every line to read it. This is probably a bug in w3m, but I haven't tried diving into its rendering code yet ...

reply | parent | thread )
userinfo cjwatson
[userpic]
2003/08/14 04:10:58
Oh, actually, that turns out to be a slander. What it does is causes w3m to render every comment to 79 characters wide, while the normal style causes it to render the box containing all comments to 79 characters wide. I suppose your approach is necessary to make deep nesting work sensibly, although if it weren't quite so close to the terminal width that would be nice. :-) When you scroll left or right by moving the cursor off the left or right edge of the window, it scrolls by half a screen (I think) so almost never manages to produce something readable.

However, I've now discovered the ',' and '.' keys, which scroll left and right respectively by one column, so I have a good enough workaround ...

reply | parent | thread )
userinfo simont
[userpic]
2003/08/14 04:38:00
w3m has to make an arbitrary decision about how to convert widths measured in pixels into widths measured in characters. You can fiddle with this arbitrary scaling factor using the -ppc command-line option, or the pixels_per_char setting in the config file. Mine is apparently set to 10, where the default is 8, and my S2 comments pages seem to work fine with that.

reply | parent | thread )

< | 10 glosses | comment | > )

Well, I've made a start on my S2 style Grail. It's already an… - Squaring the circle... — LiveJournal

> log in
> recent entries
> fiends
> archive
> toothywiki page
> profile
> new entry
> recent comments


> go to top