I'm not aware of a CPAN Module, but that's just me, and yes, I think it could be CPAN worthy. You might want to post the POD as a RFC meditation to get more feedback.

But without looking at the source, I see two distinct tasks in your hack:

• convert a nested HTML list into an internal tree (probably via some HTML parser)
• output that tree as JavaScript code

There are some modules which do the first part, not necessary with HTML input. Pod::Simple::SimpleTree comes to mind. I would suggest to provide the JavaScript generating via your module with interfaces to existing tree generating modules.

On the name - maybe Tree::JS::dTree, since it could be used for other trees than just HTML lists?

Minor nit - your converted page lacks the TOP id in the box div :-)

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

Hi

I saw chromatic's review of Pod::POM::Web just the other day.

It seems to do what you are describing.

trwww

Thnx for the links. I also found a use.perl.org entry reviewing Pod::POM::Web with a screenshot link. And then found several other solutions on CPAN. I'd forgotten about the Pod::POM namespace.

But based on what I've seen thus far, Pod::ProjectDocs comes closest to what I'm after: a minimal solution to format the complete POD for a project, and that I can subclass for some add'l features I need. I don't really need/want a full webserver based solution, just the docs, and I'd rather not have to navigate an entire document model. With ProjectDocs, I can just grab or filter out what I need with a few regexen. Then just copy it up to a website for public consumption.

Which leads me to think I've got 2 distinct issues:

1. The general problem of converting nested HTML lists to a JS tree
2. The specific issue of easing navigation of POD project docs
(Note that if the nested lists were in their own div, or if the outermost list had a unique ID, the conversion could be done entirely in Javascript. But that much recursive Javascript in the browser makes me nervous).

After some minor changes to my HTML nested lists hack, I successfully applied it to some other non-POD web pages in dire need of refreshing/easier navigation. Which also leads me to think that using HTML nested lists might be a nice notation for generating JS tree widgets, since the HTML would be pretty standard, whereas there are about 1,000,000 different JS tree widget APIs roaming the web.

---

Perl Contrarian & SQL fanboy