Re: [Catalyst] Re: So, what do we want in the -next- book?

2008-04-28 Thread Ali M.
On Mon, Apr 28, 2008 at 7:29 AM, Jonathan Rockway [EMAIL PROTECTED] wrote: 2) Learn how to use Catalyst (read my book) Sorry to say this, but your book is not a good book! I cannot in good faith recommend it to anyone. Please consider believing the bad review your book got, because they are

Re: [Catalyst] Re: So, what do we want in the -next- book?

2008-04-28 Thread Jonathan Rockway
* On Mon, Apr 28 2008, Ali M. wrote: On Mon, Apr 28, 2008 at 7:29 AM, Jonathan Rockway [EMAIL PROTECTED] wrote: 2) Learn how to use Catalyst (read my book) Sorry to say this, but your book is not a good book! I cannot in good faith recommend it to anyone. Please consider believing the

Re: [Catalyst] Re: So, what do we want in the -next- book?

2008-04-28 Thread Richard Jones
Jonathan Rockway wrote: * On Mon, Apr 28 2008, Ali M. wrote: Sorry to say this, but your book is not a good book! One of the reasons we need a second book, is that because your book was so bad. People right away started asking and hoping for a second book. Now I can see why people are

Re: [Catalyst] Re: So, what do we want in the -next- book?

2008-04-27 Thread J. Shirley
On Sun, Apr 27, 2008 at 11:05 AM, Aristotle Pagaltzis [EMAIL PROTECTED] wrote: * J. Shirley [EMAIL PROTECTED] [2008-04-27 19:30]: If you want to know the internals of catalyst, do as Jonathan said and fire up a code browser and get started. Putting together a map of a mountain by

Re: [Catalyst] Re: So, what do we want in the -next- book?

2008-04-27 Thread J. Shirley
On Sun, Apr 27, 2008 at 5:19 PM, Aristotle Pagaltzis [EMAIL PROTECTED] wrote: I'm not talking about COMPONENT. I'm talking about classes with accessors for which they never set a value themselves. I don't remember specific examples since it was two or three weeks ago, but it had to do

Re: [Catalyst] Re: So, what do we want in the -next- book?

2008-04-27 Thread Ali M.
Books can be made big, I just checked my copy of Perl Cookbook and its almost 900 pages If there is a new Catalyst Book, I think the book can have the first 100 -150 or so pages explaining how catalyst work + some nice diagrams of how the pieces fit together + the much asked for how are

Re: [Catalyst] Re: So, what do we want in the -next- book?

2008-04-27 Thread Dave Rolsky
On Mon, 28 Apr 2008, Aristotle Pagaltzis wrote: I’m not talking about COMPONENT. I’m talking about classes with accessors for which they never set a value themselves. I don’t remember specific examples since it was two or three weeks ago, but it had to do with the dispatcher, and I stumbled

Re: [Catalyst] Re: So, what do we want in the -next- book?

2008-04-27 Thread Jonathan Rockway
* On Sun, Apr 27 2008, Aristotle Pagaltzis wrote: * J. Shirley [EMAIL PROTECTED] [2008-04-27 19:30]: If you want to know the internals of catalyst, do as Jonathan said and fire up a code browser and get started. Putting together a map of a mountain by examining it one pebble at a time is not

Re: [Catalyst] Re: So, what do we want in the -next- book?

2008-04-06 Thread Ali M.
Kinda opposed to popular demand, I would like the next book to be the equivilant of the camel book programming perl . I would like to know how Catalyst Work, so I can better figure things on my one, instead of the desired receipe approach of a cookbook I would like to learn the concepts behind