Trouble is, having a ton of documentation is not really useful if there's not enough introductory stuff. POE suffers from this. The way people use documentation, at least when starting out, is they want to ask "I have problem X, how do I solve it". The POE docs don't help here, they're just a reference - at least that was the case last time I looked. But a reference is only useful once you know what you're doing.
Last time I whined about this, Rocco said that he knew it was a problem and he'd be happy to accept any documentation I could write. Unfortunately there's a bootstrapping problem there - without having sufficient documentation I couldn't learn the product in any reasonable time scale and so couldn't write the documentation.
exim suffers from the same problem. I learnt exim not from the docs but by taking someone elses config file and hacking it until it Did The Right Thing. I tried to learn POE the same way - taking the test suite and trying to turn it into my application, but POE's just a wee bit too complicated for me to learn it that way ;-)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||