Stjepan Rajko wrote:
> 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).
>

Not directly related to your ideas but I'd just like to mention something 
aloud since lots of things are changing fast.

I think quickbook is a great code documentation tool and I use it to 
document code (and more) at work.  I would like to make sure that quickbook 
and its generated output is still useable without boost and for non-boost 
documentation.

I dont know if I still have to but before I had to add something like the 
following to my jamfile

<xsl:param>boost.image.src=images/company_logo.png
<xsl:param>boost.image.alt="\"Company Name\""
<xsl:param>boost.image.w=100
<xsl:param>boost.image.h=100

Which seems sort of silly.  Couldn't a more descriptive name be chosen for 
these paramaters that would invite the rest of the world to use these cool 
documentation tools?

Thanks,

Michael Marcin 


-------------------------------------------------------------------------
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

Reply via email to