in reply to Re: An alternative Perldoc site
in thread An alternative Perldoc site

Two reasons:

  1. I haven't had the time to write a good POD-to-HTML converted to run across my local installation. :-) I wrote one once that worked decently, actually, but it indirectly depended on a bunch of modules I didn't want to keep and it had a few niggles of its own; rather than fix the latter, I trashed it in order to start fresh with a different set of the former; but I haven't gotten around to writing that replacement since.

  2. When I'm writing stuff on the web, I like to stick in hyperlinks for easy lookup for readers. It helps to have somewhere for the links to point to. *grin*

That said I don't like that new site particularly much, nor do I like Kobe's rendition. The search.cpan.org look and featureset is exactly what I want/like.

Update: actually, Kobesearch isn't as bad as I remember it; it had been a while since I went there. I still prefer the way the navigation is set up at search.cpan.org, but Kobesearch is quite nice as well now.

Makeshifts last the longest.

Replies are listed 'Best First'.
Re^3: An alternative Perldoc site
by jj808 (Hermit) on Jan 21, 2005 at 14:24 UTC
    The http://perldoc.perldrunks.org site is still quite heavily under development, so if could please be a bit more specific about what it is you don't like about the site then I'll certainly take your comments on board.

    Either post here or feel free to email me directly at jj@jonallen.info.

      It's not interlinked.

      F.ex, look at the perl POD page on perldoc.com: each POD page name it mentions is hyperlinked. Your version of perl has no links. Same goes for the “See also“ section of the POD pages on your site. Check the rendition of perlfunc on perldoc.com: the functions are all linked. Then click its link for unpack and compare with your version of the unpack documentation: on perldoc.com, the link actually leads to pack, on your site, it does nothing. That forces the user to constantly back out of his reading and delve into the navigation to locate where it is what they wanted to read, before being able to continue.

      I realize providing such extensive linking requires non-trivial guessing in the general case and even special case guessing for some particular POD pages. I did write a POD-tree-to-HTML-tree converter myself, so I know it can be a pretty ugly job.

      But not doing that greatly diminishes the value of the resulting docs, at least as far as I'm concerned.

      Makeshifts last the longest.

        Thanks Aristotle, those suggestions have now been implemented.
        Hi Aristotle,

        Thanks for the feedback, I'll put it on the to-do list for future versions.

        JJ