[Catalyst] External plugins

[apv]

That's great. That looks like exactly what I want (too/instead) for a 
design
question I was about to ask: how to parse the resulting X?HTML of the 
page
*once* no matter how many "plugins" wanted access to the token stream.

Thanks!
-Ashley

On Tuesday, February 14, 2006, at 07:23  PM, Sebastian Riedel wrote:
>> I'm envisioning a package that might have a couple hundred
>> optional plugins (contributed by various people so some would overlap
>> or clash) where each user would probably only want a handful or a
>> couple dozen turned on. Certainly never all of them.
>>
>> I'm working on a Catalyst blog (no offense to the very nice Agave 
>> project,
>> I just wanted to do it myself since I have for the last 5 years) and 
>> I am
>> thinking a big pre-installed plugin list that users could activate 
>> easily
>> without messing with another install process.
>>
>> I haven't got to this part of the project yet though so it's all 
>> speculation,
>> wish-list-ing.
>
> What you want is a whole different level than the Catalyst plugins.
> Thats exactly what i wrote Catalyst::Plugin::Pluggable for. ;)
>
>
> --
> sebastian
>
>
> _______________________________________________
> Catalyst mailing list
> Catalyst at lists.rawmode.org
> http://lists.rawmode.org/mailman/listinfo/catalyst
>
>