Andrew Kornak wrote:
Personally, I would like any book on Catalyst, even if it was only a
single chapter in a larger MVC treatment. I bought Jonathan's book and
contrary to another poster's opinion found it quite useful.

-Andrew

+1

Rod
--

On Mon, 2008-04-28 at 10:03 -0500, Mitch Jackson wrote:
I'd like to see a walkthrough of good MVC separation in practice.
This took me a while to get through my stubborn skull, and would be
good material to a new Catalyst developer.  My first few Cat apps
suffered heavily from having too much logic in the controllers.

The example could look something like this:
- Put this logic into a model method and why
- Build a .t file to test the model method ( possibly include
deploying and testing against a mock database )
- Build a .pl file, outside the catalyst web app that uses the method
- Finally, use the method from your catalyst action

This not only suggests good practice to the reader, but shows them how
to do it properly and gives them hands-on with the benefits of the
approach.

/Mitchell K. Jackson

On Sat, Apr 26, 2008 at 7:01 PM, Ian Sillitoe <[EMAIL PROTECTED]> wrote:
So as I said - I contacted O'Reilly to request info/submit interest in a
Catalyst Cookbook/Best Practices. I've been in contact with a chap called
Andy Oram who seems to be O'Reilly's Perl Guy (FWIW he also seems a nice,
but very busy, guy). I was waiting for him to give me the nod before posting
the following thread to the mailing list...


----


I just had a moment to reply. You can post my reply to the mailing list--I
do appreciate that you asked first. Results of my asking around are
discouraging. I will try to do some more research next week, but this is a
busy time for me. (I have only 6 days at home during the whole month of
April.)

 Andy

 ----- Original Message -----
 From: "Ian Sillitoe" <[EMAIL PROTECTED]>
 To: "Andy Oram" <[EMAIL PROTECTED]>
 Sent: Thursday, April 17, 2008 4:28:34 AM (GMT-0500) America/New_York
 Subject: Re: Catalyst Cookbook/Best Practices

 Andy,

 Thanks for getting back to me. It would obviously be nice to see
 O'Reilly give Catalyst the full "Best Practices" treatment, however as
 you say, a more simple "Catalyst Cookbook/Hacks" book of code snippets
 would presumably be much easier to produce/edit and therefore more
 likely to happen. The Catalyst POD docs are already pretty good and
 will undoubtably continue to improve. However most Catalyst
 developers, i.e. the people that would actually fork out money (or get
 their employers to fork out money) to buy the book, would probably be
 very happy just to get the interesting snippets in lots of different
 case scenarios.

 Also, I was going to post the reply you gave on the Catalyst mailing
 list - but it feels a bit rude without at least asking you first - any
 objections?

 Lots of people would be really interested in any further developements
 so if you had a chance to update me when you hear anything, I would be
 really grateful.

 Regards,

 Ian


 ---------- Forwarded message ----------
 From: Andy Oram <[EMAIL PROTECTED]>
 Date: Wed, Apr 16, 2008 at 11:46 PM
 Subject: Catalyst Cookbook/Best Practices
 To: [EMAIL PROTECTED]


 I just had a moment to reply to your request for a Catalyst Cookbook,
 which was forwarded to me because I edit most of our Perl books now.

  I appreciate your contacting us, and I'll ask the Stonehenge trainers
 as well as the many O'Reilly employees who are heavily involved in
 Perl development. Unfortunately, it's very hard to make money on books
 about Web frameworks. Even the Rails market, which used to be very
 good, is weakening.

  Basically, the success of the open source movement makes book
 publishing difficult. There are lots of competing frameworks and
 languages. There are core groups of excited users for each one, but
 rarely do they add up to a market for a book.

  But we'll see what our Perl contacts say. The idea of bypassing the
 tutorial and writing a cookbook is appealing.





On Fri, Apr 4, 2008 at 12:46 PM, Ian Sillitoe <[EMAIL PROTECTED]>
wrote:


On Thu, Apr 3, 2008 at 10:36 PM, Pierre Moret <[EMAIL PROTECTED]> wrote:

Jon wrote:

[...] Or like others have suggested, a cookbook with a large variety
of useful examples showing "best practices" for different situations.
That's exactly what I would like to see. I got the first book (thanks!)
and would buy such a cookbook immediately.

Seconded... and, like one of the previous posters, I've also added my
tuppence to (proposals@) O'Reilly (.com) suggesting they get on the case.


_______________________________________________
 List: Catalyst@lists.scsys.co.uk
 Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
 Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
 Dev site: http://dev.catalyst.perl.org/


_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/


_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/


_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/

Reply via email to