Chuck Esterbrook <[EMAIL PROTECTED]> wrote: > >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?
Well, Cheetah writes everything to transactions. But you can get a string back if you want, which is constructed by the DummyTransaction. It acts like capture. So you might do: #set $bodyHolder = $body header stuff... $body footer stuff Ian _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
