At 03:57 PM 11/1/2001 -0600, Ian Bicking wrote:
>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).
I do most of my form handling in awake().
> > 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.
I didn't mean to be vague. The spans are continuous. e.g. self._spans is a
list. To deliver them:
output = ''.join([span.content() for span in self._spans])
But the names of spans, make them easy to access randomly.
>In Cheetah, this actually wouldn't be a big deal, since it captures
>output fairly easily (with DummyTransaction).
Using a template doesn't seem any different than "compute first, then
output". Spans give you easy random access from your Python page programming.
BTW What's a DummyTransaction?
-Chuck
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss
