Re: [boost] [QuickBook] missing prev/next

Subject: Re: [boost] [QuickBook] missing prev/next
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2011-01-05 13:24:33

> -----Original Message-----
> From: boost-bounces_at_[hidden] [mailto:boost-bounces_at_[hidden]]
> On Behalf Of Lorenzo Caminiti
> Sent: Wednesday, January 05, 2011 4:11 PM
> To: boost_at_[hidden]
> Subject: Re: [boost] [QuickBook] missing prev/next
> 
> On Tue, Dec 21, 2010 at 6:10 AM, Daniel James <dnljms_at_[hidden]> wrote:
> > On 21 December 2010 02:31, Lorenzo Caminiti <lorcaminiti_at_[hidden]>
> wrote:
> >>
> >> <link rel="stylesheet"
> >> href="C:%5CPROGRA~1%5Cboost%5Cboost_1_45_0/doc/src/boostbook.css"
> >> type="text/css">
> >
> > You shouldn't be using local absolute paths - they're not going to
> > work on other computers. The Jamfile for units sets 'boost.root' to
> > use the correct relative path so this shouldn't be a problem.
> >
> >> <link rel="home" href="../index.html" title="Boost.Local 0.0.1
> >> (development)"> <link rel="up" href="../index.html"
> >> title="Boost.Local 0.0.1 (development)">
> >
> > Where does 'Boost.Local 0.0.1' come from? Can you try building the
> > documentation with a clean copy of boost and see if that works? If not
> > please post your user-config.jam and 'bin.v2/boostbook_catalog.xml' so
> > we can see how you've set it up.
> >
> >> **Is there any way I can pullout debug info from XSL or similar?**
> >
> > You can use an <xsl:message> tag to write to stdout, such as:
> >
> >    <xsl:message>
> >        count($prev) = <xsl:value-of select="count($prev)"/>
> >    </xsl:message>
> >
> > http://www.sagehill.net/docbookxsl/DebuggingXSL.html
> 
> Unfortunately, I was not able to figure this out... my knowledge of these
tools is
> very limited...
> 
> I have posted the generated HTML on the web:
> http://contractpp.sourceforge.net/boost-local_0_1_0-
> 818/libs/local/doc/html/index.html
> The Quick Book source is in the Boost Vault under "Function Objects"
> boost-local_0_1_0-818.zip (see libs/local/doc/qbk) with the related
Jamfiles.
> 
> It would be great if someone could build this documentation and see if the
> prev/next links show up. If so then the issue is just with my Quick/Boost
Book
> configuration and not with my .qbk or .jam files...

Looking nice (if you want local functions ;-).

(Aside - other libraries all use a jamfile.v2, and have a different
directory structure.
I think you'd do better to get your proposed library in the sandbox, and
follow the structure used by others - though there is some variation - and
it would be a good idea if everyone had the same folder'n'file layout to
ease maintenance - and answering questions like this!).

I've only glanced at this, but do you now have to ask for a navigation bar?

  <xsl:param>nav.layout=horizontal # to get a horizontal navigation bar (you
probably DO want this).

  <xsl:param>boost.image=Boost # options are: none (no logo), Boost (for
boost.png), or your own logo like inspired_by_boost.png
  <xsl:param>boost.image.src=./images/boost.png   # <<<<<<<<<   note implied
location of /images
  <xsl:param>boost.image.w=180 # Width of logo in pixels.
  <xsl:param>boost.image.h=90 # Height of logo in pixels.

  # HTML options:
  <xsl:param>navig.graphics=1  # Use graphics not text for navigation.
  <xsl:param>chunk.section.depth=10  # How far down we chunk nested
sections, basically all of them.
  <xsl:param>chunk.first.sections=1  # Don't put the first section on the
same page as the TOC.
  <xsl:param>toc.section.depth=10  # How far down sections get TOCs.
  <xsl:param>toc.max.depth=4  # Max depth in each TOC.
  <xsl:param>generate.section.toc.level=10  # How far down we go with TOCs.

are in many libraries, and may help.

HTH

Paul

---
Paul A. Bristow,
Prizet Farmhouse, Kendal LA8 8AB  UK
[phone]  07714330204
pbristow_at_[hidden]