To be honest, I would not mind having a slightly incompatible change to the
C::A API, that would do away with the load_tmpl and query() methods
entirely (although I do understand the dependance on the CGI module from
the headers() aspect). I would much rather have a subclass or a SuperApp
class to let me decide what templating system I wish to use (if any), My
reasoning being that the templating system used should be a local decision,
not one made by the framework.
However, not eliminating the dependence on H::T is not a huge deal with me,
since I use it anyway. In fact, if it went away, I would probably add it
back by making C::A::HT module that I would use instead. Besides, there is
a lot of existing code out there right now that uses load_tmpl and H::T,
so...
My $0.02,
Brian
--
Brian T. Wightman suppressed
Global Data Management http://pdm.cg.jci.com/
Johnson Controls, Controls Group (414) 524-4025
suppressed
om To: suppressed, suppressed
cc:
04/09/2004 10:04 Subject: RE: [cgiapp] load_tmpl() question.
AM
-----Original Message-----
From: petersm [mailto:suppressed
Sent: Friday, April 09, 2004 4:32 PM
To: Emanuele Zeppieri; suppressed
Subject: Re: [cgiapp] load_tmpl() question.
> I disagree. I think that by adding new methods to C::A
> you just clutter it up.
> [...]
OK, I agree with this on a general basis (and I can also narrow to the
load_tmpl() specific situation my previous statement about hiding
external modules use in C::A apps, which could sound too general
really).
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.
If we will implement load_tmpl_scalar_ref() somewhat out of C::A, as you
seem to suggest, we will end up in a situation where we can use the
internal load_tmpl() method when we want to load a template from a file,
while we have to resort to some external something when we want to load
a template from a text ref.
At least in this particular case, it's a little bit confusing, I
think...
> Instead of this, I think we should resume the discussion we had
> a few months back about including some sort of plugin/registry/cleanup
> functionality to C::A.
I perfectly agree, on a general basis.
--Emanuele Zeppieri.
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.