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

[rahed]

On 4/27/08, Ali M. <tclwarrior at gmail.com> wrote:
> i completly oppose another cookbook for catalyst
>
>  catalyst need an indepth book that describe its design!
>  the first book was very much a learning by example book, which is
>  close to a cookbook
>
>  and the main complain or the bad review where that, after reading the
>  book, developers still didnt not understand how catalyst work (for
>  exampl how subroutines attributes are used)
>
>  we need a book with diagrams that exlpain the different pieces of catalyst
>
>  a cookbook maybe be easier to write, but its not what i think is needed
>  a cookbook is for people who already knows catalysts, this book trend
>  will make catalyst a very exclusive framework only used by perl
>  experts!
>
>

I would also prefer a deeper explanation to a cookbook, though the
cookbook is occasionally quite handy.
How the framework works with existing applications - mod_perl, fastcgi
(pros and cons), interfacing to web services, problems with forking.

Reading the used code is sometimes necessary but also much more
tedious, e.g. going through SOAP::Lite which I'd like to use at the
moment from the framework.

-- 
Radek