The beginning of your reply precisely illustrates why this isn't a great idea for POD

My point exactly. Why limit yourself to the lowest common denominator of POD?

Everyone has a browser. They are the single most advanced and powerful applications available for the presentation of complex information. Why not use them natively?

20 years ago, when a "browsers" meant lynx and man pages were cool, POD made some sense. But today?

your anchor got mangled entirely and does not (or at least originally didn't) point anywhere.

Not my anchor. See the first subhead beneath Synopsis at the top of the page: MCE->new ( [ options ] ).

Unfortunately, I can't see a way past PMs html restrictions, that will allow that to be linked correctly from here.

Anyway, just move to the second code section to see what I mean.

I am not seeing this mouseover effect under SCO

I did say: "imagine" :) I wasn't about to try and do a full html conversion job for the sake of a PM response. Especially as I know the author is currently restructuring and re-documenting the entire module suite.

I was simply trying to suggest that using html, those 5 screens of dense & impenetrable information could be cleanly presented on one screen. Giving both overview and detail as required.

I guess the bottom line is: if you think more of the same is the way to go; that's what we'll get.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
I'm with torvalds on this Agile (and TDD) debunked I told'em LLVM was the way to go. But did they listen!
P

In reply to Re^4: The problem of documenting complex modules. by BrowserUk
in thread The problem of documenting complex modules. by BrowserUk

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.