John Hinsley <[EMAIL PROTECTED]> is widely believed to have written:

> I'm not absolutely sure what you want. All this referesh/cacheing
> behaviour seems to depend very much on the browser you use (Netscape
> works best): both IE and Konqueror seem to like being refreshed!
Yup, I tried it on adifferent browser and it behaves as I would hope;
very annoying.  I thought the whole idea of html was that it should
be platform neutral...

> 
> As for the ++++ stuff, I've not yet arrived at a way of doing threading
> in the way you suggest, but "+_" does give a nice "flat" arrangement of
> comments.
True, though the large number of textareas that can get easily generated
worries me a bit; it's both UI bad and resource bad. Here's a faintly
plausible idea:-
Make the comments display in a threaded tree (like you see on slashdot
etc) BUT have a radio button by each one. To comment on an item, hit the
radio button and then type the comment in the _single_ text area.
Hmm, might work for moderate numbers of comments, but bad for long
lists.

I think I still prefer that idea of having a buttony thing by each entry
that you hit and go to another page (can you make it open an new
window automatically?) with the comment (maybe a few in the same
branch?) and a text area.

What's wrong with the current edit approach you ask? Well, it gets
really cumbersome very quickly once you get past a couple of dozen
lines. Also, I need to make a reasonably threaded chat/commentary page
for students to discuss a topic without leaving too much opportunity for
dipsticks to delete the lot. Which is one of the reasons I'd like to not
show the edit button at all for anyone except the teacher/admin.

tim

-- 
Tim Rowledge, [EMAIL PROTECTED], http://sumeru.stanford.edu/tim
Computers...  are not designed, as we are, for ambiguity.  - Thomas

Reply via email to