[Catalyst] External plugins (continued)
Matt S Trout
dbix-class at trout.me.uk
Fri Feb 17 21:27:31 CET 2006
On Fri, Feb 17, 2006 at 11:54:58AM -0800, Ovid wrote:
> Hi all,
>
> So it sounds like there's a bit of consensus to be able to specify a
> MyApp::Plugin directory just like we have
> MyApp::(?:Controller|Model|View) directories. Until (and unless)
> someone wants to write the code for this, is the unary plus model
> acceptable?
>
> use Catalyst qw(
> DateTime
> +MyApp::Custom::Plugin::DoesTheDishes
> );
>
> Since plugin order appears to be important, "use base" isn't a good
> option and writing a "Catalyst::Plugin" wrapper just means more grunt
> work. The unary plus saves a lot of time and is fairly clean.
> However, I won't write this unless others are comfortable with it (and
> it won't conflict with the MyApp::Plugin scenario. Instead, it merely
> offers greater flexibility with minimal risk)
I dunno if people want to have a debate over exactly what name to use, but
I think in general this is a good idea.
--
Matt S Trout Offering custom development, consultancy and support
Technical Director contracts for Catalyst, DBIx::Class and BAST. Contact
Shadowcat Systems Ltd. mst (at) shadowcatsystems.co.uk for more information
+ Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ +
More information about the Catalyst
mailing list