forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bernhard Huber <>
Subject Re: build times
Date Sat, 23 Nov 2002 00:08:06 GMT
just another idea decreate turn around time for writing documentation

1. write the docs using your favourite html-editor,
i tried using netscape html editor

just be aware of following rules:
   h1, h2, h3, h4 will become s1, s2, s3, s4 tags,
   use a div tag to mark the content of a h1/s1, h2/s2, ... tags.
thus write
   <p>bla, bla...</p>
       <p>bla, bla...</p>

2. save your html file in an import dir
3. use sitemap definition snippet to check your html docs:
   <!-- display an edited html document
     <map:match pattern="imports/**.html">
       <map:generate type="html" src="imports/{1}.html"/>
       <map:transform src="stylesheets/xhtml2document.xsl" label="content"/>
       <map:transform src="stylesheets/document2html.xsl"/>
       <map:serialize type="html"/>

Use, or adopt the xhtml2document.xsl snippet
   <xsl:template match="h1">
       <xsl:attribute name="title"><xsl:value-of 
       <xsl:apply-templates select="following-sibling::div[1]"/>

4. If your are happy with the docs, move it to its dest dir,
   converting it to xml, that's still on my to-do list....

i know this is not a replacement for a xml editor, but maybe i you
prefer using an html-editor....

any comments?
bye bernhard

Diana Shannon wrote:
> Having worked with a Forrest setup for Cocoon, I was wondering how we 
> can decrease the build time. It took me (on OSX 10.1 JVM 1.3.1) 30 
> minutes to build the docs statically. Removing the pdf links (which 
> prevents pdf generation) still took  24 minutes. I realize build times 
> are somewhat irrelevant for bots, but, I fear committers won't preview 
> their doc changes if build times are so long.
> Is this all because of the Cocoon command line? Do we have any options? 
> Or have I overlooked some important configuration detail (e.g. 
> cocoon.xconf). Or perhaps a problem with my setup.
> Thanks.
> Diana

View raw message