Documentation has been an admitted problem
, and they are trying to form a scheme
to keep things coherent. There is a ton of documentation in the fairly dense POE modules themselves, and Dngor is working on consolidating it into more readable forms.
Good places to start:
Dennis Taylor's Introductory Article (Raw POD, but I found it a good read) (EDIT: Woops, seems to be the same article as Mr Person's perl.com link. :) - Not sure if there are revisions in the POD or not)
Evolution of a POE Server (A GREAT guided tour through designing a POE application from the ground up)
Out of the Main POE docs, POE::Session is probably the most important to understand, closely followed by POE::Kernel. As you can get by with just understanding the constants the Kernel exports at first.
I've read through the majority of the POE docs many many times over the past few months as I dabble in various projects, and still keep coming across more little things. Also, don't be afraid to just make your own page on the wiki and post questions there, or even on an existing page like the FAQ. It lets the friendly devs over there know what parts confuse people the most, and someone usually sees your question fairly quickly and will be happy to help you understand it.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||