Mailing-List: contact general-help@gump.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Gump code and data" <general@gump.apache.org>
Message-ID: <01c201c412ac$13ea8cf0$a322160a@sybase.com>
From: "Adam Jack" <ajack@TrySybase.com>
To: <general@gump.apache.org>
References: <4062BFA5.1030202@antbuild.com>
 <01d901c4127b$aa113bb0$9901a8c0@sybase.com>
 <023101c4127d$74533a80$9901a8c0@sybase.com>
 <016101c412a5$1a1bcd70$a322160a@sybase.com> <c3vf0e$hej$1@sea.gmane.org>
Subject: Generating HTML (was Gump Threashing/Spinning)
Date: Thu, 25 Mar 2004 13:59:29 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


> 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 this in the past. That said, even
though there are some huge fields here (build output logs) maybe a template
mechanism is enough for the simple structure (results tables, lists, etc.)
that we have. We have huge pages, with options missing (or not) based off
content. I'm not sure any template could cope with that, but I am open
minded to it.

Second, I didn't realize that Python DOM had nice serialization mechanism.
Maybe I should've used that from the start.

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):

Fixing this area is clearly important, and I'd appreciate all insights...

regards,

Adam


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org