<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Maybe there should be a list of modules that should be preferred<br>
for certain purposes when writing Catalyst extensions? Of course<br>
we don't to *prescribe* any of them, since the main selling point<br>
of Catalyst is that cares more about being glue and about having<br>
an opinion. So if you want to glue something big like Template<br>
Toolkit or Mason into Catalyst you might have to accept modules<br>
which duplicate functionality that other dependencies already<br>
offer. But it might be good to say "for tasks where you don't<br>
already have a really strong opinion and where it's up to you,<br>
please strongly consider using the following modules". (The<br>
Catalyst Canon maybe, if you will.)<br>
</blockquote><div><br>I think this is a great idea - I know the flexibility that Catalyst offers is a big selling point, however<br>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.<br>
<br>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.<br><br>I guess there's:<br><br> <a href="http://dev.catalystframework.org/wiki/recommended_plugins">http://dev.catalystframework.org/wiki/recommended_plugins</a><br>
<br>or something like:<br>
<br> <a href="http://search.cpan.org/~perigrin/Task-Kensho-0.0.4/lib/Task/Kensho.pm">http://search.cpan.org/~perigrin/Task-Kensho-0.0.4/lib/Task/Kensho.pm</a><br><br><br>Cheers,<br><br>Ian<br><br><br><br><br></div></div>
<br>
-- <br>Ian Sillitoe<br>CATH Team -- <a href="http://cathdb.info" target="_blank">http://cathdb.info</a><br><br>