Vladimir Prus wrote:

Jonathan Turkanis wrote:

...

I think Robert's menu is very effective, and was hoping it represented a de facto relaxation of the no-script policy.

...

I have some reservation

...

1. It does not work very nice when image loading is turned off (as it is for me). 2. It takes qutie a lot of screen space.

Hmm - on IE and Navigator I can slide the frame all the way to the right and make the navigation window disappear. This also raise the question about browsers that don't support frames. It would be my understanding that usage of frames would also make documentation un-displayable on some browsers.

I think it's probably better to somehow make all new libraries use Boost.Book. If that's done, any presentation issues can be solved in one place. For example, I think there were already discussion about expandable TOC on the boost-doc failings list.

I would like to see one package done in boost book before we impose such a requirement. When I go to the NightlyCVS link in the main boost page it shows what looks like boost book generated main page (whose aesthetics I'm not crazy about). When I click on one of the items it's a dead link. This gives me the impression that boost.book is still in development and that there are still too many pending issues to impose such a requirement.

At all events, I'd prefer constistent look of all Boost library docs (and the ability to print them), to every author introducing something they like.

I think the boost documentation information www.boost.org is pretty good and helps promote this idea. I think it should used as a starting point. Robert Ramey