> 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.
Originally I tried it with IF statements, but different clients wanted different report formats with different fields and different field names. It was just easier to write a new template for each of the 5 clients rather then have to think. Also I could email the cheetah to thier each clients designers for modification. The topic was a templating system, and I have had no luck implementing a cheetah based template server that I like. I tried a template pool like db pool that would take a few params and return a compiled template, but I never seemed worth the effort. Compiling a bunch of templates in the init method and then selecting it based on user params if quick and easy, but I do not think it would scale very well. Cheetah is good in the PERL way that it makes it easy to do something easy and allows you to do something complex as well. So in the PERL way my lazy solution is false lazyness and true lazyness would be the template server. Thanks, -Aaron _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
