Thanks Cees. That all looks great. I have a thought
on the conceptual level though. Please note, I am
half thinking out loud here - just interested in
others' thoughts.
Should C::A::Plugin perhaps put the plugin methods
into C::A space, and not the C::A app module? After
all, the plugin is a /C::A/ plugin, not a 'MyApp'
plugin.
Then, when the app module does its normal 'use base
C::A;', it will get the "registered" plugins. C::A
would simply provide a class method
'register_plugins', or grab them from a config file /
ENV variable.
As a case in point for why this could be beneficial,
the 'jedit' project eventually makes certain plugins
"standard", allowing the base appplication - the base
platform, if you will - to evolve through community
contributions.
Bill
--- Cees Hek <suppressed> wrote:
> Bill Catlan wrote:
> > Sounds good ... did someone previously mention
> that an
> > initial hack is available? :)
>
>
http://cees.crtconsulting.ca/perl/modules/CGI-Application-Plugin-0.01.tar.gz
>
> Or if you just want to look at the code:
>
>
http://cees.crtconsulting.ca/perl/modules/CGI-Application-Plugin-0.01/lib/CGI/Application/Plugin.pm
>
> And here is a link to the original message I sent
> out regarding this
> module and the discussion that followed:
>
>
http://www.mail-archive.com/suppressed/msg01888.html
>
> Cheers,
>
> Cees
>
---------------------------------------------------------------------
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.