Generating HiveDoc from ModuleDescriptor objects would definitely be a requirement. This in turn requires some additions to the Descriptor classes (I can only think of "description" fields right now).
But the big question is: How should the HiveDoc be generated? Using a visitor to generate the equivalent XML again and then use the existing XSLT is the best solution I can come up with at the moment. Is anyone working on this yet? The Groovy support I've been playing with piggybacks on the DescriptorParser to create the ModuleDescriptors by generating SAX events. I think that's a reasonable approach as there is quite a bit of logic in DescriptorParser which would be unfortunate to duplicate. This, alas, requires changing the DescriptorParser so it can be used as a standard SAX ContentHandler. --knut On Tue, 12 Oct 2004 08:15:06 -0400, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > I'd like to see some refactoring to support generating HiveDoc from > the parsed Descriptor objects (however that would work!). Once that > is in place, I'd personally be much more open to various scripting > approaches to building the Registry. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
