[Catalyst] Re: OT: Use the CPAN, Luke?

[Ian Sillitoe]

>
> Maybe there should be a list of modules that should be preferred
> for certain purposes when writing Catalyst extensions? Of course
> we don't to *prescribe* any of them, since the main selling point
> of Catalyst is that cares more about being glue and about having
> an opinion. So if you want to glue something big like Template
> Toolkit or Mason into Catalyst you might have to accept modules
> which duplicate functionality that other dependencies already
> offer. But it might be good to say "for tasks where you don't
> already have a really strong opinion and where it's up to you,
> please strongly consider using the following modules". (The
> Catalyst Canon maybe, if you will.)
>

I think this is a great idea - I know the flexibility that Catalyst offers
is a big selling point, however
I think lots of people new to Catalyst (or just new to a different area of
Catalyst) want to know best practices, e.g. which modules have been tried
and tested in a production environment, which modules are well accepted,
written and supported, etc.

Obviously TMTOWTDI but I'm very happy to take advice from people who have
lots of experience in the field - if you're developing systems for
production you'd be crazy not to.

I guess there's:

  http://dev.catalystframework.org/wiki/recommended_plugins

or something like:

  http://search.cpan.org/~perigrin/Task-Kensho-0.0.4/lib/Task/Kensho.pm


Cheers,

Ian





-- =

Ian Sillitoe
CATH Team -- http://cathdb.info
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.scsys.co.uk/pipermail/catalyst/attachments/20081127/200a9=
5d2/attachment.htm