[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Cp-tools-discuss] Re: Cp-tools Javadoc Overview (was Re: Classpath API
[Cp-tools-discuss] Re: Cp-tools Javadoc Overview (was Re: Classpath API javadoc)
Sun, 28 Apr 2002 17:17:53 +0100
> Mark Wielaard wrote:
> > I have not tried out the texidoclet for the Classpath Tools project yet.
> > Source can be found <http://savannah.gnu.org/cgi-bin/viewcvs/cp-tools/>
> > I don't know if there has been an official release yet.
> Hi there,
> let me take this opportunity and give you a brief overview of
> our doings at cp-tools.
> We have a couple of javadoc-related tools underway:
> - "Gjdoc" is an alternative javadoc driver. That is, it scans
> Java source files, extracts all javadoc related information
> and provides that to whichever doclet is plugged into it
> via the Doclet API.
> When finished, it will provide basically the same output
> as Sun's javadoc tool does, but currently there are some minor
> deviations and also some stuff missing.
How do we compile and run this driver?
What are its dependencies (versions too)?
> - "TexInfo doclet" (formerly TexiDoclet) takes that information
> (from either Gjdoc or Sun's Javadoc) and generates TexInfo code
> from it, which in turn can be converted to Info pages for viewing
> in Emacs or with the Info standalone tool. The TexInfo code is
> not intended for converting it into a printable form, though.
> - "XML doclet" puts all information into an XML file. I have
> written an XSLT style sheet which generates HTML documentation
> from that XML file. The generated HTML has a structure similar
> to that of Suns "Standard Doclet" output, but is currently
> missing a couple of things (for example, a full class tree
> page, serialization pages, package overview page)
|[Prev in Thread]
||[Next in Thread]|
- [Cp-tools-discuss] Re: Cp-tools Javadoc Overview (was Re: Classpath API javadoc),
John Leuner <=