Sounds good ... did someone previously mention that an
initial hack is available? :)
Bill
--- Michael Peters <[EMAIL PROTECTED]> wrote:
> Answering for Cees (hope you don't mind :)
>
> Bill Catlan wrote:
> > Cees,
> >
> > So a plugin author would
> >
> > use base CGI::Application::Plugin;
> >
> > in their plugin, and that would be it?
>
> And they would have to add the CGIAppPluginMethod
> attribute
> to the methods they want the user to have access to.
> Just
> like this:
>
> sub Mode1 : CGIAppPluginMethod
> {
> [whatever]
> }
>
>
> > Separately, how would a CGI::Application app
> author
> > get access to the plugin methods? What makes the
> > Plugin available to the CGI::Application app -
> > CGI:Application (though you said no mod to C::A
> code)
> > or else the C::A app itself?
>
> In the .pm file you're writing for you app you would
>
> use 'SomePlugin';
>
> and the methods the author gave to you would
> automatically
> be there for you to use as if they belonged to the
> class
> you're currently writing.
>
> HTH
>
> --
> Michael Peters
> Developer
> Plus Three, LP
>
>
---------------------------------------------------------------------
> 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]
>
>
---------------------------------------------------------------------
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]
