[cgiapp] Re: Comments requested

[Mark Stosberg <suppressed>]

On 2003-10-20, Christopher Hicks <suppressed> wrote:
> On Mon, 20 Oct 2003, Mark Stosberg wrote:
>> I'm also not sure I fully understand your proposal yet. Can you offer a
>> code sample as example, or you are still working at the conceptual,
>> theoretical level with the idea?  
>
> The concept is that if I call a plug-in in a template that the cgiapp
> plug-in manager will semiautomagically find that plug-in, load it, and
> include it's output as desired.  The use case I feel likes keeps getting
> ignored is "a nonprogrammer edits a template to add a plug-in".  There's
> no reason for this person to need to know Perl at all.  There's no reason
> they should have to edit the Perl to add simple new functionality.  So the
> only code would be (from a TT2 perspective):
>
> [%- PLUGIN FINIcounter prefs="roman=want" params="id=demo,title=API Demo" -%]

Chris,

Thanks for the follow up. I use H::T and not TT2, but I understand
that TT2 supports a lot of plugins on it's own. I'm curious what the
difference in syntax and effort is to use a TT2 plug-in through it's
standard syntax, versus having CGI::App help with that.

My personal interest in plugins is different-- I'm happy with just
exposing the user to the H::T syntax, and handling making plug-ins work
in the code. 

Still, other parts of your design ideas resonate with me. I like the
idea of plugins that could work at the server or application level, and
be accessible through the code.  However, for that case I think the
standard methods for "using" Perl modules could work. 


Still, maybe if you build it, "they will come". :)

	Mark	

-- 
http://mark.stosberg.com/ 


---------------------------------------------------------------------
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