> 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.
This is pretty much what I would expect. Inline code comments are typically a nice way to maintain the detailed reference materials that are tied directly to the structure of the code. In my experience, doc generators are not terribly helpful or productive way to create overview documentation. Jeff ------------------------------------------------------- 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
