forrest-site-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r529915 [13/20] - in /forrest/site: ./ docs_0_70/ docs_0_70/howto/ docs_0_70/howto/cvs-ssh/ docs_0_70/howto/multi/ docs_0_80/ docs_0_80/howto/ docs_0_80/howto/cvs-ssh/ docs_0_80/howto/multi/ dtdx/ plan/ pluginDocs/ pluginDocs/plugins_0_70/ ...
Date Wed, 18 Apr 2007 08:36:26 GMT
Modified: forrest/site/docs_0_70/sitemap-ref.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_70/sitemap-ref.html?view=diff&rev=529915&r1=529914&r2=529915
==============================================================================
--- forrest/site/docs_0_70/sitemap-ref.html (original)
+++ forrest/site/docs_0_70/sitemap-ref.html Wed Apr 18 01:36:14 2007
@@ -3,7 +3,7 @@
 <head>
 <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.8-dev">
+<meta name="Forrest-version" content="0.9-dev">
 <meta name="Forrest-skin-name" content="pelt">
 <title>Forrest Sitemap Reference (v0.7)</title>
 <link type="text/css" href="../skin/basic.css" rel="stylesheet">
@@ -87,7 +87,7 @@
     |start Subtabs
     +-->
 <div id="level2tabs">
-<a class="selected" href="../docs_0_70/index.html">0.70 (current)</a><a class="unselected" href="../docs_0_80/index.html">0.80-dev (under development)</a><a class="unselected" href="../docs_0_60/index.html">0.60 (past)</a>
+<a class="unselected" href="../docs_0_80/index.html">0.80 (current)</a><a class="unselected" href="../docs_0_90/index.html">0.90-dev (under development)</a><a class="selected" href="../docs_0_70/index.html">0.70 (past)</a>
 </div>
 <!--+
     |end Endtabs
@@ -100,7 +100,7 @@
     |breadtrail
     +-->
 <div class="breadtrail">
-             
+
              &nbsp;
            </div>
 <!--+
@@ -283,7 +283,7 @@
 </div>
 <div id="credit">
 <hr>
-        This is documentation for current version v0.7
+        This is documentation for past version v0.7
        (<a href="http://forrest.apache.org/versions/">More</a>)</div>
 <div id="roundbottom">
 <img style="display: none" class="corner" height="15" width="15" alt="" src="../skin/images/rc-b-l-15-1body-2menu-3menu.png"></div>
@@ -312,7 +312,7 @@
 </div>
 <h1>Forrest Sitemap Reference</h1>
 <div id="motd-area">
-        This is documentation for current version v0.7
+        This is documentation for past version v0.7
        (<a href="http://forrest.apache.org/versions/">More</a>)</div>
 <div id="minitoc-area">
 <ul class="minitoc">
@@ -392,32 +392,31 @@
 </div>
     
 <p>
-      Technically, Forrest can be thought of as a 
-      <a href="http://cocoon.apache.org/2.1/">Cocoon</a> distribution that has been stripped down
-      and optimized for people with simple site publishing needs.  Central to
-      Cocoon, and hence Forrest, is the <strong>sitemap</strong>.  The sitemap
+      Technically, Forrest can be thought of as a
+      <a href="http://cocoon.apache.org/2.1/">Cocoon</a> distribution that has been stripped
+      down and optimized for people with simple site publishing needs. Central
+      to Cocoon, and hence Forrest, is the <strong>sitemap</strong>. The sitemap
       defines the site's URI space (what pages are available), and how each page
-      is constructed.  Understanding the sitemap is the key to understanding
+      is constructed. Understanding the sitemap is the key to understanding
       Forrest.
     </p>
     
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-      We advise you to spend time to understand the Apache Cocoon sitemap.
-      See <a href="http://cocoon.apache.org/2.1/userdocs/concepts/sitemap.html">Cocoon sitemap</a>
-      and <a href="http://cocoon.apache.org/2.1/userdocs/concepts/">Cocoon concepts</a>
-      and related component documentation.
-      The Forrest sitemap is broken into multiple files. The main one is
-      <strong>sitemap.xmap</strong> which delegates to others.
+      We advise you to spend time to understand the Apache Cocoon sitemap. See
+      <a href="http://cocoon.apache.org/2.1/userdocs/concepts/sitemap.html">Cocoon sitemap</a> and
+      <a href="http://cocoon.apache.org/2.1/userdocs/concepts/">Cocoon concepts</a> and related
+      component documentation. The Forrest sitemap is broken into multiple
+      files. The main one is <strong>sitemap.xmap</strong> which delegates to
+      others.
     </div>
 </div>
     
 <p>
-      This document provides an overview of the special sitemap which
-      is used at the core of Apache Forrest.
+      This document provides an overview of the special sitemap which is used at
+      the core of Apache Forrest.
     </p>
-
     
 <a name="N10028"></a><a name="getting_started"></a>
 <h2 class="underlined_10">Getting started</h2>
@@ -428,37 +427,37 @@
 <p>
         You can add pre-processing sitemaps to your project
         <span class="codefrag">src/documentation</span> directory (or wherever
-        <span class="codefrag">${project.sitemap-dir}</span> points to). Any match that
-        is not handled, passes through to be handled by the default Forrest
-        sitemaps - obviously extremely powerful. The capability is described
-        in 
-        "<a href="../docs_0_70/project-sitemap.html">Using project sitemaps</a>".
+        <span class="codefrag">${project.sitemap-dir}</span> points to). Any match that is not
+        handled, passes through to be handled by the default Forrest sitemaps -
+        obviously extremely powerful. The capability is described in
+        "<a href="../docs_0_70/project-sitemap.html">Using project
+        sitemaps</a>".
       </p>
 <p>
         Another way to experiment with the sitemap is to do '<span class="codefrag">forrest
-        run</span>' on a Forrest-using site.  Changes to the core
-        <span class="codefrag">*.xmap</span> files will now be immediately visible
-        at <span class="codefrag">&gt;http://localhost:8888/</span>
+        run</span>' on a Forrest-using site. Changes to the core
+        <span class="codefrag">*.xmap</span> files will now be immediately visible at
+        <span class="codefrag">&gt;http://localhost:8888/</span>
       
 </p>
 </div>
-
     
 <a name="N1004B"></a><a name="overview"></a>
 <h2 class="underlined_10">Sitemap Overview</h2>
 <div class="section">
 <p>
-        Forrest's sitemap is divided both physically and logically.  The most
-        obvious is the physical separation.  There are a number of separate
-        *.xmap files, each defining pipelines for a functional area.  Each *.xmap
-        file has its purpose documented in comments at the top.  Here is a brief
+        Forrest's sitemap is divided both physically and logically. The most
+        obvious is the physical separation. There are a number of separate
+        *.xmap files, each defining pipelines for a functional area. Each *.xmap
+        file has its purpose documented in comments at the top. Here is a brief
         overview of the files, in order of importance.
       </p>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
         
 <tr>
           
-<th colspan="1" rowspan="1"><strong>sitemap.xmap</strong></th>
+<th colspan="1" rowspan="1"><strong>sitemap.xmap</strong>
+          </th>
           <td colspan="1" rowspan="1">Primary sitemap file, which delegates responsibility for serving
             certain URIs to the others (technically called sub-sitemaps).  More
             about the structure of this file later.</td>
@@ -574,8 +573,7 @@
       
 </table>
 </div>
-
-    <!--
+<!--
     <section>
       <title>Logical structure</title>
       <p>There are a few major groups of sitemap pipelines</p>
@@ -586,35 +584,33 @@
       </dl>
     </section>
     -->
-
     
-<a name="N10122"></a><a name="source_pipelines"></a>
+<a name="N10123"></a><a name="source_pipelines"></a>
 <h2 class="underlined_10">Source pipelines (**.xml)</h2>
 <div class="section">
 <p>
         Most *.xmap files (forrest, aggregate, faq, status, issues, revisions,
-        dtd) define Source pipelines.  Source pipelines define the content
-        (body) XML for site pages.  The input XML format can be any format
+        dtd) define Source pipelines. Source pipelines define the content (body)
+        XML for site pages. The input XML format can be any format
         (document-v13, Docbook, RSS, FAQ, Howto) and from any source (local or
-        remote).  The output format is always Forrest's intermediate "document-v13"
-        format.
+        remote). The output format is always Forrest's intermediate
+        "document-v13" format.
       </p>
 <p>
-        Source pipelines always have a "<span class="codefrag">.xml</span>" extension.
-        Thus, 
+        Source pipelines always have a "<span class="codefrag">.xml</span>" extension. Thus,
         <a href="index.xml">index.xml</a> gives you the XML source for the
-        index page.  Likewise, <a href="faq.xml">faq.xml</a> gives you XML
-        for the FAQ (transformed from FAQ syntax), and 
-        <a href="changes.xml">changes.xml</a> returns XML from the status.xml file.
-        Take any page, and replace its extension (<span class="codefrag">.html</span> or
-        <span class="codefrag">.pdf</span>) with <span class="codefrag">.xml</span> and you'll have the Source
-        XML.
+        index page. Likewise, <a href="faq.xml">faq.xml</a> gives you XML
+        for the FAQ (transformed from FAQ syntax), and
+        <a href="changes.xml">changes.xml</a> returns XML from the
+        status.xml file. Take any page, and replace its extension
+        (<span class="codefrag">.html</span> or <span class="codefrag">.pdf</span>) with <span class="codefrag">.xml</span> and
+        you'll have the Source XML.
       </p>
 <p>
         This is quite powerful, because we now have an abstraction layer, or
         "virtual filesystem", on which the rest of Forrest's sitemap can build.
         Subsequent layers don't need to care whether the XML was obtained
-        locally or remotely, or from what format.  Wikis, RSS, FAQs and Docbook
+        locally or remotely, or from what format. Wikis, RSS, FAQs and Docbook
         files are all processed identically from here on.
       </p>
 <pre class="code">
@@ -628,35 +624,45 @@
 (*.xml)
                         (in forrest.xmap, faq.xmap, etc)
       </pre>
-<a name="N1014D"></a><a name="forrest_xmap"></a>
+<a name="N1014E"></a><a name="forrest_xmap"></a>
 <h3 class="underlined_5">forrest.xmap</h3>
 <p>
           Most of the usual Source pipelines are defined in
           <span class="codefrag">forrest.xmap</span> which is the default (fallback) handler for
-          <span class="codefrag">**.xml</span> pages. The forrest.xmap uses the 
-          <a href="../docs_0_70/cap.html">SourceTypeAction</a> to determine the type of XML
-          it is processing, and converts it to document-v13 if necessary.
+          <span class="codefrag">**.xml</span> pages. The forrest.xmap uses the
+          <a href="../docs_0_70/cap.html">SourceTypeAction</a> to determine the
+          type of XML it is processing, and converts it to document-v13 if
+          necessary.
+        </p>
+<p>
+          For instance, say we are rendering
+          <a href="../docs_0_70/howto/howto-howto.html">a Howto document</a> called
+          "howto-howto.xml". It contains this DOCTYPE declaration:
         </p>
-<p>For instance, say we are rendering <a href="../docs_0_70/howto/howto-howto.html">a
-            Howto document</a> called "howto-howto.xml".  It contains this DOCTYPE
-          declaration:</p>
 <pre class="code">
 &lt;!DOCTYPE howto PUBLIC "-//APACHE//DTD How-to V1.3//EN"
   "http://forrest.apache.org/dtd/howto-v13.dtd"&gt;</pre>
-<p>The SourceTypeAction sees this, and applies this transform to get it
-          to document-v13:</p>
+<p>
+          The SourceTypeAction sees this, and applies this transform to get it
+          to document-v13:
+        </p>
 <pre class="code">
+
           &lt;map:when test="howto-v13"&gt;
             &lt;map:transform src="{forrest:forrest.stylesheets}/howto2document.xsl" /&gt;
           &lt;/map:when&gt;
-          </pre>
-<a name="N10175"></a><a name="other_source"></a>
+          
+        </pre>
+<a name="N10176"></a><a name="other_source"></a>
 <h3 class="underlined_5">Other source pipelines</h3>
-<p>As mentioned above, all non-core Source pipelines are distributed in
-          independent <span class="codefrag">*.xmap</span> files.  There is a block of
+<p>
+          As mentioned above, all non-core Source pipelines are distributed in
+          independent <span class="codefrag">*.xmap</span> files. There is a block of
           <span class="codefrag">sitemap.xmap</span> which simply delegates certain requests to
-          these subsitemaps:</p>
+          these subsitemaps:
+        </p>
 <pre class="code">
+
       &lt;!-- Body content --&gt;
       &lt;map:match pattern="**.xml"&gt;
         &lt;map:match pattern="changes.xml"&gt;
@@ -683,51 +689,59 @@
           &lt;map:mount uri-prefix="" src="aggregate.xmap" check-reload="yes" /&gt;
         &lt;/map:match&gt;
         ....
-        ....</pre>
-<a name="N10188"></a><a name="late_binding_pipelines"></a>
+        ....
+        </pre>
+<a name="N10189"></a><a name="late_binding_pipelines"></a>
 <h4>Late-binding pipelines</h4>
 <p>
             One point of interest here is that the sub-sitemap is often not
             specific about which URLs it handles, and relies on the caller (the
-            section listed above) to only pass relevant requests to it.  We term
-            this "binding a URL" to a pipeline.</p>
-<p>For instance, the main pipeline in <span class="codefrag">faq.xmap</span> matches
+            section listed above) to only pass relevant requests to it. We term
+            this "binding a URL" to a pipeline.
+          </p>
+<p>
+            For instance, the main pipeline in <span class="codefrag">faq.xmap</span> matches
             <span class="codefrag">**.xml</span>, but only <span class="codefrag">**faq.xml</span> requests are
-            sent to it.</p>
-<p>This "late binding" is useful, because the whole URL space is
+            sent to it.
+          </p>
+<p>
+            This "late binding" is useful, because the whole URL space is
             managed in <span class="codefrag">sitemap.xmap</span> and not spread over lots of
-            *.xmap files.  For instance, say you wish all <span class="codefrag">*.xml</span>
-            inside a "<span class="codefrag">faq/</span>" directory to be processed as FAQs.  Just
+            *.xmap files. For instance, say you wish all <span class="codefrag">*.xml</span>
+            inside a "<span class="codefrag">faq/</span>" directory to be processed as FAQs. Just
             override <span class="codefrag">sitemap.xmap</span> and redefine the relevant source
-            matcher:</p>
+            matcher:
+          </p>
 <pre class="code">
+
         &lt;map:match pattern="**faq.xml"&gt;
           &lt;map:mount uri-prefix="" src="faq.xmap" check-reload="yes" /&gt;
-        &lt;/map:match&gt;</pre>
+        &lt;/map:match&gt;
+          </pre>
 </div>
-
     
-<a name="N101B3"></a><a name="output_pipelines"></a>
+<a name="N101B4"></a><a name="output_pipelines"></a>
 <h2 class="underlined_10">Output pipelines</h2>
 <div class="section">
 <p>
         To recap, we now have a <span class="codefrag">*.xml</span> pipeline defined for each
-        page in the site, emitting standardized XML.  These pipeline definitions
+        page in the site, emitting standardized XML. These pipeline definitions
         are located in various *.xmap files, notably forrest.xmap
       </p>
 <p>
         We now wish to render the XML from these pipelines to output formats
         like HTML and PDF.
       </p>
-<a name="N101C2"></a><a name="pdf"></a>
+<a name="N101C3"></a><a name="pdf"></a>
 <h3 class="underlined_5">PDF output</h3>
 <p>
           Easiest case first; PDFs don't require menus or headers, so we can
           simply transform our intermediate format into XSL:FO, and from there
-          to PDF.  This is done by the following matcher in
+          to PDF. This is done by the following matcher in
           <span class="codefrag">sitemap.xmap</span> ...
         </p>
 <pre class="code">
+
 1   &lt;map:match type="regexp" pattern="^(.*?)([^/]*).pdf$"&gt;
 2     &lt;map:generate src="cocoon:/{1}{2}.xml"/&gt;
 3     &lt;map:transform type="xinclude"/&gt;
@@ -738,6 +752,7 @@
 8     &lt;/map:transform&gt;
 9     &lt;map:serialize type="fo2pdf"/&gt;
 10  &lt;/map:match&gt;
+        
         </pre>
 <ol>
           
@@ -757,13 +772,17 @@
             XSL:FO XML.</li>
         
 </ol>
-<p>Lastly, we generate a PDF using the fo2pdf serializer.</p>
-<a name="N101FC"></a><a name="html"></a>
+<p>
+          Lastly, we generate a PDF using the fo2pdf serializer.
+        </p>
+<a name="N101FD"></a><a name="html"></a>
 <h3 class="underlined_5">HTML output</h3>
-<p>Generating HTML pages is more complicated, because we have to merge
+<p>
+          Generating HTML pages is more complicated, because we have to merge
           the page body with a menu and tabs, and then add a header and footer.
-          Here is the <span class="codefrag">*.html</span> matcher in
-          <span class="codefrag">sitemap.xmap</span> ...</p>
+          Here is the <span class="codefrag">*.html</span> matcher in <span class="codefrag">sitemap.xmap</span>
+          ...
+        </p>
 <pre class="code">
           &lt;map:match pattern="*.html"&gt;
             &lt;map:aggregate element="site"&gt;
@@ -780,9 +799,9 @@
 <p>
           So <a href="index.html">index.html</a> is formed from
           aggregating <a href="body-index.html">body-index.html</a> and
-          <a href="menu-index.html">menu-index.html</a> and 
-          <a href="tab-index.html">tab-index.html</a> and then applying the
-          <span class="codefrag">site2xhtml.xsl</span> stylesheet to the result.
+          <a href="menu-index.html">menu-index.html</a> and
+          <a href="tab-index.html">tab-index.html</a> and then applying
+          the <span class="codefrag">site2xhtml.xsl</span> stylesheet to the result.
         </p>
 <p>
           There is a nearly identical matcher for HTML files in subdirectories:
@@ -804,13 +823,16 @@
         </pre>
 </div>
     
-<a name="N10246"></a><a name="intermediate_pipelines"></a>
+<a name="N10247"></a><a name="intermediate_pipelines"></a>
 <h2 class="underlined_10">Intermediate pipelines</h2>
 <div class="section">
-<a name="N1024C"></a><a name="body_pipeline"></a>
+<a name="N1024D"></a><a name="body_pipeline"></a>
 <h3 class="underlined_5">Page body</h3>
-<p>Here is the matcher which generates the page body:</p>
+<p>
+          Here is the matcher which generates the page body:
+        </p>
 <pre class="code">
+
 1   &lt;map:match pattern="**body-*.html"&gt;
 2     &lt;map:generate src="cocoon:/{1}{2}.xml"/&gt;
 3     &lt;map:transform type="idgen"/&gt;
@@ -822,7 +844,8 @@
 9       &lt;map:parameter name="notoc" value="false"/&gt;
 10    &lt;/map:call&gt;
 11  &lt;/map:match&gt;
-          </pre>
+          
+        </pre>
 <ol>
           
 <li>In our matcher pattern, {1} will be the directory (if any) and {2}
@@ -831,12 +854,13 @@
 <li>First, we obtain XML content from a source pipeline</li>
           
 <li>
-            
-<p>We then apply a custom-written
+<p>
+              We then apply a custom-written
               <span class="codefrag">IdGeneratorTransformer</span>, which ensures that every
-              &lt;section&gt; has an "id" attribute if one is not supplied, by generating one from the
-              &lt;title&gt; if necessary.  For example, &lt;idgen&gt; will
-              transform:</p>
+              &lt;section&gt; has an "id" attribute if one is not supplied, by
+              generating one from the &lt;title&gt; if necessary. For example,
+              &lt;idgen&gt; will transform:
+            </p>
             
 <pre class="code">
               &lt;section&gt;
@@ -844,7 +868,9 @@
               ...
             </pre>
             
-<p>into:</p>
+<p>
+              into:
+            </p>
             
 <pre class="code">
               &lt;section id="How+to+boil+eggs"&gt;
@@ -852,10 +878,11 @@
               ...
             </pre>
             
-<p>Later, the <span class="codefrag">document2html.xsl</span> stylesheet will create
+<p>
+              Later, the <span class="codefrag">document2html.xsl</span> stylesheet will create
               an &lt;a name&gt; element for every section, allowing this section to
-              be referred to as <span class="codefrag">index.html#How+to+boil+eggs</span>.</p>
-          
+              be referred to as <span class="codefrag">index.html#How+to+boil+eggs</span>.
+            </p>
 </li>
           
 <li>We then expand XInclude elements.</li>
@@ -867,10 +894,14 @@
             &lt;html&gt; and &lt;body&gt;) suitable for merging with the menu and tabs.</li>
         
 </ol>
-<a name="N10291"></a><a name="menu_pipeline"></a>
+<a name="N10290"></a><a name="menu_pipeline"></a>
 <h3 class="underlined_5">Page menu</h3>
-<p>In the <span class="codefrag">sitemap.xmap</span> file, the matcher generating HTML for the menu is:</p>
+<p>
+          In the <span class="codefrag">sitemap.xmap</span> file, the matcher generating HTML for
+          the menu is:
+        </p>
 <pre class="code">
+
       &lt;map:match pattern="**menu-*.html"&gt;
         &lt;map:generate src="cocoon:/{1}book-{2}.html"/&gt;
         &lt;map:transform type="<a href="#linkrewriting_impl">linkrewriter</a>" src="cocoon:/{1}linkmap-{2}.html"/&gt;
@@ -879,17 +910,25 @@
           &lt;map:parameter name="path" value="{1}{2}.html"/&gt;
         &lt;/map:call&gt;
       &lt;/map:match&gt;
-      </pre>
-<p>We get XML from a "book" pipeline, 
-        <a href="#linkrewriting_impl">rewrite links</a>, and apply the
-          <span class="codefrag">book2menu.xsl</span> stylesheet to generate HTML.</p>
-<p>How the menu XML is actually generated (the *book-*.html pipeline) is
-          sufficiently complex to require a 
-          <a href="#menu_xml_generation">section of its own</a>.</p>
-<a name="N102B7"></a><a name="tab_pipeline"></a>
+      
+        </pre>
+<p>
+          We get XML from a "book" pipeline,
+          <a href="#linkrewriting_impl">rewrite links</a>, and apply the
+          <span class="codefrag">book2menu.xsl</span> stylesheet to generate HTML.
+        </p>
+<p>
+          How the menu XML is actually generated (the *book-*.html pipeline) is
+          sufficiently complex to require a
+          <a href="#menu_xml_generation">section of its own</a>.
+        </p>
+<a name="N102B6"></a><a name="tab_pipeline"></a>
 <h3 class="underlined_5">Page tabs</h3>
-<p>Tab generation is quite tame compared to menus:</p>
+<p>
+          Tab generation is quite tame compared to menus:
+        </p>
 <pre class="code">
+
      &lt;map:match pattern="**tab-*.html"&gt;
        &lt;map:generate src="content/xdocs/tabs.xml" /&gt;
        &lt;map:transform type="<a href="#linkrewriting_impl">linkrewriter</a>" src="cocoon:/{1}linkmap-{2}.html"/&gt;
@@ -898,43 +937,53 @@
          &lt;map:parameter name="path" value="{1}{2}.html"/&gt;
        &lt;/map:call&gt;
      &lt;/map:match&gt;
-           </pre>
-<p>All the smarts are in the <span class="codefrag">tab2menu.xsl</span> stylesheet, which
-          needs to choose the correct tab based on the current path.  Currently,
-          a "longest matching path" algorithm is implemented.  See the
-          <span class="codefrag">tab2menu.xsl</span> stylesheet for details.</p>
+           
+        </pre>
+<p>
+          All the smarts are in the <span class="codefrag">tab2menu.xsl</span> stylesheet, which
+          needs to choose the correct tab based on the current path. Currently,
+          a "longest matching path" algorithm is implemented. See the
+          <span class="codefrag">tab2menu.xsl</span> stylesheet for details.
+        </p>
 </div>
-
     
-<a name="N102D3"></a><a name="menu_xml_generation"></a>
+<a name="N102D2"></a><a name="menu_xml_generation"></a>
 <h2 class="underlined_10">Menu XML generation</h2>
 <div class="section">
-<p>The "book" pipeline is defined in <span class="codefrag">sitemap.xmap</span>as:</p>
+<p>
+        The "book" pipeline is defined in <span class="codefrag">sitemap.xmap</span>as:
+      </p>
 <pre class="code">
+
         &lt;map:match pattern="**book-*.html"&gt;
           &lt;map:mount uri-prefix="" src="menu.xmap" check-reload="yes" /&gt;
         &lt;/map:match&gt;
-        </pre>
-<p>Meaning that it is defined in the <span class="codefrag">menu.xmap</span> file.  In there we find
-        the real definition, which is quite complicated, because there are three
-        supported menu systems (see <a href="../docs_0_70/linking.html">menus and
-          linking</a>).  We will not go through the sitemap itself
-        (menu.xmap), but will instead describe the logical steps involved:</p>
+        
+      </pre>
+<p>
+        Meaning that it is defined in the <span class="codefrag">menu.xmap</span> file. In there
+        we find the real definition, which is quite complicated, because there
+        are three supported menu systems (see
+        <a href="../docs_0_70/linking.html">menus and linking</a>). We will not
+        go through the sitemap itself (menu.xmap), but will instead describe the
+        logical steps involved:
+      </p>
 <ol>
         
 <li>Take site.xml and expand hrefs so that they are all
           root-relative.</li>
         
 <li>
-<p>Depending on the <span class="codefrag">forrest.menu-scheme</span> property, we
-            now apply one of the two algorithms for choosing a set of menu links
+<p>
+            Depending on the <span class="codefrag">forrest.menu-scheme</span> property, we now
+            apply one of the two algorithms for choosing a set of menu links
             (described in <a href="../docs_0_70/linking.html#menu_generation">menu
-              generation</a>):</p>
+            generation</a>):
+          </p>
           
 <ul>
             
 <li>
-              
 <p>
                 For "@tab" menu generation, we first ensure each site.xml node
                 has a tab attribute (inherited from a parent if necessary), and
@@ -944,10 +993,10 @@
               
 <p>
                 For example, say our current page's path is
-                <span class="codefrag">community/howto/index.html</span>.  In
+                <span class="codefrag">community/howto/index.html</span>. In
                 <span class="codefrag">site.xml</span> we look for the node with this
-                "<span class="codefrag">href</span>" and discover its "<span class="codefrag">tab</span>" attribute
-                value is "<span class="codefrag">howtos</span>".  We then prune the
+                "<span class="codefrag">href</span>" and discover its "<span class="codefrag">tab</span>"
+                attribute value is "<span class="codefrag">howtos</span>". We then prune the
                 <span class="codefrag">site.xml</span>-derived content to contain only nodes with
                 <span class="codefrag">tab="howtos"</span>.
               </p>
@@ -958,41 +1007,45 @@
               </p>
               
 <pre class="code">
+
 &lt;map:transform src="resources/stylesheets/site2site-normalizetabs.xsl" /&gt;
 &lt;map:transform src="resources/stylesheets/site2site-selectnode.xsl"&gt;
   &lt;map:parameter name="path" value="{1}{2}"/&gt;
 &lt;/map:transform&gt;
-                </pre>
-            
+                
+              </pre>
 </li>
             
 <li>
-              
-<p>For "directory" menu generation, we simply use an
+<p>
+                For "directory" menu generation, we simply use an
                 <span class="codefrag">XPathTransformer</span> to include only pages in the
-                current page's directory, or below:</p>
+                current page's directory, or below:
+              </p>
               
 <pre class="code">
+
 &lt;map:transform type="xpath"&gt;
   &lt;map:parameter name="include" value="//*[@href='{1}']" /&gt;
 &lt;/map:transform&gt;
-                </pre>
+                
+              </pre>
               
 <p>
-                Here, the "<span class="codefrag">{1}</span>" is the directory part of the current
-                page.  So if our current page is
-                <span class="codefrag">community/howto/index.html</span> then "<span class="codefrag">{1}</span>" will
-                be <span class="codefrag">community/howto/</span> and the transformer will
+                Here, the "<span class="codefrag">{1}</span>" is the directory part of the
+                current page. So if our current page is
+                <span class="codefrag">community/howto/index.html</span> then "<span class="codefrag">{1}</span>"
+                will be <span class="codefrag">community/howto/</span> and the transformer will
                 include all nodes in that directory.
               </p>
-            
 </li>
           
 </ul>
           
-<p>We now have a <span class="codefrag">site.xml</span> subset relevant to our current
-            page.</p>
-        
+<p>
+            We now have a <span class="codefrag">site.xml</span> subset relevant to our current
+            page.
+          </p>
 </li>
         
 <li>The "<span class="codefrag">href</span>" nodes in this are then made relative to the
@@ -1005,58 +1058,65 @@
       
 </ol>
 </div>
-
     
-<a name="N10359"></a><a name="linkrewriting_impl"></a>
+<a name="N10353"></a><a name="linkrewriting_impl"></a>
 <h2 class="underlined_10">Link rewriting</h2>
 <div class="section">
-<p>In numerous places in <span class="codefrag">sitemap.xmap</span> you will see the
-        "linkrewriter" transformer in action.  For example:</p>
-<pre class="code">&lt;map:transform type="linkrewriter" src="cocoon:/{1}linkmap-{2}.html"/&gt;</pre>
-<p>This statement is Cocoon's linking system in action.  A full
-        description is provided in <a href="../docs_0_70/linking.html">Menus and
-          Linking</a>.  Here we describe the implementation of linking.</p>
-<a name="N10370"></a><a name="input_modules"></a>
+<p>
+        In numerous places in <span class="codefrag">sitemap.xmap</span> you will see the
+        "linkrewriter" transformer in action. For example:
+      </p>
+<pre class="code">
+&lt;map:transform type="linkrewriter" src="cocoon:/{1}linkmap-{2}.html"/&gt;
+      </pre>
+<p>
+        This statement is Cocoon's linking system in action. A full description
+        is provided in <a href="../docs_0_70/linking.html">Menus and
+        Linking</a>. Here we describe the implementation of linking.
+      </p>
+<a name="N1036A"></a><a name="input_modules"></a>
 <h3 class="underlined_5">Cocoon foundations: Input Modules</h3>
 <p>
           The implementation of <span class="codefrag">site:</span> linking is heavily based on
           Cocoon <a href="http://cocoon.apache.org/2.1/userdocs/concepts/modules.html">Input Modules</a>, a
-          little-known but quite powerful aspect of Cocoon.  Input Modules are
+          little-known but quite powerful aspect of Cocoon. Input Modules are
           generic Components which simply allow you to look up a value with a
-          key.  The value is generally dynamically generated, or obtained by
+          key. The value is generally dynamically generated, or obtained by
           querying an underlying data source.
         </p>
 <p>
           In particular, Cocoon contains an <span class="codefrag">XMLFileModule</span>, which
           lets one look up the value of an XML node, by interpreting the key as
-          an XPath expression.  Cocoon also has a
+          an XPath expression. Cocoon also has a
           <span class="codefrag">SimpleMappingMetaModule</span>, which allows the key to be
           rewritten before it is used to look up a value.
         </p>
 <p>
           The idea for putting these together to rewrite "<span class="codefrag">site:</span>"
           links was described in <a href="http://marc.theaimsgroup.com/?t=103992708800001&r=1&w=2">this
-            thread</a>. The idea is to write a Cocoon Transformer that
-          triggers on encountering &lt;link
-          href="<span class="codefrag">scheme:address</span>"&gt;, and interprets the
-          <span class="codefrag">scheme:address</span> internal URI as
-          <span class="codefrag">inputmodule:key</span>.  The transformer then uses the named
+          thread</a>. The idea is to write a Cocoon Transformer that triggers
+          on encountering &lt;link href="<span class="codefrag">scheme:address</span>"&gt;, and
+          interprets the <span class="codefrag">scheme:address</span> internal URI as
+          <span class="codefrag">inputmodule:key</span>. The transformer then uses the named
           InputModule to look up the key value. The <span class="codefrag">scheme:address</span>
-          URI is then rewritten with the found value.  This transformer was
-          implemented as 
+          URI is then rewritten with the found value. This transformer was
+          implemented as
           <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15611">LinkRewriterTransformer</a>,
           currently distributed as a "block" in Cocoon 2.1
         </p>
-<a name="N103A4"></a><a name="implement_rewriting"></a>
+<a name="N1039E"></a><a name="implement_rewriting"></a>
 <h3 class="underlined_5">Implementing "site:" rewriting</h3>
 <p>
           Using the above components, "<span class="codefrag">site:</span>" URI rewriting is
           accomplished as follows.
         </p>
-<a name="N103B3"></a><a name="cocoon_xconf"></a>
+<a name="N103AD"></a><a name="cocoon_xconf"></a>
 <h4>cocoon.xconf</h4>
-<p>First, we declare all the input modules we will be needing:</p>
+<p>
+            First, we declare all the input modules we will be needing:
+          </p>
 <pre class="code">
+
 &lt;!-- For the site: scheme --&gt;
 &lt;component-instance
   class="org.apache.cocoon.components.modules.input.XMLFileModule"
@@ -1071,7 +1131,8 @@
 &lt;component-instance
   class="org.apache.cocoon.components.modules.input.SimpleMappingMetaModule"
   logger="core.modules.mapper" name="ext"/&gt;
-</pre>
+
+          </pre>
 <ul>
             
 <li>
@@ -1083,21 +1144,21 @@
 <strong>site</strong> provides a "mask" over
               <strong>linkmap</strong> such that <span class="codefrag">site:index</span> expands
               to <span class="codefrag">linkmap:/site//index/@href</span>
-            
 </li>
             
 <li>
 <strong>ext</strong> provides another "mask" over
               <strong>linkmap</strong>, such that <span class="codefrag">ext:ant</span> would
               expand to <span class="codefrag">linkmap:/site/external-refs//ant/@href</span>
-            
 </li>
           
 </ul>
-<p>However at the moment, we have only declared the input modules.
-            They will be configured in <span class="codefrag">sitemap.xmap</span> as described in
-            the next section.</p>
-<a name="N103F1"></a><a name="sitemap"></a>
+<p>
+            However at the moment, we have only declared the input modules. They
+            will be configured in <span class="codefrag">sitemap.xmap</span> as described in the
+            next section.
+          </p>
+<a name="N103E9"></a><a name="sitemap"></a>
 <h4>sitemap.xmap</h4>
 <p>
             Now in the sitemap, we define the LinkRewriterTransformer, and
@@ -1105,6 +1166,7 @@
             content:
           </p>
 <pre class="code">
+
 ....
 &lt;!-- Rewrites links, e.g. transforming
      href="site:index" to href="../index.html"
@@ -1138,55 +1200,68 @@
   &lt;map:transform type="xinclude"/&gt;
   &lt;map:transform type="linkrewriter" src="cocoon:/{1}linkmap-{2}.html"/&gt;
   ...
-&lt;/map:match&gt;</pre>
-<p>As you can see, our three input modules are configured as part of
-            the LinkRewriterTransformer's configuration.</p>
+&lt;/map:match&gt;
+          </pre>
+<p>
+            As you can see, our three input modules are configured as part of
+            the LinkRewriterTransformer's configuration.
+          </p>
 <ul>
             
 <li>
-              
-<p>Most deeply nested, we have:</p>
+<p>
+                Most deeply nested, we have:
+              </p>
               
 <pre class="code">
+
                 &lt;input-module name="linkmap"&gt;
                   &lt;file src="{src}" reloadable="false" /&gt;
-              &lt;/input-module&gt;</pre>
+              &lt;/input-module&gt;
+              </pre>
               
-<p>The "<span class="codefrag">{src}</span>" text is expanded to the value of the
+<p>
+                The "<span class="codefrag">{src}</span>" text is expanded to the value of the
                 "<span class="codefrag">src</span>" attribute in the "<span class="codefrag">linkrewriter</span>"
-                instance, namely "<span class="codefrag">cocoon:/{1}linkmap-{2}.html</span>"
-                Thus the <span class="codefrag">linkmap</span> module reads dynamically
-                generated XML specific to the current request.</p>
-            
+                instance, namely "<span class="codefrag">cocoon:/{1}linkmap-{2}.html</span>" Thus
+                the <span class="codefrag">linkmap</span> module reads dynamically generated XML
+                specific to the current request.
+              </p>
 </li>
             
 <li>
-              
-<p>One level out, we configure the "<span class="codefrag">site</span>" and
+<p>
+                One level out, we configure the "<span class="codefrag">site</span>" and
                 "<span class="codefrag">ext</span>" input modules, to map onto our dynamically
-                configured "<span class="codefrag">linkmap</span>" module.</p>
-            
+                configured "<span class="codefrag">linkmap</span>" module.
+              </p>
 </li>
             
 <li>
-              
-<p>Then at the outermost level, we configure the
-                "<span class="codefrag">linkrewriter</span>" transformer.  First we tell it which
-                attributes to consider rewriting:</p>
+<p>
+                Then at the outermost level, we configure the
+                "<span class="codefrag">linkrewriter</span>" transformer. First we tell it which
+                attributes to consider rewriting:
+              </p>
               
 <pre class="code">
+
                 &lt;link-attrs&gt;href src&lt;/link-attrs&gt;
-                &lt;schemes&gt;site ext&lt;/schemes&gt;</pre>
+                &lt;schemes&gt;site ext&lt;/schemes&gt;
+              </pre>
               
-<p>So, "<span class="codefrag">href</span>" and "<span class="codefrag">src</span>" attributes starting
-                with "<span class="codefrag">site:</span>" or "<span class="codefrag">ext:</span>" are rewritten.</p>
-
+<p>
+                So, "<span class="codefrag">href</span>" and "<span class="codefrag">src</span>" attributes
+                starting with "<span class="codefrag">site:</span>" or "<span class="codefrag">ext:</span>" are
+                rewritten.
+              </p>
               
-<p>By nesting the "<span class="codefrag">site</span>" and "<span class="codefrag">ext</span>" input
-                modules in the "<span class="codefrag">linkrewriter</span>" configuration, we tell
-                "<span class="codefrag">linkrewriter</span>" to use these two input modules when
-                rewriting links.</p>
-            
+<p>
+                By nesting the "<span class="codefrag">site</span>" and "<span class="codefrag">ext</span>" input
+                modules in the "<span class="codefrag">linkrewriter</span>" configuration, we
+                tell "<span class="codefrag">linkrewriter</span>" to use these two input modules
+                when rewriting links.
+              </p>
 </li>
           
 </ul>
@@ -1197,17 +1272,18 @@
             <span class="codefrag">cocoon:/community/linkmap-index.html</span>
           
 </p>
-<a name="N10464"></a><a name="dynamic_linkmap"></a>
+<a name="N10456"></a><a name="dynamic_linkmap"></a>
 <h4>Dynamically generating a linkmap</h4>
 <p>
             Why do we need this "linkmap" pipeline generating dynamic XML from
-            <span class="codefrag">site.xml</span>, instead of just using <span class="codefrag">site.xml</span> directly?  The reasons are described
+            <span class="codefrag">site.xml</span>, instead of just using <span class="codefrag">site.xml</span> directly? The reasons are described
             in <a href="http://marc.theaimsgroup.com/?l=forrest-dev&m=103444028129281&w=2">the linkmap RT</a>: we need to
             concatenate @hrefs and add dot-dots to the paths, depending on which
-            directory the linkee is in.  This is done with the following
+            directory the linkee is in. This is done with the following
             pipelines in <span class="codefrag">linkmap.xmap</span> ...
           </p>
 <pre class="code">
+
 &lt;!-- site.xml with @href's appended to be context-relative. --&gt;
 &lt;map:match pattern="abs-linkmap"&gt;
   &lt;map:generate src="content/xdocs/site.xml" /&gt;
@@ -1224,9 +1300,11 @@
   &lt;/map:transform&gt;
   &lt;map:serialize type="xml" /&gt;
 &lt;/map:match&gt;
-            </pre>
-<p>You can try these URIs out directly on a live Forrest to see what
-            is going on (for example, Forrest's own 
+            
+          </pre>
+<p>
+            You can try these URIs out directly on a live Forrest to see what is
+            going on (for example, Forrest's own
             <a href="../abs-linkmap">abs-linkmap</a>).
           </p>
 </div>

Modified: forrest/site/docs_0_70/sitemap-ref.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_70/sitemap-ref.pdf?view=diff&rev=529915&r1=529914&r2=529915
==============================================================================
Binary files - no diff available.

Modified: forrest/site/docs_0_70/skin-package.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_70/skin-package.html?view=diff&rev=529915&r1=529914&r2=529915
==============================================================================
--- forrest/site/docs_0_70/skin-package.html (original)
+++ forrest/site/docs_0_70/skin-package.html Wed Apr 18 01:36:14 2007
@@ -3,7 +3,7 @@
 <head>
 <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.8-dev">
+<meta name="Forrest-version" content="0.9-dev">
 <meta name="Forrest-skin-name" content="pelt">
 <title>Skin packaging, provision, and use (v0.7)</title>
 <link type="text/css" href="../skin/basic.css" rel="stylesheet">
@@ -87,7 +87,7 @@
     |start Subtabs
     +-->
 <div id="level2tabs">
-<a class="selected" href="../docs_0_70/index.html">0.70 (current)</a><a class="unselected" href="../docs_0_80/index.html">0.80-dev (under development)</a><a class="unselected" href="../docs_0_60/index.html">0.60 (past)</a>
+<a class="unselected" href="../docs_0_80/index.html">0.80 (current)</a><a class="unselected" href="../docs_0_90/index.html">0.90-dev (under development)</a><a class="selected" href="../docs_0_70/index.html">0.70 (past)</a>
 </div>
 <!--+
     |end Endtabs
@@ -100,7 +100,7 @@
     |breadtrail
     +-->
 <div class="breadtrail">
-             
+
              &nbsp;
            </div>
 <!--+
@@ -283,7 +283,7 @@
 </div>
 <div id="credit">
 <hr>
-        This is documentation for current version v0.7
+        This is documentation for past version v0.7
        (<a href="http://forrest.apache.org/versions/">More</a>)</div>
 <div id="roundbottom">
 <img style="display: none" class="corner" height="15" width="15" alt="" src="../skin/images/rc-b-l-15-1body-2menu-3menu.png"></div>
@@ -313,7 +313,7 @@
 <h1>Skin packaging, provision, and use</h1>
 <h3>Automated distributed skin packages</h3>
 <div id="motd-area">
-        This is documentation for current version v0.7
+        This is documentation for past version v0.7
        (<a href="http://forrest.apache.org/versions/">More</a>)</div>
 <div id="minitoc-area">
 <ul class="minitoc">
@@ -330,11 +330,11 @@
 <h2 class="underlined_10">Overview</h2>
 <div class="section">
 <p>
-Skins are standard zip archives with a *.zip extension.
-This enables them to be unpacked and installed automatically.
+        Skins are standard zip archives with a *.zip extension. This enables
+        them to be unpacked and installed automatically.
       </p>
 <p>
-To publish a skin:
+        To publish a skin:
       </p>
 <pre class="code">
 1 - forrest package-skin
@@ -343,7 +343,7 @@
 3 - ask forrest-dev to add the url and the skin name to the list of skins
 </pre>
 <p>
-To use a custom skin with automatic download:
+        To use a custom skin with automatic download:
       </p>
 <pre class="code">
 1 - set the skin property in forrest.properties to the name of the skin
@@ -351,23 +351,22 @@
 3 - forrest
 </pre>
 <p>
-Currently there are two test skins: "testskin" and "testskin2"
+        Currently there are two test skins: "testskin" and "testskin2"
       </p>
 <p>
-To see the names of the remote skins:
+        To see the names of the remote skins:
       </p>
 <pre class="code">forrest available-skins</pre>
 </div>
-
     
 <a name="N10032"></a><a name="notes"></a>
 <h2 class="underlined_10">Notes</h2>
 <div class="section">
 <p>
-The skin will get blown away by the next 'build clean' in forrest.
-But that is okay because it is so quick to go get another copy. Also it
-may be preferable to get a fresh copy. If the user wanted to keep
-the skin and perhaps enhance it, then they can copy it to their project.
+        The skin will get blown away by the next 'build clean' in forrest. But
+        that is okay because it is so quick to go get another copy. Also it may
+        be preferable to get a fresh copy. If the user wanted to keep the skin
+        and perhaps enhance it, then they can copy it to their project.
       </p>
 </div>
   

Modified: forrest/site/docs_0_70/skins.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_70/skins.html?view=diff&rev=529915&r1=529914&r2=529915
==============================================================================
--- forrest/site/docs_0_70/skins.html (original)
+++ forrest/site/docs_0_70/skins.html Wed Apr 18 01:36:14 2007
@@ -3,7 +3,7 @@
 <head>
 <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.8-dev">
+<meta name="Forrest-version" content="0.9-dev">
 <meta name="Forrest-skin-name" content="pelt">
 <title>Default skins (v0.7)</title>
 <link type="text/css" href="../skin/basic.css" rel="stylesheet">
@@ -87,7 +87,7 @@
     |start Subtabs
     +-->
 <div id="level2tabs">
-<a class="selected" href="../docs_0_70/index.html">0.70 (current)</a><a class="unselected" href="../docs_0_80/index.html">0.80-dev (under development)</a><a class="unselected" href="../docs_0_60/index.html">0.60 (past)</a>
+<a class="unselected" href="../docs_0_80/index.html">0.80 (current)</a><a class="unselected" href="../docs_0_90/index.html">0.90-dev (under development)</a><a class="selected" href="../docs_0_70/index.html">0.70 (past)</a>
 </div>
 <!--+
     |end Endtabs
@@ -100,7 +100,7 @@
     |breadtrail
     +-->
 <div class="breadtrail">
-             
+
              &nbsp;
            </div>
 <!--+
@@ -283,7 +283,7 @@
 </div>
 <div id="credit">
 <hr>
-        This is documentation for current version v0.7
+        This is documentation for past version v0.7
        (<a href="http://forrest.apache.org/versions/">More</a>)</div>
 <div id="roundbottom">
 <img style="display: none" class="corner" height="15" width="15" alt="" src="../skin/images/rc-b-l-15-1body-2menu-3menu.png"></div>
@@ -312,7 +312,7 @@
 </div>
 <h1>Default skins</h1>
 <div id="motd-area">
-        This is documentation for current version v0.7
+        This is documentation for past version v0.7
        (<a href="http://forrest.apache.org/versions/">More</a>)</div>
 <div id="minitoc-area">
 <ul class="minitoc">
@@ -362,11 +362,10 @@
         many capabilities so that extra skins are not needed.
       </p>
 <p>
-        Note that the new Dispatcher capability in future versions of
-        Forrest will be a better solution.
+        Note that the new Dispatcher capability in future versions of Forrest
+        will be a better solution.
       </p>
 </div>
-
     
 <a name="N1001A"></a><a name="names"></a>
 <h2 class="underlined_10">Convention for choosing skin names</h2>
@@ -374,13 +373,12 @@
 <p>
         The skin names are based on playing with the word "skin". See our
         technique for
-        <a href="http://svn.apache.org/repos/asf/forrest/trunk/main/webapp/skins/new-skin-names.txt">choosing skin names</a>.
-        A name with "-dev" extension signifies that it is under development.
-        There is no concept of versions of default skins.
-        New skins have new names.
+        <a href="http://svn.apache.org/repos/asf/forrest/trunk/main/webapp/skins/new-skin-names.txt">choosing
+        skin names</a>. A name with "-dev" extension signifies that it is under
+        development. There is no concept of versions of default skins. New skins
+        have new names.
       </p>
 </div>
-
     
 <a name="N10028"></a><a name="skins"></a>
 <h2 class="underlined_10">Skin descriptions and examples</h2>
@@ -390,35 +388,35 @@
 <p>
           Uses CSS "div" and no HTML tables.
         </p>
-<p>Examples:
-          <a href="http://forrest.apache.org/">Apache Forrest</a> |
+<p>
+          Examples: <a href="http://forrest.apache.org/">Apache Forrest</a> |
           <a href="http://lenya.apache.org/">Apache Lenya</a>
         
 </p>
 <a name="N10043"></a><a name="tigris"></a>
 <h3 class="underlined_5">tigris</h3>
 <p>
-          This skin is based on version 1.1 of the 
-          <a href="http://style.tigris.org/">style.tigris.org</a> project.
-          (It deliberately contravenes our skin naming convention.)
+          This skin is based on version 1.1 of the
+          <a href="http://style.tigris.org/">style.tigris.org</a> project. (It
+          deliberately contravenes our skin naming convention.)
         </p>
-<p>Examples:
-          <a href="http://www.core.gen.tr/">Core Computer Security Group</a>
+<p>
+          Examples: <a href="http://www.core.gen.tr/">Core Computer Security
+          Group</a>
         
 </p>
 <a name="N10058"></a><a name="plain-dev"></a>
 <h3 class="underlined_5">plain-dev</h3>
 <p>
-          This is a very minimal skin to produce plain HTML documents.
-          Such capability might be useful to generate a collection of
-          documents for some off-line product's user help system.
+          This is a very minimal skin to produce plain HTML documents. Such
+          capability might be useful to generate a collection of documents for
+          some off-line product's user help system.
         </p>
-<p>Examples:
-          <a href="images/snapshot-plain-dev.png">snapshot</a>
+<p>
+          Examples: <a href="images/snapshot-plain-dev.png">snapshot</a>
         
 </p>
 </div>
-
     
 <a name="N1006A"></a><a name="old"></a>
 <h2 class="underlined_10">Old and deprecated skins</h2>
@@ -433,8 +431,8 @@
           This is the old skin that we have been dragging around since early
           days. Uses HTML tables.
         </p>
-<p>Examples:
-          <a href="http://xml.apache.org/">Apache XML</a>
+<p>
+          Examples: <a href="http://xml.apache.org/">Apache XML</a>
         
 </p>
 <a name="N10084"></a><a name="krysalis-site"></a>
@@ -442,15 +440,16 @@
 <p>
           Uses HTML tables.
         </p>
-<p>Examples:
+<p>
+          Examples:
         </p>
 <a name="N10091"></a><a name="view"></a>
 <h3 class="underlined_5">view/viewHelper</h3>
 <p>
-          This is the evolution of the "leather-dev" skin, to have contracts. 
-          It allows the user to provide their own implementations of contracts.
-          The view is controlled by a config file that is easy to understand.
-          It is still in development. Note: you need to have both plugins installed.
+          This is the evolution of the "leather-dev" skin, to have contracts. It
+          allows the user to provide their own implementations of contracts. The
+          view is controlled by a config file that is easy to understand. It is
+          still in development. Note: you need to have both plugins installed.
         </p>
 <div class="note">
 <div class="label">Note</div>
@@ -458,8 +457,8 @@
           This is now out-of-date. See the new Dispatcher.
         </div>
 </div>
-<p>Examples:
-          <a href="images/snapshot-view-viewHelper.png">snapshot</a>
+<p>
+          Examples: <a href="images/snapshot-view-viewHelper.png">snapshot</a>
         
 </p>
 </div>

Modified: forrest/site/docs_0_70/tab-index.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_70/tab-index.html?view=diff&rev=529915&r1=529914&r2=529915
==============================================================================
--- forrest/site/docs_0_70/tab-index.html (original)
+++ forrest/site/docs_0_70/tab-index.html Wed Apr 18 01:36:14 2007
@@ -15,4 +15,4 @@
 <li>
 <a class="unselected" href="../tools/index.html">Tools</a>
 </li>
-</ul><span id="level2tabs"><a class="selected" href="../docs_0_70/index.html">0.70 (current)</a><a class="unselected" href="../docs_0_80/index.html">0.80-dev (under development)</a><a class="unselected" href="../docs_0_60/index.html">0.60 (past)</a></span>
+</ul><span id="level2tabs"><a class="unselected" href="../docs_0_80/index.html">0.80 (current)</a><a class="unselected" href="../docs_0_90/index.html">0.90-dev (under development)</a><a class="selected" href="../docs_0_70/index.html">0.70 (past)</a></span>

Modified: forrest/site/docs_0_70/todo.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_70/todo.html?view=diff&rev=529915&r1=529914&r2=529915
==============================================================================
--- forrest/site/docs_0_70/todo.html (original)
+++ forrest/site/docs_0_70/todo.html Wed Apr 18 01:36:14 2007
@@ -3,7 +3,7 @@
 <head>
 <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.8-dev">
+<meta name="Forrest-version" content="0.9-dev">
 <meta name="Forrest-skin-name" content="pelt">
 <title>Todo List (v0.7)</title>
 <link type="text/css" href="../skin/basic.css" rel="stylesheet">
@@ -87,7 +87,7 @@
     |start Subtabs
     +-->
 <div id="level2tabs">
-<a class="selected" href="../docs_0_70/index.html">0.70 (current)</a><a class="unselected" href="../docs_0_80/index.html">0.80-dev (under development)</a><a class="unselected" href="../docs_0_60/index.html">0.60 (past)</a>
+<a class="unselected" href="../docs_0_80/index.html">0.80 (current)</a><a class="unselected" href="../docs_0_90/index.html">0.90-dev (under development)</a><a class="selected" href="../docs_0_70/index.html">0.70 (past)</a>
 </div>
 <!--+
     |end Endtabs
@@ -100,7 +100,7 @@
     |breadtrail
     +-->
 <div class="breadtrail">
-             
+
              &nbsp;
            </div>
 <!--+
@@ -283,7 +283,7 @@
 </div>
 <div id="credit">
 <hr>
-        This is documentation for current version v0.7
+        This is documentation for past version v0.7
        (<a href="http://forrest.apache.org/versions/">More</a>)</div>
 <div id="roundbottom">
 <img style="display: none" class="corner" height="15" width="15" alt="" src="../skin/images/rc-b-l-15-1body-2menu-3menu.png"></div>
@@ -312,7 +312,7 @@
 </div>
 <h1>Todo List</h1>
 <div id="motd-area">
-        This is documentation for current version v0.7
+        This is documentation for past version v0.7
        (<a href="http://forrest.apache.org/versions/">More</a>)</div>
 <div id="minitoc-area">
 <ul class="minitoc">
@@ -334,7 +334,7 @@
 <ul>
 <li>
 <strong>[code]</strong> 
-        <!-- Please leave this action at the top -->
+<!-- Please leave this action at the top -->
         Please see our Jira
         <a href="../issues.html">issue tracker</a> for tasks to be done.
         Note that the Todo list below is old. We need someone to move those
@@ -366,8 +366,7 @@
          &rarr; NKB</li>
 </ul>
 </div>
-
-      
+    
 <a name="N1002B"></a><a name="medium"></a>
 <h2 class="underlined_10">medium</h2>
 <div class="section">
@@ -425,15 +424,14 @@
           Develop a mechanism for supporting legacy URLs.
           See email discussion -
           <a href="http://marc.theaimsgroup.com/?l=forrest-dev&m=102390892524750">redirects with static sites</a>
-         &rarr; open</li>
+       &rarr; open</li>
 <li>
 <strong>[code]</strong> 
           Fix up and integrate the Forrest Maven plugin.
          &rarr; open</li>
 </ul>
 </div>
-
-      
+    
 <a name="N10065"></a><a name="low"></a>
 <h2 class="underlined_10">low</h2>
 <div class="section">
@@ -475,8 +473,8 @@
           Add a document about authoring in XML for beginners..
          &rarr; open</li>
 </ul>
-</div>    
-    
+</div>
+  
 </div>
 <!--+
     |end content

Modified: forrest/site/docs_0_70/upgrading_07.html
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_70/upgrading_07.html?view=diff&rev=529915&r1=529914&r2=529915
==============================================================================
--- forrest/site/docs_0_70/upgrading_07.html (original)
+++ forrest/site/docs_0_70/upgrading_07.html Wed Apr 18 01:36:14 2007
@@ -3,7 +3,7 @@
 <head>
 <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.8-dev">
+<meta name="Forrest-version" content="0.9-dev">
 <meta name="Forrest-skin-name" content="pelt">
 <title>Upgrading to Apache Forrest 0.7 (v0.7)</title>
 <link type="text/css" href="../skin/basic.css" rel="stylesheet">
@@ -87,7 +87,7 @@
     |start Subtabs
     +-->
 <div id="level2tabs">
-<a class="selected" href="../docs_0_70/index.html">0.70 (current)</a><a class="unselected" href="../docs_0_80/index.html">0.80-dev (under development)</a><a class="unselected" href="../docs_0_60/index.html">0.60 (past)</a>
+<a class="unselected" href="../docs_0_80/index.html">0.80 (current)</a><a class="unselected" href="../docs_0_90/index.html">0.90-dev (under development)</a><a class="selected" href="../docs_0_70/index.html">0.70 (past)</a>
 </div>
 <!--+
     |end Endtabs
@@ -100,7 +100,7 @@
     |breadtrail
     +-->
 <div class="breadtrail">
-             
+
              &nbsp;
            </div>
 <!--+
@@ -283,7 +283,7 @@
 </div>
 <div id="credit">
 <hr>
-        This is documentation for current version v0.7
+        This is documentation for past version v0.7
        (<a href="http://forrest.apache.org/versions/">More</a>)</div>
 <div id="roundbottom">
 <img style="display: none" class="corner" height="15" width="15" alt="" src="../skin/images/rc-b-l-15-1body-2menu-3menu.png"></div>
@@ -312,7 +312,7 @@
 </div>
 <h1>Upgrading to Apache Forrest 0.7</h1>
 <div id="motd-area">
-        This is documentation for current version v0.7
+        This is documentation for past version v0.7
        (<a href="http://forrest.apache.org/versions/">More</a>)</div>
 <div id="minitoc-area">
 <ul class="minitoc">
@@ -347,35 +347,31 @@
 <a href="#To+be+continued...">To be continued...</a>
 </li>
 </ul>
-</div> 
+</div>
     
 <a name="N1000D"></a><a name="introduction"></a>
 <h2 class="underlined_10">Introduction</h2>
 <div class="section">
 <p>
-      This page describes some changes to Apache Forrest that affect people who are
-      upgrading to the 0.7 version.
-      If you have other issues, then please discuss on either the
-      <a href="../mail-lists.html#forrest-dev">dev</a> or
-      <a href="../mail-lists.html#forrest-user">user</a>
-      mailing lists.
-      As more experience is gained, this document will be updated.  
+        This page describes some changes to Apache Forrest that affect people
+        who are upgrading to the 0.7 version. If you have other issues, then
+        please discuss on either the
+        <a href="../mail-lists.html#forrest-dev">dev</a> or
+        <a href="../mail-lists.html#forrest-user">user</a> mailing lists. As more
+        experience is gained, this document will be updated.
       </p>
 <p>
-      (If you are upgrading from a version prior to 0.6 then you will need
-      to see the notes for the <a href="../docs_0_60/upgrading_06.html">previous</a>
-      upgrade.)
+        (If you are upgrading from a version prior to 0.6 then you will need to
+        see the notes for the previous upgrade.)
       </p>
 </div>
-
     
-<a name="N10026"></a><a name="new"></a>
+<a name="N10022"></a><a name="new"></a>
 <h2 class="underlined_10">New Features</h2>
 <div class="section">
 <p>
-        The following list shows some of the key new features
-        (for the full list of changes, see the
-        <a href="../docs_0_80/changes.html">change log</a>).
+        The following list shows some of the key new features (for the full list
+        of changes, see the <a href="../docs_0_90/changes.html">change log</a>).
       </p>
 <ul>
         
@@ -389,116 +385,108 @@
         forrest.properties and skinconf.xml with that of your project.
       </p>
 </div>
-
     
-<a name="N10040"></a><a name="clean"></a>
+<a name="N1003C"></a><a name="clean"></a>
 <h2 class="underlined_10">Run a clean target after upgrade</h2>
 <div class="section">
 <p>
-        Do 'forrest clean-work' in each of your projects. This also removes
-        the old Cocoon disk cache.
+        Do 'forrest clean-work' in each of your projects. This also removes the
+        old Cocoon disk cache.
       </p>
 </div>
-
     
-<a name="N1004A"></a><a name="home"></a>
+<a name="N10046"></a><a name="home"></a>
 <h2 class="underlined_10">New location of $FORREST_HOME</h2>
 <div class="section">
 <p>
-      $FORREST_HOME is now the top-level of the distribution.
-      Also make sure $PATH gets updated to use the new $FORREST_HOME/bin
+        $FORREST_HOME is now the top-level of the distribution. Also make sure
+        $PATH gets updated to use the new $FORREST_HOME/bin
       </p>
 </div>
-
     
-<a name="N10054"></a><a name="jdk14"></a>
+<a name="N10050"></a><a name="jdk14"></a>
 <h2 class="underlined_10">Java 1.4 (or newer) is required</h2>
 <div class="section">
-<p>Java 1.4 (or newer) is required, starting with this Forrest 0.7 version.
-        For further information, see <a href="../docs_0_70/faq.html#requirements">FAQ</a>.
+<p>
+        Java 1.4 (or newer) is required, starting with this Forrest 0.7 version.
+        For further information, see
+        <a href="../docs_0_70/faq.html#requirements">FAQ</a>.
       </p>
 </div>
-
     
-<a name="N10062"></a><a name="tips"></a>
+<a name="N1005E"></a><a name="tips"></a>
 <h2 class="underlined_10">General upgrade tips</h2>
 <div class="section">
 <p>
-      Synchronise your project's skinconf.xml and forrest.properties files.
+        Synchronise your project's skinconf.xml and forrest.properties files.
       </p>
 <p>
-      Take advantage of the separation of concerns. In a new workspace,
-      create a fresh
-      '<span class="codefrag">forrest seed</span>' site, then tweak its forrest.properties
-      and skinconf.xml until it reflects your old site.
-      When it is ready, replace your project's skinconf.xml and
-      forrest.properties files.
-      Any remaining issues would concern other aspects of your configuration,
-      such as site.xml and your actual content.
+        Take advantage of the separation of concerns. In a new workspace, create
+        a fresh '<span class="codefrag">forrest seed</span>' site, then tweak its
+        forrest.properties and skinconf.xml until it reflects your old site.
+        When it is ready, replace your project's skinconf.xml and
+        forrest.properties files. Any remaining issues would concern other
+        aspects of your configuration, such as site.xml and your actual content.
       </p>
 </div>
-
     
-<a name="N10072"></a><a name="plugin"></a>
+<a name="N1006E"></a><a name="plugin"></a>
 <h2 class="underlined_10">Plugin architecture</h2>
 <div class="section">
 <p>
-        See
-        <a href="../pluginDocs/plugins_0_80/pluginInfrastructure.html">Plugin Infrastructure</a>
-        and
-        <a href="../pluginDocs/plugins_0_80/usingPlugins.html">Extending Forrest with Plugins</a>
-        and for developing new plugins see
-        <a href="../docs_0_70/howto/howto-buildPlugin.html">How to Build a Plugin</a>.
-        See the list of
-        <a href="../pluginDocs/plugins_0_80/index.html">current plugins</a>
-        and their documentation.
+        See <a href="../pluginDocs/plugins_0_90/pluginInfrastructure.html">Plugin Infrastructure</a> and
+        <a href="../pluginDocs/plugins_0_90/usingPlugins.html">Extending Forrest with Plugins</a> and for
+        developing new plugins see <a href="../docs_0_70/howto/howto-buildPlugin.html">How
+        to Build a Plugin</a>. See the list of
+        <a href="../pluginDocs/plugins_0_90/index.html">current plugins</a> and their
+        documentation.
       </p>
 <p>
         Note that other experimental plugins can be found in the
         "whiteboard/plugins" directory.
       </p>
 </div>
-
     
-<a name="N1008F"></a><a name="configure-plugin"></a>
+<a name="N1008B"></a><a name="configure-plugin"></a>
 <h2 class="underlined_10">Configure plugins</h2>
 <div class="section">
 <p>
-       Some functionality has been moved out of the forrest core and into
-       plugins. You will need to declare any plugins that are used by
-       your project, e.g. if you use projectInfo (status, changes, todo)
-       and PDF output, then declare the following in forrest.properties
+        Some functionality has been moved out of the forrest core and into
+        plugins. You will need to declare any plugins that are used by your
+        project, e.g. if you use projectInfo (status, changes, todo) and PDF
+        output, then declare the following in forrest.properties
       </p>
 <pre class="code">
 project.required.plugins=org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.output.pdf
       </pre>
 </div>
-
     
-<a name="N1009D"></a><a name="raw"></a>
+<a name="N10099"></a><a name="raw"></a>
 <h2 class="underlined_10">Including raw un-processed content</h2>
 <div class="section">
-<p>The method for including "raw un-processed content" has changed.
+<p>
+        The method for including "raw un-processed content" has changed.
       </p>
 <p>
         In 0.6 version, the raw content was placed in the
-        src/documentation/content/ directory and potential sub-directories.
-        In the generated site, these links would automatically function.
-        Any linked file with .html extension was not processed and not
-        adorned with Forrest skin and navigation menus.
-      </p>
-<p>It was also possible to place HTML content in the xdocs directory
-      where it would be copied across if it was linked from the main
-      content.</p>
-<p>
-        In 0.7 version, any file that is linked to, needs to be placed in
-        the content/xdocs/ directory structure.
-        Any linked file with .html extension is now processed and is
-        adorned with Forrest skin and navigation menus.
-      </p>
-<p>If you 
-        you wish to emulate the behaviour of 0.6 and earlier then you
-        must add the following to your project sitemap.</p>
+        src/documentation/content/ directory and potential sub-directories. In
+        the generated site, these links would automatically function. Any linked
+        file with .html extension was not processed and not adorned with Forrest
+        skin and navigation menus.
+      </p>
+<p>
+        It was also possible to place HTML content in the xdocs directory where
+        it would be copied across if it was linked from the main content.
+      </p>
+<p>
+        In 0.7 version, any file that is linked to, needs to be placed in the
+        content/xdocs/ directory structure. Any linked file with .html extension
+        is now processed and is adorned with Forrest skin and navigation menus.
+      </p>
+<p>
+        If you you wish to emulate the behaviour of 0.6 and earlier then you
+        must add the following to your project sitemap.
+      </p>
 <pre class="code">
 &lt;map:match pattern="**.html"&gt;
  &lt;map:select type="exists"&gt;
@@ -522,19 +510,18 @@
 &lt;/map:match&gt;
         </pre>
 <p>
-        If you need to include files that are not linked to,
-        then place them in the src/documentation/content/ directories
-        as with the 0.6 version. 
+        If you need to include files that are not linked to, then place them in
+        the src/documentation/content/ directories as with the 0.6 version.
       </p>
 </div>
-
     
-<a name="N100BA"></a><a name="To+be+continued..."></a>
+<a name="N100B6"></a><a name="To+be+continued..."></a>
 <h2 class="underlined_10">To be continued...</h2>
 <div class="section">
-<p>...as more issues are discovered/remembered :)  Please send feedback
-      to the
-      <a href="../mail-lists.html#forrest-dev">mailing list</a>.</p>
+<p>
+        ...as more issues are discovered/remembered :) Please send feedback to
+        the <a href="../mail-lists.html#forrest-dev">mailing list</a>.
+      </p>
 </div>
   
 </div>

Modified: forrest/site/docs_0_70/upgrading_07.pdf
URL: http://svn.apache.org/viewvc/forrest/site/docs_0_70/upgrading_07.pdf?view=diff&rev=529915&r1=529914&r2=529915
==============================================================================
Binary files - no diff available.



Mime
View raw message