On Tue, 3 Dec 2002, David Abrahams wrote: > That's seriously nice. The main complaint I have with writing Boost > docs by hand is the cost of creating indexes.
I'm hoping we can automate more mundane tasks as well. For instance, users have requested a log of changes between releases. DocBook already supports revision numbers with a set of tags like this: <revision> <revnumber>1.29.0</revnumber> <date>26 Aug 2002</date> <authorinitiaAls>dpg</authorinitials> <revremark>Support new function syntax</revremark> </revision> Since we often don't know the next Boost version number, we could add in a <nextrevnumber> tag: <revision> <nextrevnumber/> <date>26 Aug 2002</date> <authorinitiaAls>dpg</authorinitials> <revremark>Support new function syntax</revremark> </revision> As part of the release script, a little XSLT stylesheet could transform the <nextrevnumber> tags into real <revnumber> tags with the new version number, and commit the changes back to CVS. The "Latest News" section could be generated from the revision tags, too. > > I've also converted the Ref documentation and the reference documentation for > > Signals. To see the new features, check out the HTML version here: > > http://www.cs.rpi.edu/~gregod/Boost > > Adding some .pngs for the nav buttons would help the user experience A > LOT. Will do. Doug ------------------------------------------------------- This SF.net email is sponsored by: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at: http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en _______________________________________________ Boost-docs mailing list [EMAIL PROTECTED] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
