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. Reference material does nothing to help me see clear real world examples of how things work in POE. I am one of the Perl coders out there who have marveled at the things you are doing with POE, only to be dumbfounded as to how to implement things in POE in my day to day coding because I can't yet grasp it properly. Inevitably I end upmoving back to non POE coding in Perl and keep watching this list hoping I will have the light bulb turn on someday.
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. - Ty Roden On 9/7/07, lanas <[EMAIL PROTECTED]> wrote: > > Le Vendredi, 7 Septembre 2007 15:29:52 -0400, > Rocco Caputo <[EMAIL PROTECTED]> a écrit : > > > POE has had a "documentation" project for over four years. It's in > > http://poe.svn.sourceforge.net/viewvc/poe/trunk/docs/ ... see > > revision 1997 for some really old documentation. > > > If people are really interested in contributing, please let me know > > how I can help. I can't actually write documentation. Until POE's > > perldocs are done, they have priority on my documentation > > resources. Maybe I can resurrect some old guidelines and outlines to > > provide some guidance, though. > > Personally, how I see it is more like a real book than documentation. > For comparison's sake, it'd be like a book on Perl OO such has the one > by Damian instead of the Perl OO man pages. The POE Cookbook gives some > good examples, but it is not like a book with all the extraneous text > and context explanation unecessary bla bla and such things (even > funny bits) that makes a book a book. That makes it an interesting > read and ultimately inspiring for trying things out. > > Documentation is very important, but a book, with its less formal > approach is great when it uses entertaining and interesting examples, > not only the basic stuff. > > Cheers, > Al > >
