Imagine we have such a demo tool for perl/Tk!
Are you saying there isn't one? Because there is you know, its called widget. Also, wxPerl has a pretty similar demo.

 

Another example is the documentation that came with a standard installation of python, it is in one place, categorizes the modules according to their usage, searchable and indexed. Although ActivePerl came with a better presented documentation, it's still less thoughtful than that of python, and that of the perl books, IMHO.
Have you ever read
  perldoc perl
  perldoc perltoc
Looks fairly well organized and indexed to me. As for "searchability", but I guess additions could be made to perldoc (grep works for me when I need it, or windows "File Find" thing).

 

Now the goal of this post is not to complain, so please spare me the flames. I meant to ask, is there something we, as a community, can/should do to ease the pain of the beginners, actually also those of us less talented veterans. I truely believe all documentation is already there, it's just their organization, or lack of, that makes it less helpful. This is sort of like the web before google.
I don't know what you're getting at. I do not think there is anything, we, as a community, can/should do to ease the pain of the beginners. The perl documentation is pretty well organized, and if that's painful, well, then you need some one-on-one attention, or you need one of the many products that deal with the documentation on cpan, like tkpod among others.

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.


In reply to Re: Perl documentation by PodMaster
in thread Perl documentation by johnnywang

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.