[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cgiapp
Subject:    [cgiapp]  Re: Re: CGI::App and HTML::Template subclasses
From:       "Viacheslav Sheveliov" <slavash () aha ! ru>
Date:       2006-12-13 17:34:26
Message-ID: elpdj7$ndj$1 () sea ! gmane ! org
[Download RAW message or body]

"Rhesa Rozendaal" <perl@rhesa.com> wrote:

> I would vote not doing this in CGI::Application itself. I'd rather see 
> C::A and H::T completely decoupled.

This is good thing - it will make C:A more "generalized". But since they are 
copuled...

> A more sensible place would be in CGI::Application::Plugin::AnyTemplate, 
> but I could also see the use for a CAP::HtmlTemplate-ish plugin.
>
> Something like
>
>   use CGI::Application::Plugin::HtmlTemplateX 'HTML::Template::Compiled';
>
> could export load_tmpl, using the supplied H::T derivative.

OK I'll stop on this (alredy wrote). IMHO specifying module name at compile 
time isn't good idea - object variable is more flexible way.

wbr
Viacheslav Sheveliov 




---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/cgiapp@lists.erlbaum.net/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: cgiapp-unsubscribe@lists.erlbaum.net
For additional commands, e-mail: cgiapp-help@lists.erlbaum.net

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic