Where a user does not specify a name space, where do the methods go - a default namespace, or the module's namespace? I think, based upon what we said earlier, it would be a default namespace - perhaps given by UNIVERSAL::moniker - or whatever.
My intial thought would be to just put them into the module's namespace wich is using the plugin. But that's my opinion. What does everyone else think?
Maybe this... (as I said above) use CGI::Application::Plugin::TT ( name => tt, override => 0);
Yes, default behavior for
use CGI::Application::Plugin::TT
being:
use CGI::Application::Plugin::TT ( name => [moniker], override => 1 );
That sounds good to me. Also, I would think that all plugins should have those defaults as well (if we decide to use UNIVERSAL::moniker default namespace).
Correct? Any ETA on when you see yourself getting to
this?
Well, I didn't want to usurp Cees's work here. Also I wanted to get more opinions (than just yours and mine ) on these last points here. Cees said he didn't think the namespace thing was and issue so I wanted to see how he thought about our more recent ideas.
If Cees doesn't mind I'll take a crack at it, but I probably won't get to it for a couple of days (maybe Wednesday?) since work is pretty compelling today and tomorrow.
By the way, I did some research on attributes, but never worked with them; I think you might want to consider having only one attribute name (eg, cgiapp_plugin) and you then define an attribuite list for each subroutine with that attribute name. Either that, or you can parameterize the attribute. I think by doing so, you can swap out the attribute list from underneath the attribute name and alter program behavior - by using differing default attribute list values, for example. Just some (half baked) thoughts. :) If this is all correct, I think it becomes trivial to flip attr list values on individual methods if we ever want to extend the API. For now, we would do it wholesale, as you suggest, setting the 'override' attr list value to whatever the 'override' param provides, or according to the rules we've discussed.
I'll have to look at the details of this, but I'm sure we can find an easy flexible way to handle it.
-- 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]
