Jeff Garland wrote: > > Sure, frames are allowed, as are CSSes, which are more powerful than > > most people know. > > We need to be very careful with frames. Used incorrectly they make it very > difficult to create a link to a page because the URL of the 'target' page > does not appear in the browser bar. This is a serious problem b/c it makes > getting the link to respond to a question, etc much harder...
I don't like frames, either. Most of the time they just eat up space on the screen, while adding very little. Maybe I'm just paranoid about desktop space ;-) > > 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 ;-) > > I agree -- I'm not fond of the collapsing trees either. Guess there's not a lot of Web designers out there, so if we run into a problems with JavaScript, it can be a nightmare. OTOH, the code Reece has sent looks simple and even works. But maybe just list of libraries in main Boost docs is the simplest thing to try first? - Volodya ------------------------------------------------------- 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
