Matias Capeletto wrote:
On 6/20/07, Robert Ramey <ramey@rrsd.com> wrote:
Has there been any thought to adding to the Boostbook the facility for automatically generating a navigation window similar to what the serialization documentation uses. I believe this could be generated automatically by Boostbook. We already have javascript which has been vetted on all used browsers to implement this. The serialization library really depends upon this for navigating around the documentation.
Hi Rovert,
I have give it more than one thought to it. Iostream navigation style use frames. Frames are not part of XHTML because they cause lot of troubles. We have implemented a new navigation approach based on GropedLinks () select boxes. Look at the top-right corner of the page: http://tinyurl.com/22sja5
I didn't see anything at the top-right hand corner of the page. But I - assuming that the table of contents is automatically generated from the *.qbk documents - it seems to me that the table of contents page is almost what I want. All you have to do is: a) put it in a separate pane so it can be used to navigate around the documentation. b) add in the code - already written by J. Turkanis and tested by several of us on different browsers. I really like the expand/contract feature that the javascriptcontrol provides- though if I had to I could probably live without it. I would think that it would be an optional "add-on" that not everyone else has to use. Robert Ramey
GroupedLinks is documented here: http://tinyurl.com/332tsh
IMHO this select boxes offers a great deal of functionality and do not get in your way.
We are working in an automated algorithm to make the GroupedLinks definition files. Do you think your docs will work fine with GroupedLinks instead of frames?
Best regards Matias _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost