See, I'd rather have lots of plugins than have a monolithic CGI::App
core that I only use parts of. Of course, I'm in the camp that says
HTML::Template should not be a requirement for C::A and that the
load_tmpl function should be an abstract method that is implemented by a
plugin. I wouldn't have a problem if the default plugin was
C::A::P::HTML-Template (or whatever it'd be called) but am advocating
stripping down C::A more than building it up :).
I think we are still in the same camp.
All these functions can still be implemented as separate modules, but I think the more popular plugins should ship with the core package.
That will take a little more disk space, but since the plugins are not loaded unless
you want them to, that should be a fair deal for not having to download all those mini-modules.
And of course, I am all for moving the HTML::Template features of the current core application
into a C:A:P:HtmlTemplate plugin which for compatibility's sake would be loaded by default
(but could optionally be disabled).
The nice thing about this approach with Perl's subroutine export mechanism for plugins is that
it is quite transparent for the user where the code really comes from.
Thilo
--------------------------------------------------------------------- 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]
