On Thu, 30 Jan 2003, Timothy Appnel wrote: > Here is the snag. I need to provide a designer > that ability to apply any one or more of a number > of filters that could occur post processing -- > lowercase, strip tags, encode xml etc. Trying to > predict and create every possible combination to > pass into the template seems rather inefficent and > an exercise in futility.
Are you sure you need to do that? I ask only because I've created quite a few web apps without needing this functionality. But, sigh, if this is what you need then HTML::Template::Expr is undoubtably what you need. Just define the filters as functions and: <tmpl_var expr="encode_xml(var)"> > my $content = $template->output(); > > return &post_filter_processing($content); That works fine. It works so well, in face that I've never been interested in trying to replace it! People use this technique to use HTML::Clean on HTML::Template output, for example. > I beleive this would reduce caching performance, correct? I don't think so. What do you mean exactly? -sam ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Html-template-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/html-template-users
