Of these things, the "expand-all" and bigger twiddle targets would likely be among the easier, while the other two would require a lot more work.
These are in fact not too hard. I'll consider it.
It turns out that I've been sucked in to spending time learning about XSLT, XML editors, DocBooK, BoostBook. etc. So I've considered re-formating the serialization documentation in terms of BoostBook which would address all he the above and give the serialization library documentation a more up date look compatible with the other boost libraries.
BUT - I would lose the navigator - which I'm actually in love with.
What I would really like is an XSLT script which would build a free-floating BoostBook Navigator which would navigate all the boost book docs. Of course it's usage would be optional.
Nice idea. Robert: the HTML in your navigator pane looks rather similar to the HTML in generated for the Boostbook TOC page, could your scripts be injected in without too much change? If so we would just need to tweak HTML generation to produce an extra TOC page along with the frames etc? BTW I really don't like those tiny graphics either. Also just noted that docbook can output web help, which looks rather nice: http://docbook.sourceforge.net/release/xsl/current/webhelp/docs/content/ch01... but appears to require Java client side? John.