Hi, John Maddock recently mentioned using the boost.root parameter to avoid having to have copies of html/images in a libs own doc/html directory. In addition, this parameter is also applied as a prefix to the "Home", "People", "FAQ", and "More" links in the navbar (but not "Libraries").
Another cool use case seems to be that, instead of specifying the relative-path-to-boost-root, you can also specify a global url (like http://www.boost.org) and it will work with the images from there and the navbar links will also point to the right place. This seems useful for developing libs that are not yet in boost, and don't necessarily have a relative path to a boost root (when uploaded somewhere). My question is, should the boost.root parameter by default also be applied as a prefix to the boostbook.css location, as well as the "Libraries" link in the navbar? The former would require something like the following in html.xsl (and xhtml.xsl i presume): <xsl:param name="html.stylesheet"> <xsl:choose> <xsl:when test="$boost.root"><xsl:value-of select="concat($boost.root, '/doc/html/boostbook.css')"/></xsl:when> <xsl:otherwise>'boostbook.css'</xsl:otherwise> </xsl:choose> </xsl:param> (I tested this and it looks like it works.) The latter would require something similar in the definition of the boost.libraries xsl:param in navbar.xsl. Does this sound reasonable to add? I can post the diffs here for verification, since this is the first time I've looked at an xsl sheet. Please let me know what you think. Best regards, Stjepan ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
