Now Gump generates it's xdocs using an object tree structure. Watching
the
python memory grow from 20M (after loading all XML) to 136M (during
generating these pages) it has some sort of leak (actual or effective)
ouch! Maybe it would pay off to use pipelining (you know, SAX, stuff)
We should probably use a template engine. I'm sure there's a python
equivalent for something like velocity (or smarty).
First, I like the dynamic 'tree of nodes' based approach to writing
HTML/XML, rather than template -- in the main because of pleasant
experiences with the Perl modules for
First, I like the dynamic 'tree of nodes' based approach to writing
HTML/XML, rather than template
I like merging the concepts. Once you've built the tree, flatten the
part of it that will make up the page, and feed that to the template
engine. Even if you don't use a template engine,
