[Catalyst-dev] RfC: Extending Catalyst POD

[Ash Berlin]

Robert 'phaylon' Sedlacek wrote:
> Good evening fellow codeslappers,
> 
> since Catalyst::Manual::WritingPlugins is way (way!) outdated and even 
> contains some bad practices (I wrote it at 5.33 time with very little 
> actual Catalyst understanding) I wrote a successor named "Extending 
> Catalyst." As you can surely guess, it would be great if -dev could 
> review it before it goes public.
> 
> You can find the whole beast at
> 
>   <http://474.at/lab/ExtendingCatalyst.pod>
> 
> And here, for convenience, the outline:
> 
>   NAME
>   DESCRIPTION
>   BEST PRACTICES
>     Quick Checklist
>     Namespaces
>     Can it be a simple module?
>     Inheritance and overriding methods
>     Tests and documentation
>     The context object *
>   CONFIGURATION
>     Attributes
>     Creating custom accessors
>     Component configuration
>   IMPLEMENTATION **
>     Action classes
>     Component base classes
>     Controllers
>     Models and Views ***
>     Plugins *4
>     Factory components with COMPONENT() *5
>   SEE ALSO
>   AUTHOR
>   LICENSE AND COPYRIGHT
> 
> Footnotes:
>  *   ACCEPT_CONTEXT stuff and model/app bondage warnings.
>  **  Sorted by 'smallest scope first.'
>  *** Details on what a View should do.
>  *4  Yes, it contains a metaphorical 'You don't want this.'
>  *5  mst: Please make sure I got this one right.
> 
> I would very much appreciate any comments on this matter as a whole and 
> the document specifically. I hope I got all the "its" vs. "it's" this time.
> 
> Thanks again,
> phaylon
> 

The following para:

If the functionality isn't even tied to the application or Catalyst at
all and you want to release it to the CPAN


seems unfinished and not needed...