comment on

However, I personally don't feel like it's a good replacement for the ActiveState web-based documentation that the OP was "spoilt" with using.

But you don't explain why

The ActiveState documentation includes other perldoc information like the FAQs, perlfunc, pragmas, etc.

So does HTMLBatch. No, it can't include ActiveState copyrighted material , but it does includes all the regular perl faqs etc

The module that I had suggested, Pod::POM::Web, includes all of those things that Pod::Simple::HTMLBatch does seem to cover. Also, Pod::POM::Web has a better interface and layout in my opinion.

:) I like Pod::POM::Web too, esp since I dont have disk space for html docs -- but I'm "way over" the frameset layout

FWIW, if you're on unix, http://perl.overmeer.net/ oodoc looks polished

In the same frame theme as oodoc there is also pdoc, used by http://doc.bioperl.org/

In reply to Re^6: How to Easily Check for Available CPAN Modules when Upgrading ActiveState Perl by Anonymous Monk
in thread How to Easily Check for Available CPAN Modules when Upgrading ActiveState Perl by ozboomer

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


go ahead... be a heretic
	PerlMonks