Chuck Esterbrook <[EMAIL PROTECTED]> wrote: > >I could require that anything that will display an immediate status > >message should do so in awake, but that seems too difficult. I'd > >almost prefer to reorganize Page if it really is necessary. > > Why is it too difficult to do the computations in awake()?
It's just more convenient... though I probably don't do any output until after I send those messages (except in SitePage). But it's the same thing as with not demanding that cookies and headers be set before you start outputing the page -- I'm just creating a similar header-like system for my specific site. > My first thought is that you are mixing computations with display and that > is causing the problem. Of course, it's easy for me to say that with no > example on hand. Perhaps you can provide one? Mostly its when I am doing some form action, which I don't generally do in awake() -- right now I'm having FFK override writeContent, though maybe overriding awake() would work fine too (except that awake needs to call the superclass). > Thinking aloud about such a design, your page could construct a list of > Spans, each of which is mutable string-like object with a name. The sum of > these spans represents your page content. This seems a lot more complicated than the capture method. The part that seems vague about spans is that they have to be embedded in some structure (that fits them all together into one text)... it starts to become a template issue. In Cheetah, this actually wouldn't be a big deal, since it captures output fairly easily (with DummyTransaction). Ian _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
