Le Samedi, 8 Septembre 2007 14:12:14 -0400,
"Ty Roden" <ty.roden@xxxxxxxxx> a écrit :
If I may...
> I rarely chime in here (but read religiously). A full book format is
> preferable - even if only in PDF to me. To inspire those of us don't
> normally use POE to use it requires the informal style only a book can
> offer.
I would expect a book on POE to also cover topics that are interesting
to experienced developers already using POE. A couple of introductory
chapters for newbies and then inspirational material and applications.
500 pages would be OK ! :-) Aim for the thickness of the Template
Toolkit book :-)
> Reference material does nothing to help me see clear real world
> examples of how things work in POE.
To this I must disagree. I've learned POE that way (and through the
Cookbook) and have done two successful projects with it. But then I
only used a small fragment of POE, and did not code it like some
examples I've seen written by Rocco I think which uses a modularity
that I haven't touched that much.
So a book on POE would also be a book on how to code in POE, as it
would perhaps have been intended. Make it then three chapters for
newbies. ;-)
> My 2 cents on the topic... I feel a book targeted at a mid level Perl
> audience with "Here's how you would do this in Perl -> Now, here's
> the magic POE can offer for you" sort of example method of discussion
> will really be a boon to POE.
A 'pointer chapter' on "POE and Others" would also be nice. Recently
I've seen an example of the Catalyst framewrok working with POE, for
instance. "Extending POE" or using POE with other modules, with some
working examples would be nice.
Perhaps also a chapter on how to wrap some plain CPAN modules so that
they become POE friendly. Some time ago I was looking at a Log
Dispatch POE module that was quite a simpel wrap over the plain CPAN
Log Dispatch.
Makes me think... Anything planned with POE using threads ?
Cheers,
Al
|
