t; was using it.
>
> --john
>
> - Original Message
> From: Krzysztof Krzyzaniak <[EMAIL PROTECTED]>
> To: The elegant MVC web framework
> Sent: Wednesday, August 30, 2006 7:18:33 AM
> Subject: Re: [Catalyst] Plugins vs. Base Controllers
>
> Matt S Trout wrot
: Krzysztof Krzyzaniak <[EMAIL PROTECTED]>
To: The elegant MVC web framework
Sent: Wednesday, August 30, 2006 7:18:33 AM
Subject: Re: [Catalyst] Plugins vs. Base Controllers
Matt S Trout wrote:
[..]
> If your only argument is "I need $c" you can usually do a controller, view
Matt S Trout wrote:
[..]
> If your only argument is "I need $c" you can usually do a controller, view or
> model with an ACCEPT_CONTEXT method. Often you only actually need the app
> instance (i.e. the "MyApp" class name in 5.70) not the full request context.
Could someone point me example (som
Matt S Trout <[EMAIL PROTECTED]>
:: 08/18/2006 10:08 AM :
> John Napiorkowski wrote:
> That's how I'd do it.
>
> > On a side note if anyone has
a working useful example of ACCEPT_CONTEXT I'd be
> > glad to see it. I can
see the value of this but no matter how often I reread
> > the do
John Napiorkowski wrote:
> I've been thinking that a plugin is something that usefully hooks into the
> catalyst process, like authentication and sessioning or extends the existing
> functions, like the dumper plugin extends the log object.
Actually, the Dumper plugin is strongly disrecommended
S Trout <[EMAIL PROTECTED]>
To: The elegant MVC web framework
Sent: Friday, August 18, 2006 9:40:46 AM
Subject: Re: [Catalyst] Plugins vs. Base Controllers
Mark Blythe wrote:
> Spinning this off into a new thread.
>
>> So make it a controller base class.
>>
>> People make
Mark Blythe wrote:
> Spinning this off into a new thread.
>
>> So make it a controller base class.
>>
>> People make everything a plugin by default because it seems like a good idea
>> at the time. This has resulted in massive compatibility issues due to
>> namespace collisions.
>>
>> Don't Do It.
Spinning this off into a new thread.
> So make it a controller base class.
>
> People make everything a plugin by default because it seems like a good idea
> at the time. This has resulted in massive compatibility issues due to
> namespace collisions.
>
> Don't Do It.
I've pondered the "controlle
