John Keiser ([EMAIL PROTECTED]) wrote:
> (Oh, that's the other problem. There's no getPackageDoc() in ClassDoc, and
> no getRootDoc in PackageDoc.)
Feel free to fix that.
> I am going to write out an architecture that will allow Doclets to be
> written a little easier that allows this sort of thing, but I want to make
> sure I'm not reinventing the wheel here.
I would stick to the standard JavaDoc architecture. After all, we want
to make sure that other people's doclets can work with our code. Since
this isn't a core Java package, we can create our own extensions, though
they must be upwardly compatible with the existing ones. However,
simply modifying the javadoc api package won't accomplish much because
the driver program won't use our extensions, requiring that a driver
prog be written first, which I think is backwards.
In some of these obscure situations, I'd run a test with Sun's javadoc
tool to see what comes out and emulate that behavior. You could also
find another doclet someone has released under a free software license
and look at what they did. As you say, we definitely want to avoid
reinventing the wheel.
--
Aaron M. Renn ([EMAIL PROTECTED]) http://www.urbanophile.com/arenn/
