[Catalyst] External plugins

[Christopher H. Laco]

I'll see your non-CC reply, and raise you one non-CCed reply. :-)

-=Chris

Christopher H. Laco wrote:
> Ovid wrote:
>> --- "Christopher H. Laco" <claco at chrislaco.com> wrote:
>>
>>> Hmmm, why not split the problem into its two parts?
>>>
>>> package Catalyst::Plugin::In::Another::Namespace;
>>> use base qw/Some::Plugin::In::Another::Namespace/;
>>>
>>> sub a place to override things just in case in needed to be {
>>>
>>> };
>> Because we don't want to create a lib/Catalyst/Plugin directory in our
>> apps just to have packages with one line of code (and further
>> complicating the inheritance tree).  While there are other tricks I can
>> use to avoid even that extra directory tree, simply fixing
>> setup_plugins() is much cleaner.
>>
>> Cheers,
>> Ovid
>>
> 
> Using M::P::Fast, based on M::P, I would suspect there is some level of
> tweaking that can be done to add another namespace to the mix of ones to
> search... but I guess that depends on how silly Fast is..
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 187 bytes
Desc: OpenPGP digital signature
Url : http://lists.rawmode.org/pipermail/catalyst/attachments/20060214/a0e5332b/signature.pgp