Douglas Gregor wrote:
With Jeff Garland's Doxygen XML test data, I've started to build a Doxygen XML->BoostBook translator. The XSL stylesheets are in the sandbox, in the directory libs/documentation/boostbook-xsl/doxygen. There are two stylesheets:Doug, I've tried it and it works. The first obvious problem
I've noticed is that I get
bool at_option() const;
Notes:
Tells if the current element is option.
While in fact the doc comment from source is closer to "Effects". There are some other nits, like missing class docs, but in general this is a good start.
BTW, I wonder if there's agreement on how Doxygen will be used. I think that the most reasonable way is to have a top-level in BoostBook, with selective inclusion of Doxygen fragments. I mean that it's probably not necessary to
convert Doxygen output into complete BoostBook file. What is needed is the
ability to include docs for a single class in an arbitrary place of the documentation. Do others feel the same? In that case there's no need to
care about doxygen's separate doc pages, etc.
- Volodya
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Boost-docs mailing list
[EMAIL PROTECTED]
Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
