Tim Rowledge wrote: > > 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...
Well, it still is, but the browsers, sheesh! I did read somewhere that IE5 was actually more standards compliant that Netscape..... > > > > > 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 did have a mooch around: couldn't quite find a way of doing that, but Swiki-Formatting>>LineLormatter class renderFormatter and the stuff on the class side of IdFormatter might enable you to create your own threaded tree. > > 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?) it might be possible to do this by popping in some Javascript: presumably, if the relevant formatter can be made to parse out js, then the browser will respond appropriately. The tricky bit would be to get the Swiki to pick up the results, methinks. I wonder if you could look at the html source produced by Slashdot and get Comanche to punt out something which approximates to that? > > 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. Mmmm. Two things I'm plotting at the moment are community recipes and free ads. The structure of the Recipes one goes like this: Top has a link to RECIPIES (top will be locked by root) RECIPIES is a series of links to the recipes of various nations, something like: _ <a href="/recipes/3">*+great-britain.gif+*</a> *BRITISH* _ <a href="/recipes/8">*+greece.gif+*</a> *GREEK* _ <a href="/recipes/18">*+india.gif+*</a> *INDIAN* _ <a href="/recipes/23">*+italy.gif+*</a> *ITALIAN* __ <a href="/recipes/45">*+mexico.gif+*</a> *MEXICAN* _ <a href="/recipes/49">*+spain.gif+*</a> *SPANISH* _. (so that here the images are buttons) (this page will be locked, too) which lead to a list of recipes for that particular nation. These individual pages will be locked (if I've created them) and may be locked by whoever submits the recipe (if they wish). It's only this "middle tier", where people edit the list of national recipies which is vulnerable. (It might be possible to limit this by giving them "append only" priveledges.) In all this, there are two safeguards: you can probably locate whoever buggers up the Swiki (and either deny them access or publicly garrot them) and you can always use the changes to restore it to a working state. I wonder how often the GaTech students mess up their Swikis? (Zope has all this pretty much out of the crate, but essentially it would seem to be "just" a matter of putting the methods together, and anyway, we want something written in Squeak!) In all this, I wish there was some kind of design/developers manual for Comanche, but it's a lot of work and early days. Cheers John -- If you don't care about your data, like file systems which automagically destroy themselves and have money to burn on 3rd party tools to keep your system staggering on, Microsoft (tm) have the Operating System for you.
