> That's > t = Template(templateDef, searchList=[orderData]) > to you, buddy. :) > > It's prob'ly possible with some work to store the precompiled > template module in the database and then exec it into a private > dictionary when you need it, but it's prob'ly easier to just > store the template definition in the databse and let it be > recompiled each time. How much does this cost? (I'm thinking of systems with about 20-50 users)
> If you're using inheritance, you need to store the base template > modules in the filesystem. Trying to extract those from the > database would be a lot of work since you'd have to override parts > of Python's import mechanism. Important point. I would try to base is only on a Servlet which includes common text funtions but divides output into chunks, so each template should pull in whatever it wants. Perhaps I would study the Python import mechanism which could make it easier to store a lot of Python Code also in the database. (Think of edit vía Web, search it, etc, much like Zope treats its Python-Scripts.) ... > At most sites, "printable page" just means omit drawing the table cells > and decorations arount the content, and perhaps substitute a few minimal > decorations instead. This can be handled by a couple #if stanzas in the > base template (if using inheritance), along with a 'print' variable in > the searchList. Then you'd only need one template for each page rather > than a pair of templates. I'm thinking of using ReportLab PDF files, because I couldn't find how to print Header and Footers in HTML for a multi-page report. Erny _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
