On Wed, Jul 16, 2003 at 09:10:43AM -0700, Rich Morin wrote: > I'm finding the POE module documentation a bit hard to navigate, so > I've been playing with some indexing notions. After a bit of munging, > I boiled the CPAN search results down to ~140 entries. Some entries > don't have descriptions, to be sure, but most do:
[...] > Although this helps, it is already a bit lengthy for easy navigation > (and the list looks like it will continue to grow). I would therefore > like to suggest the creation of a "module index tree" for POE. I'd > aggregate the top few levels into a single page, as: [...] > Each of the entries would, of course, link to the appropriate CPAN (or > ???) page for the module. Creating these pages wouldn't be that hard, > but maintaining them is more work than I am willing to take on. OTOH, > perhaps part of the POE wiki could be used for this purpose; if folks > like the facility, some might help to keep it up to date. > > Reactions? One of the programs in POE's distribution is lib/cpan-test.perl, which uses CPANPLUS to grab all the POE component distributions and test them. It's used to incorporate CPAN as part of POE's regression test suite. I've modified that program to output something similar to what you want, except that it's limited to the distributions (not each module). It's imperfect in other ways. It doesn't see all the distribution descriptions, for instance. POE - (none) | Component | | CD | | | Detect - (none) | | | Rip - (none) | | Child - (none) | | Client | | | DNS - (none) | | | FTP - POE FTP client | | | HTTP - (none) | | | POP3 - (none) | | | Ping - concurrent ICMP ping without fork or threads | | | Rcon - (none) | | | UserAgent - LWP and LWP::Parallel based POE web client .... I've attached source for it. It's released under the same terms as Perl itself (someone always asks). It should be easy enough to generate wiki markup. How hard is it be to update a wiki page from a cron job? -- Rocco Caputo - [EMAIL PROTECTED] - http://poe.perl.org/
