"Reece Dunn" <[EMAIL PROTECTED]> writes: >>I think you *can* implement a collapsible hierarchy with frames, just >>by automatically generating the right index pages. I don't think it's >>really helpful to have collapsibility at every level of hierarchy >>anyway. Those interfaces where everything collapses tend to be one of >>those "script annoyances" I was talking about earlier ;-) > > The problem with this is that you would have N! ToC pages where N is > the number of chapters (since you can have any combination > collapsed/expanded). If you only allow one chapter to be expanded at > any one time, this means having N toc pages which would be more > feasible.
Of course I meant one-at-a-time expansion. It's hard to imagine why we'd use any other interface. People that want to bounce back and forth between the details of two libraries can open two browser windows. > I'll take a look at adding this to the possibilities > generated. Thanks, Reece! -- Dave Abrahams Boost Consulting http://www.boost-consulting.com ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Boost-docs mailing list [EMAIL PROTECTED] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
