I've started implementing a HiveDoc generator which gets its input from ModuleDescriptorProviders instead of reading the XML module descriptors. This should allow HiveDoc being generated for module descriptors defined in other formats.
The strategy of the implementation is to assemble a single XML document equivalent to that which the <createregistry> task creates and then feed it to the existing XSLT to generate the HiveDoc. Maybe this strategy should be changed in the future, but for now I think it should be the easiest approach. This implementation requires many of the Descriptor classes to be extended. Most obvious is a new "description" field. There are also a few cases where the Descriptor classes don't provide a getter. All this should be easy to fix. More problematic is: - <schema>s are not added to the Descriptor defining them. Instead they're directly linked to the elements using them. But this leaves out any unused schemas (e.g. "hivemind.lib.Pipeline"). - A <conversion> element is "unwrapped" and cannot be distinguished from its <rules> equivalent. Anyone got thoughts on this? --knut --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
