On Fri, Apr 09, 2004 at 05:04:54PM +0200, Emanuele Zeppieri wrote:
But then your considerations should apply also to the *existing* load_tmpl() method, since it is a method conceived exactly as an "interface to different contructors/methods of other commonly used modules", as you said.
I don't think you'll get any argument about this issue from folks who don't use HTML::Template for their template engine. It's legacy code that constantly comes into discussions about how to integrate other template engines with C::A.
I use both H::T & TT and have completely bypassed load_tmpl() by writing my own process() method which does all kinds of things I need. IMHO, since C::App is a framework it shouldn't even have built-in support for any template system. But, as you and others have mentioned, it _should_ provide an easy way to use whatever template system you prefer.
If generalized template support is added, I think it should be in a new method solely because load_tmpl() has such historical significance. Personally I really like process(), but then I'm biased. :-)
Drew -- ---------------------------------------------------------------- Drew Taylor * Web development & consulting Email: [EMAIL PROTECTED] * Site implementation & hosting Web : www.drewtaylor.com * perl/mod_perl/DBI/mysql/postgres ----------------------------------------------------------------
--------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
