[Catalyst] What is the point of all these "wrapper modules" ?

[Matt S Trout]

On Thu, Nov 03, 2005 at 05:30:36PM +0100, Dami Laurent (PJ) wrote:
> Hi all,
> 
> I love the main core of Catalyst, but I don't understand why there are
> so many "wrapper modules" (Plugins, Views, Models). CPAN already has
> many, and new wrappers come out every day. Most of them do almost
> nothing except forward method calls to other CPAN modules outside of
> Catalyst. As far as I understand, the only advantage of glueing things
> in that way is that the modules will be autoloaded by Catalyst, and you
> don't need to "use Some::External::Module" from the Catalyst code.
> 
> Am I missing something ?

Yes, the fact that the catalyst wrappers are true Catalyst components and
as such can take their config from the main application config; this allows
things like e.g. the DSN for db-backed apps to be stored in either the
app run script or in a config.yml (see trunk/examples/ServerDB for e.g.).

-- 
     Matt S Trout       Specialists in Perl consulting, web development, and
  Technical Director    UNIX/Linux systems architecture and automation. Mail
Shadowcat Systems Ltd.  mst (at) shadowcatsystems.co.uk for more information

 + Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ +