Stas, I downloaded DocSet-0.14 and got the example running. See the results here.
http://www.officevision.com/pub/DocSet/example/dst_html http://www.officevision.com/pub/DocSet/example/dst_ps FYI: I had to change the "id" in example/src/config.cfg from "docs" to "home" (I assume anything would have worked) because the "id" => "docs" was already in use in example/src/docs/config.cfg. (It complained about a duplicate id when I first ran it.) (I don't have a patch file.) If I understand how to use this correctly, I need my own distribution (perhaps "Devel::Perldocs") in which I have my own version of your "example" directory full of files. This defines styles, structure of resulting documents, and so forth. Devel::Perldocs would be the application component which uses [Module::Info and/or Devel::Metadata and/or Modinfo to gather the metadata (perhaps by implementing a replacement for DocSet::Source::* ?) and then uses DocSet to produce the documentation (with custom templates to create the desired look). Rather than replace DocSet::Source::Pod, I could actually create "metadata-enhanced" PODs as a result of all the metadata extraction and inherited-method-copying and then simply process these Pods in the normal way through DocSet. What other things would you describe had to be done in order to be able to generate documentation using DocSet which is similar to this? http://www.officevision.com/docs/perl http://www.officevision.com/pub/p5ee/software/htdocs/api/ Stephen At 12:09 AM 8/16/2002 +0800, Stas Bekman wrote: >Stephen Adkins wrote: >> Hi, >> >> DocSet looks nice. >> I will look into it more. >
