forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r357603 [4/11] - in /forrest/site: ./ docs_0_60/ docs_0_60/howto/ docs_0_60/howto/bugzilla-patch/ docs_0_70/ docs_0_70/howto/ docs_0_70/howto/cvs-ssh/ docs_0_80/ docs_0_80/howto/ docs_0_80/howto/cvs-ssh/ dtdx/ pluginDocs/plugins_0_70/ plugi...
Date Mon, 19 Dec 2005 01:33:15 GMT
Modified: forrest/site/docs_0_70/forrest-contract.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/forrest-contract.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/forrest-contract.html (original)
+++ forrest/site/docs_0_70/forrest-contract.html Sun Dec 18 17:31:25 2005
@@ -342,10 +342,10 @@
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-      Some terminology will assist: <span class="codefrag ">{docroot}</span> is the location
+      Some terminology will assist: <span class="codefrag">{docroot}</span> is the location
       inside TheProject's file hierarchy where all documentation related
-      resources are stored. Usually <span class="codefrag ">{docroot}</span> equals to
-      <span class="codefrag ">{projecthome}/src/documentation</span>
+      resources are stored. Usually <span class="codefrag">{docroot}</span> equals to
+      <span class="codefrag">{projecthome}/src/documentation</span>
     
 </div>
 </div> 
@@ -378,17 +378,17 @@
 <p>Provide content and configuration ...</p>
 <ul> 
         
-<li>Provide XML content in <span class="codefrag ">{docroot}/content/xdocs</span>
+<li>Provide XML content in <span class="codefrag">{docroot}/content/xdocs</span>
           according to the Forrest DTDs or one of the other input formats.
         </li> 
         
 <li>Provide navigation metadata using the configuration files
-          <span class="codefrag ">site.xml</span> and <span class="codefrag ">tabs.xml</span>
+          <span class="codefrag">site.xml</span> and <span class="codefrag">tabs.xml</span>
         
 </li>
         
 <li>Provide the skin configuation file in
-          <span class="codefrag ">{projecthome}/skinconf.xml</span>
+          <span class="codefrag">{projecthome}/skinconf.xml</span>
         
 </li>
       
@@ -403,13 +403,13 @@
 <ul> 
         
 <li>Provide its own skin in
-          <span class="codefrag ">{docroot}/skins/{your-skin-name}</span> (Check the current
+          <span class="codefrag">{docroot}/skins/{your-skin-name}</span> (Check the current
           Forrest skins and the related pipelines to see what they are doing.
           Bear in mind that the provided skins are able to be configured and
           may already meet your needs.)</li> 
         
 <li>Provide own DTDs to handle other specialised document types in
-          <span class="codefrag ">{docroot}/resources/schema/dtd</span> 
+          <span class="codefrag">{docroot}/resources/schema/dtd</span> 
           
 <ul> 
             
@@ -417,7 +417,7 @@
               intermediate 'document' structure.</li> 
             
 <li>and declare those extra DTDs in
-              <span class="codefrag ">{docroot}/resources/schema/catalog.xcat</span>
+              <span class="codefrag">{docroot}/resources/schema/catalog.xcat</span>
 </li> 
           
 </ul>
@@ -425,7 +425,7 @@
 </li> 
         
 <li>Provide its own overwriting versions of sitemaps
-          (<span class="codefrag ">{docroot}/sitemap.xmap</span> and other *.xmap files)
+          (<span class="codefrag">{docroot}/sitemap.xmap</span> and other *.xmap files)
           ... (be sure you know what you are doing since you are then leaving
           the area where other Forresters can help you out.
         </li> 

Modified: forrest/site/docs_0_70/howto/cvs-ssh/howto-cvs-ssh.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/cvs-ssh/howto-cvs-ssh.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/howto/cvs-ssh/howto-cvs-ssh.html (original)
+++ forrest/site/docs_0_70/howto/cvs-ssh/howto-cvs-ssh.html Sun Dec 18 17:31:25 2005
@@ -257,7 +257,7 @@
 <div class="label">Note</div>
 <div class="content">This step is necessary only for Windows users. Linux users can happily skip this section and pass to <a href="#ssh_access">Setting up SSH access</a> section</div>
 </div>
-<p>If you are a domain user then you should be added to Cygwin users list (See <span class="codefrag ">[cygwin-dir]/etc/passwd</span>). 
+<p>If you are a domain user then you should be added to Cygwin users list (See <span class="codefrag">[cygwin-dir]/etc/passwd</span>). 
             </p>
 <ul>
               
@@ -305,7 +305,7 @@
     </p>
 <div class="warning">
 <div class="label">Warning</div>
-<div class="content">Having an empty passphrase isn't recommended for security reasons. See <span class="codefrag ">ssh-agent</span> documentation on how to configure automatic passphrase retaining.</div>
+<div class="content">Having an empty passphrase isn't recommended for security reasons. See <span class="codefrag">ssh-agent</span> documentation on how to configure automatic passphrase retaining.</div>
 </div>
 <a name="N100B2"></a><a name="Setting+up+passphrase+access"></a>
 <h3 class="underlined_5">Setting up passphrase access</h3>
@@ -332,7 +332,7 @@
             </pre>
 <div class="note">
 <div class="label">Note</div>
-<div class="content">If this command doesn't work then it can mean that you have an old version of SSH. In this case try <span class="codefrag ">ssh -l userxxx cvs.apache.org</span>. Run <span class="codefrag ">ssh --help</span> to get all available options.</div>
+<div class="content">If this command doesn't work then it can mean that you have an old version of SSH. In this case try <span class="codefrag">ssh -l userxxx cvs.apache.org</span>. Run <span class="codefrag">ssh --help</span> to get all available options.</div>
 </div>
 <p>
             If now you are logged in to the to the CVS machine without entering the password then everything's Ok.
@@ -351,10 +351,10 @@
                 
 <li>Add ssh.exe directory to your system PATH environment variable. Say: <br>
                 
-<span class="codefrag ">C:\&gt;set PATH=%PATH%;C:\cygwin\bin</span>
+<span class="codefrag">C:\&gt;set PATH=%PATH%;C:\cygwin\bin</span>
 </li>
                 
-<li>Add <span class="codefrag ">CVS_RSH=ssh</span> environment variable</li>
+<li>Add <span class="codefrag">CVS_RSH=ssh</span> environment variable</li>
             
 </ul>
 <p>
@@ -369,7 +369,7 @@
 </li>
                 
 <li>In the dialog that comes up: <br>
-                Set the CVSROOT to <span class="codefrag ">userxxx@cvs.apache.org:/home/cvs</span>
+                Set the CVSROOT to <span class="codefrag">userxxx@cvs.apache.org:/home/cvs</span>
 </li>
                 
 <li>Set the Authentication to SSH Server</li>                

Modified: forrest/site/docs_0_70/howto/howto-asf-mirror.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/howto-asf-mirror.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/howto/howto-asf-mirror.html (original)
+++ forrest/site/docs_0_70/howto/howto-asf-mirror.html Sun Dec 18 17:31:25 2005
@@ -411,10 +411,10 @@
 <h3 class="underlined_5">Add the mirrors.cgi as a raw file</h3>
 <p>As explained in the mirrors document, there will be a two-line CGI
       wrapper script at the top-level of your website called
-      <span class="codefrag ">mirrors.cgi</span>
+      <span class="codefrag">mirrors.cgi</span>
 </p>
 <p>Utilising the Forrest concept of raw un-processed content,
-       add the file as <span class="codefrag ">src/documentation/mirrors.cgi</span>
+       add the file as <span class="codefrag">src/documentation/mirrors.cgi</span>
        (copy the Forrest project's
         <a href="http://svn.apache.org/repos/asf/forrest/trunk/site-author/content/mirrors.cgi">mirrors.cgi</a>)
       </p>
@@ -426,7 +426,7 @@
         script to add the list of mirrors and select the closest.
       </p>
 <p>
-        Add the file as <span class="codefrag ">src/documentation/xdocs/mirrors.html</span>
+        Add the file as <span class="codefrag">src/documentation/xdocs/mirrors.html</span>
         (Use the Forrest project's
         <a href="http://svn.apache.org/repos/asf/forrest/trunk/site-author/content/xdocs/mirrors.html">mirrors.html</a>
         as a template and edit it to suit.)
@@ -457,8 +457,8 @@
         (<a href="http://cocoon.apache.org/2.1/userdocs/offline/">CLI</a>)
         to the rescue. Add an entry to your project's cli.xconf by copying the
         default one from
-        <span class="codefrag ">$FORREST_HOME/main/webapp/WEB-INF/cli.xconf</span> to your
-        <span class="codefrag ">src/documentation/conf/</span> directory (or wherever
+        <span class="codefrag">$FORREST_HOME/main/webapp/WEB-INF/cli.xconf</span> to your
+        <span class="codefrag">src/documentation/conf/</span> directory (or wherever
         ${forrest.conf-dir} points). Add the following entry ...
       </p>
 <pre class="code">
@@ -469,7 +469,7 @@
 <h3 class="underlined_5">Run 'forrest' to build your site</h3>
 <p>
         That is all that you need to do, Forrest will take care of it from
-        there. Run the '<span class="codefrag ">forrest</span>' command. The mirrors.html page
+        there. Run the '<span class="codefrag">forrest</span>' command. The mirrors.html page
         will be generated with the skin applied.
       </p>
 <div class="note">

Modified: forrest/site/docs_0_70/howto/howto-buildPlugin.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/howto-buildPlugin.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/howto/howto-buildPlugin.html (original)
+++ forrest/site/docs_0_70/howto/howto-buildPlugin.html Sun Dec 18 17:31:25 2005
@@ -462,7 +462,7 @@
         to automate some steps in the process. Since ant
         is distributed as part of Forrest, all you need to do
         is add the ant executable directory to your system path. The
-        name of this directory is <span class="codefrag ">tools/ant/bin</span>
+        name of this directory is <span class="codefrag">tools/ant/bin</span>
         in your Forrest program directory.
         (Alternatively you can prefix all calls to ant in
         the following instructions with the full path of the ant binary directory.)
@@ -481,7 +481,7 @@
       structure is almost identical, as are most of the requried
       configuration files. In this How-To we will assume that you are creating a 
       plugin in the Forrest source tree. All plugins are developed in the
-      <span class="codefrag ">forrest/plugins</span> directory.</p>
+      <span class="codefrag">forrest/plugins</span> directory.</p>
 <p class="instruction">Run the following set of commands:</p>
 <pre class="code">
       cd [path_to_forrest]/plugins
@@ -500,7 +500,7 @@
 <div class="note">
 <div class="label">Note</div>
 <div class="content">If you plan on building your plugin elsewhere you can copy the
-      <span class="codefrag ">build.xml</span> build file to your own plugin work directory and 
+      <span class="codefrag">build.xml</span> build file to your own plugin work directory and 
       use it there.</div>
 </div>
 <p>See 
@@ -525,7 +525,7 @@
 <h5>status.xml</h5>
 <p>This file is used to track changes to the plugin
           project and to manage lists of things that still need to be done.
-          At this stage you should correct the <span class="codefrag ">person</span> entry
+          At this stage you should correct the <span class="codefrag">person</span> entry
           near the top of the file. It is also a good idea to add a few key
           milestones in the task list towards the bottom of the file.</p>
 <p>As you work on the plugin you should record all major changes in
@@ -557,13 +557,13 @@
           </p>
 <a name="N100E9"></a><a name="edit-sitemap"></a>
 <h3 class="underlined_5">Edit the Plugin sitemap file(s)</h3>
-<p>The plugin <span class="codefrag ">xmap</span> file is a Cocoon sitemap that is mounted
+<p>The plugin <span class="codefrag">xmap</span> file is a Cocoon sitemap that is mounted
       at a strategic place in the Forrest pipeline. It is in this file
       that you will instruct Forrest how to operate. An input plugin
-      must provide a <span class="codefrag ">input.xmap</span> file, an output plugin
-      must provide a <span class="codefrag ">output.xmap</span> file, whilst an internal
-      plugin provides a <span class="codefrag ">internal.xmap</span> file. In addition, an
-      input plugin may provide a <span class="codefrag ">resources.xmap</span> file to
+      must provide a <span class="codefrag">input.xmap</span> file, an output plugin
+      must provide a <span class="codefrag">output.xmap</span> file, whilst an internal
+      plugin provides a <span class="codefrag">internal.xmap</span> file. In addition, an
+      input plugin may provide a <span class="codefrag">resources.xmap</span> file to
       allow the plugin to handle items such as JavaScript files.</p>
 <p>It is beyond the scope of this How-To to give details about how to 
       build your plugins XMap. See the 
@@ -579,14 +579,14 @@
 <p>If your plugin uses any components (i.e. generators, transformers or
         serializers), actions or resources they must
         be defined in either the xmap for this plugin or one of its parents. The parents
-        of an <span class="codefrag ">input.xmap</span> are <span class="codefrag ">sitemap.xmap</span> and
-        <span class="codefrag ">forrest.xmap</span>, whilst the parent of both 
-        <span class="codefrag ">output.xmap</span> and <span class="codefrag ">internal.xmap</span> are 
-        <span class="codefrag ">sitemap.xmap</span>
+        of an <span class="codefrag">input.xmap</span> are <span class="codefrag">sitemap.xmap</span> and
+        <span class="codefrag">forrest.xmap</span>, whilst the parent of both 
+        <span class="codefrag">output.xmap</span> and <span class="codefrag">internal.xmap</span> are 
+        <span class="codefrag">sitemap.xmap</span>
 </p>
 <p>If you want to use the realpath where the sitemap.xmap of your plugin 
         resides then you need to use 
-        <span class="codefrag ">{forrest:plugins}/PLUGIN_NAME</span> instead of <span class="codefrag ">{realpath:/}</span>.
+        <span class="codefrag">{forrest:plugins}/PLUGIN_NAME</span> instead of <span class="codefrag">{realpath:/}</span>.
         </p>
 <p>See the examples below for more details.</p>
 <a name="N10138"></a><a name="resources"></a>
@@ -600,9 +600,9 @@
 <p>Plugin documentation should provide (as a minimum) an
       index page that provides an overview and a set of samples that demonstrate
       the functionality of the plugin. Typically these samples will be
-      provided in a <span class="codefrag ">samples</span> subdirectory in the plugin 
-      documentation and will be referenced from both <span class="codefrag ">site.xml</span>
-      and <span class="codefrag ">tabs.xml</span> configuration files.</p>
+      provided in a <span class="codefrag">samples</span> subdirectory in the plugin 
+      documentation and will be referenced from both <span class="codefrag">site.xml</span>
+      and <span class="codefrag">tabs.xml</span> configuration files.</p>
 <p>Try to provide a sample for all the major functions of your plugin
       and document any configuration that is available.</p>
 <a name="N10159"></a><a name="test"></a>
@@ -610,21 +610,21 @@
 <p>Since your documentation for the plugin illustrates all of its 
       functionality, you can use that site for testing the plugin. However, you
       must first deploy in your local install of Forrest. Each plugin contains
-      a buildfile that includes a <span class="codefrag ">test</span> target. This target, by
+      a buildfile that includes a <span class="codefrag">test</span> target. This target, by
       default, builds the documentation for your plugin.</p>
-<p class="instruction">Run the command <span class="codefrag ">ant test</span> in
+<p class="instruction">Run the command <span class="codefrag">ant test</span> in
       the plugins directory.</p>
 <p>Of course, the build should complete without errors.</p>
 <div class="note">
 <div class="label">Note</div>
-<div class="content">You can also use <span class="codefrag ">forrest run</span> to interactively examine
+<div class="content">You can also use <span class="codefrag">forrest run</span> to interactively examine
       your documentation (point your browser at 
       <a href="http://localhost:8888">http://localhost:8888</a>).</div>
 </div>
 <p>It is also a really good idea to build proper tests for your 
       plugins using a suitable testing framework, for example, 
       <a href="http://webtest.canoo.com/">WebTest</a>. We recommend that you
-      extend the <span class="codefrag ">test</span> target in your plugins build file because
+      extend the <span class="codefrag">test</span> target in your plugins build file because
       this target is also used when performing integration tests on Forrest.
       In addition, we recommend that you use the samples in your documentation 
       for your tests, this way you are documenting your plugin at the same time 
@@ -648,28 +648,28 @@
 <h4>Deploying the Plugin</h4>
 <p>To deploy the plugin so that others can use it, it must be made 
         available as a zip from the URL indicated in the 
-        <span class="codefrag ">plugins.xml</span> file. The plugins build file provides targets 
+        <span class="codefrag">plugins.xml</span> file. The plugins build file provides targets 
         to assist with this task.</p>
 <p class="instruction">To deploy a plugin simply run the command
-        <span class="codefrag ">ant deploy</span> from within the plugin directory.</p>
+        <span class="codefrag">ant deploy</span> from within the plugin directory.</p>
 <p>This command will, by default, deploy to the Apache Forrest web site.
         In order to do this you need commit access to Forrest. If you want to
         deploy your plugin to a different location you 
-        can build the zip of your plugin with <span class="codefrag ">ant dist</span>
-        and then copy the zip file from <span class="codefrag ">build/dist</span> to wherever
+        can build the zip of your plugin with <span class="codefrag">ant dist</span>
+        and then copy the zip file from <span class="codefrag">build/dist</span> to wherever
         you intend to host the plugin.</p>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">Running this command on any plugin will also deploy any
-        changes to the <span class="codefrag ">plugins.xml</span> file. If you are deploying to
+        changes to the <span class="codefrag">plugins.xml</span> file. If you are deploying to
         your own website you will have to request changes to the 
-        <span class="codefrag ">plugins.xml</span> and ask the Forrest committers to publish the new
+        <span class="codefrag">plugins.xml</span> and ask the Forrest committers to publish the new
         document.</div>
 </div>
 <div class="warning">
 <div class="label">Warning</div>
-<div class="content">Running the <span class="codefrag ">deploy</span> or <span class="codefrag ">dist</span> targets
-        will always run the <span class="codefrag ">test</span> target first. This is to ensure
+<div class="content">Running the <span class="codefrag">deploy</span> or <span class="codefrag">dist</span> targets
+        will always run the <span class="codefrag">test</span> target first. This is to ensure
         that your only deploy working plugins. This adds a little time to
         the deploy cycle, but we feel the peace of mind is worth it.</div>
 </div>

Modified: forrest/site/docs_0_70/howto/howto-corner-images.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/howto-corner-images.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/howto/howto-corner-images.html (original)
+++ forrest/site/docs_0_70/howto/howto-corner-images.html Sun Dec 18 17:31:25 2005
@@ -389,7 +389,7 @@
       The procedure outlined below provides an understanding of how corner
       images are named (the contract) and then shows how to define new
       colors for these images by modifying the
-      <span class="codefrag ">src/documentation/skinconf.xml</span> of a project.
+      <span class="codefrag">src/documentation/skinconf.xml</span> of a project.
     </p>
 <a name="N10048"></a><a name="css-files"></a>
 <h3 class="underlined_5">Understand how corner images are named (the contract)</h3>
@@ -419,13 +419,13 @@
       </pre>
 <p>
         The first part
-        (<span class="codefrag ">images/{$name}-{$v-orientation}-{$h-orientation}-{$size}</span>)
+        (<span class="codefrag">images/{$name}-{$v-orientation}-{$h-orientation}-{$size}</span>)
         identifies which images is used and how big (width x height) it should
         be. The second part\
-        (<span class="codefrag ">-1{$backgroundColor}-2{$strokeColor}-3{$foregroundColor}</span>)
+        (<span class="codefrag">-1{$backgroundColor}-2{$strokeColor}-3{$foregroundColor}</span>)
         identifies the coloring of each portion of the image. The input
         parameter for the second part comes from the color profile of
-        <span class="codefrag ">src/documentation/skinconf.xml</span>. The second part is
+        <span class="codefrag">src/documentation/skinconf.xml</span>. The second part is
         easily identifiable through the numbering 1-2-3.
       </p>
 <p>
@@ -434,19 +434,19 @@
 <dl>
         
 <dt>
-<span class="codefrag ">images</span>
+<span class="codefrag">images</span>
 </dt>
         
 <dd>
           Path to the xslt that creates the corner.
           <br>
           
-<span class="codefrag ">images/ = {$FORREST_HOME}/main/webapp/skins/common/images/</span>
+<span class="codefrag">images/ = {$FORREST_HOME}/main/webapp/skins/common/images/</span>
         
 </dd>
         
 <dt>
-<span class="codefrag ">{$name}</span>
+<span class="codefrag">{$name}</span>
 </dt>
         
 <dd>
@@ -455,108 +455,108 @@
             
 <li>
               
-<span class="codefrag ">rc.svg.xslt</span>: handles rounded corners
+<span class="codefrag">rc.svg.xslt</span>: handles rounded corners
             </li>
             
 <li>
               
-<span class="codefrag ">dc.svg.xslt</span>: handles diagonal 45-degree corners
+<span class="codefrag">dc.svg.xslt</span>: handles diagonal 45-degree corners
             </li>
           
 </ul>
           
-<span class="codefrag ">name = [rc|dc]</span>
+<span class="codefrag">name = [rc|dc]</span>
           
 <br>
           
-<em>e.g.</em> <span class="codefrag ">rc</span>
+<em>e.g.</em> <span class="codefrag">rc</span>
         
 </dd>
         
 <dt>
-<span class="codefrag ">{$v-orientation}</span>
+<span class="codefrag">{$v-orientation}</span>
 </dt>
         
 <dd>
           Vertical orientation of the corner images (top or bottom).
           <br>
           
-<span class="codefrag ">v-orientation = [t|b]</span>
+<span class="codefrag">v-orientation = [t|b]</span>
           
 <br>
           
-<em>e.g.</em> <span class="codefrag ">t</span>
+<em>e.g.</em> <span class="codefrag">t</span>
         
 </dd>
         
 <dt>
-<span class="codefrag ">{$h-orientation}</span>
+<span class="codefrag">{$h-orientation}</span>
 </dt>
         
 <dd>
           Horizontal orientation of the corner images (left or right).
           <br>
           
-<span class="codefrag ">h-orientation = [l|r]</span>
+<span class="codefrag">h-orientation = [l|r]</span>
           
 <br>
           
-<em>e.g.</em> <span class="codefrag ">r</span>
+<em>e.g.</em> <span class="codefrag">r</span>
         
 </dd>
         
 <dt>
-<span class="codefrag ">{$size}</span>
+<span class="codefrag">{$size}</span>
 </dt>
         
 <dd>
           Pixels size of the width <strong>and</strong> height of the corner image.
           <br>
           
-<span class="codefrag ">size=x</span>
+<span class="codefrag">size=x</span>
           
 <br>
           
-<em>e.g.</em> <span class="codefrag ">5</span>
+<em>e.g.</em> <span class="codefrag">5</span>
         
 </dd>
         
 <dt>
-<span class="codefrag ">{$backgroundColor}</span>
+<span class="codefrag">{$backgroundColor}</span>
 </dt>
         
 <dd>
-          Any <span class="codefrag ">&lt;color name=""/&gt;</span> element in the <span class="codefrag ">skinconf.xml</span> (the <span class="codefrag ">value="{$color}"</span>
+          Any <span class="codefrag">&lt;color name=""/&gt;</span> element in the <span class="codefrag">skinconf.xml</span> (the <span class="codefrag">value="{$color}"</span>
           attribute will be applied).
           <br>
           
-<em>e.g.</em> <span class="codefrag ">header</span>
+<em>e.g.</em> <span class="codefrag">header</span>
         
 </dd>
         
 <dt>
-<span class="codefrag ">{$strokeColor}</span>
+<span class="codefrag">{$strokeColor}</span>
 </dt>
         
 <dd>
-          Any <span class="codefrag ">&lt;color name=""/&gt;</span> element in the <span class="codefrag ">skinconf.xml</span> (the <span class="codefrag ">value="{$color}"</span>
+          Any <span class="codefrag">&lt;color name=""/&gt;</span> element in the <span class="codefrag">skinconf.xml</span> (the <span class="codefrag">value="{$color}"</span>
           attribute will be applied).
           <br>
           
-<em>e.g.</em> <span class="codefrag ">searchbox</span>
+<em>e.g.</em> <span class="codefrag">searchbox</span>
         
 </dd>
         
 <dt>
-<span class="codefrag ">{$foregroundColor}</span>
+<span class="codefrag">{$foregroundColor}</span>
 </dt>
         
 <dd>
-          Any <span class="codefrag ">&lt;color name=""/&gt;</span> element in the <span class="codefrag ">skinconf.xml</span> (the <span class="codefrag ">value="{$color}"</span>
+          Any <span class="codefrag">&lt;color name=""/&gt;</span> element in the <span class="codefrag">skinconf.xml</span> (the <span class="codefrag">value="{$color}"</span>
           attribute will be applied).
           <br>
           
-<em>e.g.</em> <span class="codefrag ">searchbox</span>
+<em>e.g.</em> <span class="codefrag">searchbox</span>
         
 </dd>
       
@@ -564,12 +564,12 @@
 <a name="N10123"></a><a name="skinconfig"></a>
 <h3 class="underlined_5">Modifying the skinconf.xml of your project</h3>
 <p>
-        modifying the <span class="codefrag ">skinconf.xml</span> of your project (by
-        default you find it at <span class="codefrag ">[project-dir]/src/documentation/</span>).
+        modifying the <span class="codefrag">skinconf.xml</span> of your project (by
+        default you find it at <span class="codefrag">[project-dir]/src/documentation/</span>).
       </p>
 <p>
-        Starting about line 155 you find a <span class="codefrag ">&lt;colors&gt;</span>
-        ... <span class="codefrag ">&lt;/colors&gt;</span> element with content commented-out:
+        Starting about line 155 you find a <span class="codefrag">&lt;colors&gt;</span>
+        ... <span class="codefrag">&lt;/colors&gt;</span> element with content commented-out:
       </p>
 <pre class="code">
 &lt;colors&gt;
@@ -592,8 +592,8 @@
       </pre>
 <p>
         To modify the colors of the corner images, you can either define
-        your own <span class="codefrag ">&lt;color name=.../&gt;</span> elements or uncomment
-        one of the existing <span class="codefrag ">&lt;color name=.../&gt;</span> elements
+        your own <span class="codefrag">&lt;color name=.../&gt;</span> elements or uncomment
+        one of the existing <span class="codefrag">&lt;color name=.../&gt;</span> elements
         and adjust the color value to your needs.
       </p>
 <p>
@@ -605,10 +605,10 @@
 &lt;color name="tab-selected" value="#FF0000"/&gt;
       </pre>
 <p>
-        This affects all corner images whose <span class="codefrag ">{$backgroundColor}</span>, <span class="codefrag ">{$strokeColor}</span> or
-        <span class="codefrag ">{$foregroundColor}</span> is set to <span class="codefrag ">tab-selected</span>.
+        This affects all corner images whose <span class="codefrag">{$backgroundColor}</span>, <span class="codefrag">{$strokeColor}</span> or
+        <span class="codefrag">{$foregroundColor}</span> is set to <span class="codefrag">tab-selected</span>.
         <br>
-        For example, in <span class="codefrag ">screen.css</span> (of the "pelt" skin) you find:
+        For example, in <span class="codefrag">screen.css</span> (of the "pelt" skin) you find:
       </p>
 <pre class="code">
 #roundbottomsmall {
@@ -618,15 +618,15 @@
 }
       </pre>
 <p>
-        Now the stroke color (<span class="codefrag ">-2tab-selected</span>) and the foreground
-        color (<span class="codefrag ">-3tab-selected</span>) are set to red (remember: we
-        defined <span class="codefrag ">#FF0000</span> as the "color" value of
-        <span class="codefrag ">tab-selected</span>).
+        Now the stroke color (<span class="codefrag">-2tab-selected</span>) and the foreground
+        color (<span class="codefrag">-3tab-selected</span>) are set to red (remember: we
+        defined <span class="codefrag">#FF0000</span> as the "color" value of
+        <span class="codefrag">tab-selected</span>).
       </p>
 <a name="N1017A"></a><a name="css_modify"></a>
 <h3 class="underlined_5">Modifying .css files</h3>
 <p>
-        In addition to the modification of <span class="codefrag ">skinconf.xml</span>
+        In addition to the modification of <span class="codefrag">skinconf.xml</span>
         you can also modify the respective .css file of your skin.
       </p>
 <p>
@@ -653,7 +653,7 @@
       </pre>
 <p>
         Here we have created our own color tags (in the .css file) and
-        defined the respective values for them (in <span class="codefrag ">skinconf.xml</span>). 
+        defined the respective values for them (in <span class="codefrag">skinconf.xml</span>). 
         Now you have color images with a red background and a green
         foreground. Horrible, isn't it?
       </p>

Modified: forrest/site/docs_0_70/howto/howto-custom-html-source.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/howto-custom-html-source.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/howto/howto-custom-html-source.html (original)
+++ forrest/site/docs_0_70/howto/howto-custom-html-source.html Sun Dec 18 17:31:25 2005
@@ -635,8 +635,8 @@
         current context and then assemble the actual expression(s) from it.
       </p>
 <p>In our example the matcher pattern
-       <span class="codefrag ">**/*.html</span> is applied to the request-name
-       <span class="codefrag ">mytest/mybad.html</span>, so we have three variables
+       <span class="codefrag">**/*.html</span> is applied to the request-name
+       <span class="codefrag">mytest/mybad.html</span>, so we have three variables
        altogether:
       </p>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -735,8 +735,8 @@
       </p>
 <p>
         In our example the matcher pattern
-        <span class="codefrag ">**body-*.html</span> is applied to the request-name
-        <span class="codefrag ">mytest/body-mybad.html</span>.
+        <span class="codefrag">**body-*.html</span> is applied to the request-name
+        <span class="codefrag">mytest/body-mybad.html</span>.
         Which means that we have three variables altogether:
       </p>
 <table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -838,7 +838,7 @@
         
 <li>
           
-<span class="codefrag ">&lt;map:generate src="{project:content.xdocs}{uri}.html" type="html"/&gt;</span>
+<span class="codefrag">&lt;map:generate src="{project:content.xdocs}{uri}.html" type="html"/&gt;</span>
 <br>
             Using the html-generator, Forrest reads the html-document
             from file and uses JTidy to clean up and convert it to xml
@@ -851,7 +851,7 @@
         
 <li>
             
-<span class="codefrag ">&lt;map:transform src="{forrest:stylesheets}/html2document.xsl"/&gt;</span>
+<span class="codefrag">&lt;map:transform src="{forrest:stylesheets}/html2document.xsl"/&gt;</span>
 <br>
           Using the standard stylesheet 'html2document.xsl', this XHTML is 
           transformed into Forrest standard document format.
@@ -859,14 +859,14 @@
         
 <li>
           
-<span class="codefrag ">&lt;map:transform type="idgen"/&gt;</span>
+<span class="codefrag">&lt;map:transform type="idgen"/&gt;</span>
 <br>
           This step generates IDs required for navigation within the page.
         </li>
         
 <li>
           
-<span class="codefrag ">&lt;map:serialize type="xml-document"/&gt;</span>
+<span class="codefrag">&lt;map:serialize type="xml-document"/&gt;</span>
 <br>
           Finally the document is serialized as XML and returned to the
           calling pipeline.

Modified: forrest/site/docs_0_70/howto/howto-forrest-from-maven.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/howto-forrest-from-maven.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/howto/howto-forrest-from-maven.html (original)
+++ forrest/site/docs_0_70/howto/howto-forrest-from-maven.html Sun Dec 18 17:31:25 2005
@@ -372,13 +372,13 @@
 <h2 class="underlined_10">Steps</h2>
 <div class="section">
 <p>The procedure outlined below describes how to add a goal to your
-    project's maven.xml that will invoke Forrest's <span class="codefrag ">site</span>
+    project's maven.xml that will invoke Forrest's <span class="codefrag">site</span>
     target.</p>
 <a name="N1003A"></a><a name="set-maven-home"></a>
 <h3 class="underlined_5">Set the FORREST_HOME environment variable</h3>
 <p>Make sure the FORREST_HOME environment variable points to your
       Forrest home directory (i.e. the directory that contains
-      <span class="codefrag ">forrest.build.xml</span>) (e.g. C:\opt\apache-forrest-0.7)</p>
+      <span class="codefrag">forrest.build.xml</span>) (e.g. C:\opt\apache-forrest-0.7)</p>
 <a name="N10047"></a><a name="define-ant-environment-prop"></a>
 <h3 class="underlined_5">Initialize an Ant environment property at the top of
       maven.xml</h3>
@@ -414,7 +414,7 @@
       it's not even necessary to have Ant 1.6 installed separately.</p>
 <a name="N10066"></a><a name="Alternative+file"></a>
 <h3 class="underlined_5">Alternative file</h3>
-<p>Under <span class="codefrag ">$FORREST_HOME/tools/targets/maven.xml</span>
+<p>Under <span class="codefrag">$FORREST_HOME/tools/targets/maven.xml</span>
 </p>
 </div>
 <a name="N10072"></a><a name="Feedback"></a>

Modified: forrest/site/docs_0_70/howto/howto-howto.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/howto-howto.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/howto/howto-howto.html (original)
+++ forrest/site/docs_0_70/howto/howto-howto.html Sun Dec 18 17:31:25 2005
@@ -438,7 +438,7 @@
       
 <li>An understanding of the How-To document structure. Just use this
       template document and you will be safe.
-      Make sure you run '<span class="codefrag ">forrest validate-xdocs</span>' before
+      Make sure you run '<span class="codefrag">forrest validate-xdocs</span>' before
       contributing your document.</li>
     
 </ul>

Modified: forrest/site/docs_0_70/howto/howto-pdf-tab.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/howto-pdf-tab.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/howto/howto-pdf-tab.html (original)
+++ forrest/site/docs_0_70/howto/howto-pdf-tab.html Sun Dec 18 17:31:25 2005
@@ -387,14 +387,14 @@
 <h2 class="underlined_10">Steps</h2>
 <div class="section">
 <p>The procedure outlined below will define a project
-      <span class="codefrag ">sitemap.xmap</span> and create a new
-      <span class="codefrag ">pdf-tab.xmap</span>.
+      <span class="codefrag">sitemap.xmap</span> and create a new
+      <span class="codefrag">pdf-tab.xmap</span>.
     </p>
 <a name="N1003D"></a><a name="sitemap"></a>
 <h3 class="underlined_5">Create your project's main sitemap.xmap</h3>
 <p>
       If you do not have already a sitemap then create a new empty one in your
-      <span class="codefrag ">src/documentation</span> directory (or wherever
+      <span class="codefrag">src/documentation</span> directory (or wherever
       ${project.sitemap-dir} points to).
     </p>
 <a name="N1004A"></a><a name="aggregator"></a>
@@ -426,7 +426,7 @@
 <a name="N10062"></a><a name="edit-aggregator"></a>
 <h3 class="underlined_5">Edit the file pdf-tab.xmap</h3>
 <p>
-      The <span class="codefrag ">&lt;map:match pattern="*.xml"&gt;</span> element
+      The <span class="codefrag">&lt;map:match pattern="*.xml"&gt;</span> element
       should look like the following:
     </p>
 <pre class="code">
@@ -464,7 +464,7 @@
 </div>
 <p>
       Add the following entry to your site.xml in the
-      <span class="codefrag ">&lt;about&gt;</span> element
+      <span class="codefrag">&lt;about&gt;</span> element
     </p>
 <pre class="code">... 
 &lt;whole_foosite href="pdf-tab.html" label="sub site" /&gt;
@@ -484,11 +484,11 @@
     </pre>
 <p>
       This allows you to link to it via a
-      <span class="codefrag ">&lt;link href="site:whole_foosite"&gt;</span>
+      <span class="codefrag">&lt;link href="site:whole_foosite"&gt;</span>
       reference. 
     </p>
 <p>Add to every element that should be included in the pdf-tab.pdf
-      the attribute <span class="codefrag ">wholesite="true"</span>
+      the attribute <span class="codefrag">wholesite="true"</span>
 </p>
 <pre class="code">
 &lt;sample-wiki label="Wiki page" href="wiki-sample.html"
@@ -498,8 +498,8 @@
 <div class="label">Note</div>
 <div class="content">This attribute will be inherited by all children of the element. 
 	 Do not use it in the parent element that contains the 
-	 <span class="codefrag ">&lt;whole_foosite href="pdf-tab.html" label="pdf-tab" /&gt;</span> 
-	 as the child (will cause a <span class="codefrag ">stack overflow</span> if you do)!!!
+	 <span class="codefrag">&lt;whole_foosite href="pdf-tab.html" label="pdf-tab" /&gt;</span> 
+	 as the child (will cause a <span class="codefrag">stack overflow</span> if you do)!!!
 	</div>
 </div>
 <a name="N100A8"></a><a name="explain"></a>
@@ -508,9 +508,9 @@
       Line 4 of our example
       <br>
       
-<span class="codefrag ">&lt;map:parameter name="include" value="//*[@wholesite='true']"/&gt;</span>
+<span class="codefrag">&lt;map:parameter name="include" value="//*[@wholesite='true']"/&gt;</span>
       looks at your site.xml and will match every element containing the
-      <span class="codefrag ">wholesite="true"</span> attribute. For example, to use the "samples"
+      <span class="codefrag">wholesite="true"</span> attribute. For example, to use the "samples"
       tab ...
     </p>
 <pre class="code">
@@ -522,8 +522,8 @@
     </pre>
 <p>
       It matches <strong>all</strong> of the elements that contain
-      <span class="codefrag ">wholesite="true"</span>
-      (in our example <span class="codefrag ">&lt;samples&gt;</span>
+      <span class="codefrag">wholesite="true"</span>
+      (in our example <span class="codefrag">&lt;samples&gt;</span>
       and its "children") for the content of the pdf file to be generated.
     </p>
 <pre class="code"> 
@@ -538,16 +538,16 @@
     </pre>
 <p>
       This example shows that you can as well exclude site(s) from the aggregation 
-      by using the <span class="codefrag ">wholesite="false"</span> attribute. This attribute will be as well inherited 
+      by using the <span class="codefrag">wholesite="false"</span> attribute. This attribute will be as well inherited 
       by all children of the element.
     </p>
 <p>
       Line 8 defines the title of the pdf file by taking the content
       of the project-name variable in
-      <span class="codefrag ">skinconf.xml</span> and adding some funny text:
+      <span class="codefrag">skinconf.xml</span> and adding some funny text:
       <br>
       
-<span class="codefrag ">&lt;map:parameter name="title" value="{conf:project-name}: Still My Foo Site"/&gt;</span>
+<span class="codefrag">&lt;map:parameter name="title" value="{conf:project-name}: Still My Foo Site"/&gt;</span>
     
 </p>
 </div>

Modified: forrest/site/docs_0_70/howto/howto-view-contracts.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/howto-view-contracts.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/howto/howto-view-contracts.html (original)
+++ forrest/site/docs_0_70/howto/howto-view-contracts.html Sun Dec 18 17:31:25 2005
@@ -407,7 +407,7 @@
 <p>
       By working on the i18n integration for "pelt" we crossed again the whys for using views. ;-)
       The maintainment problem was to change the captions of the skin features (contracts) to enable
-      support for i18n. The case is that the <span class="codefrag ">site2xhtml.xsl</span> has a lot of repeating code. 
+      support for i18n. The case is that the <span class="codefrag">site2xhtml.xsl</span> has a lot of repeating code. 
     </p>
 <p>
       For example the "last-publish"-contract could be found 2 times in the code.  
@@ -459,8 +459,8 @@
 <h3 class="underlined_5">Explaining the blank forrest:contract</h3>
 <p>
         To start a new forrest:contract you can copy the 'blank.ft' from
-        <span class="codefrag ">org.apache.forrest.plugin.output.viewHelper.xhtml/resources/templates</span>. 
-        The exact file system path can be looked up at <span class="codefrag ">http://localhost:8888/ls.contracts.html</span>.
+        <span class="codefrag">org.apache.forrest.plugin.output.viewHelper.xhtml/resources/templates</span>. 
+        The exact file system path can be looked up at <span class="codefrag">http://localhost:8888/ls.contracts.html</span>.
       </p>
 <p>
         The 'blank.ft' is a simple xml file with the following code which you can use to base new contracts 
@@ -489,8 +489,8 @@
 
       </pre>
 <p>
-        The most important is the name of the contract <span class="codefrag ">&lt;forrest:contract name="blank"/&gt;</span>. 
-        This name is the same as the file name of the contract (without file extension) <span class="codefrag ">blank.ft</span>. 
+        The most important is the name of the contract <span class="codefrag">&lt;forrest:contract name="blank"/&gt;</span>. 
+        This name is the same as the file name of the contract (without file extension) <span class="codefrag">blank.ft</span>. 
       </p>
 <div class="note">
 <div class="label">Note</div>
@@ -499,7 +499,7 @@
       </div>
 </div>
 <p>
-        The <span class="codefrag ">&lt;description/&gt;</span> tag needs to be filled in with some information
+        The <span class="codefrag">&lt;description/&gt;</span> tag needs to be filled in with some information
         that is explaining the contract to the webdesigner. The better explained the more efficient
         for the webdesigner to pick the right contract.
       </p>
@@ -508,19 +508,19 @@
 &lt;/description&gt;
       </pre>
 <p>
-        In the <span class="codefrag ">&lt;usage/&gt;</span> tag we have to explain how the designer can use 
+        In the <span class="codefrag">&lt;usage/&gt;</span> tag we have to explain how the designer can use 
         the contract in his view.
       </p>
 <pre class="code">&lt;usage&gt;&lt;![CDATA[&lt;forrest:contract name="siteinfo-last-published-howto"/&gt;]]&gt;&lt;/usage&gt;
       </pre>
 <p>
         
-<span class="codefrag ">&lt;forrest:template name="blank" body="false" head="false"&gt; </span> 
+<span class="codefrag">&lt;forrest:template name="blank" body="false" head="false"&gt; </span> 
         That leads to the template attribute @body="true" and
 				@head="false". In xhtml a contract can add content to the &lt;body/&gt; or/and
 				&lt;head/&gt; part of &lt;html/&gt;. This values have to be change when adding an actual template.
         Besides this a xsl-template has to indicate this in the naming. A template that add content to the 
-        html body has to end with "<span class="codefrag ">-body</span>"!!!
+        html body has to end with "<span class="codefrag">-body</span>"!!!
       </p>
 <div class="note">
 <div class="label">Note</div>
@@ -552,7 +552,7 @@
 </div>
 <p> 
 				Now lets pick up the example we started with and create a "siteinfo-last-published-howto" contract.
-        Save the blank.ft to <span class="codefrag ">{project.home}/src/documentation/resources/templates/siteinfo-last-published-howto.ft</span>.
+        Save the blank.ft to <span class="codefrag">{project.home}/src/documentation/resources/templates/siteinfo-last-published-howto.ft</span>.
       </p>
 <p>
         Now the maintainment optimized code (xpath="/html/body/*") was:
@@ -623,7 +623,7 @@
 <h3 class="underlined_5">Activating the contract</h3>
 <p>
         To see whether the new contract works we need to add it to our view.
-        The contract usage contains the contract-tag <span class="codefrag ">&lt;forrest:contract name="siteinfo-last-published-howto"/&gt;</span>
+        The contract usage contains the contract-tag <span class="codefrag">&lt;forrest:contract name="siteinfo-last-published-howto"/&gt;</span>
         Please see <a href="../../docs_0_80/howto/howto-view-dsl.html">Getting started with forrest:view DSL</a> for more details.
       </p>
 <div class="fixme">

Modified: forrest/site/docs_0_70/howto/howto-view-dsl.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/howto-view-dsl.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/howto/howto-view-dsl.html (original)
+++ forrest/site/docs_0_70/howto/howto-view-dsl.html Sun Dec 18 17:31:25 2005
@@ -406,13 +406,13 @@
 </div>
 <p>
       We developed<strong> forrest:view</strong>  to let the user decide where to place elements in e.g. html-pages.
-      We started this work with the <span class="codefrag ">skinconf.xml</span> where you could configure certain elements and
+      We started this work with the <span class="codefrag">skinconf.xml</span> where you could configure certain elements and
       their positions. This elements was known under certain names. It was up to the skin-designer to support 
       this configuration and the elements.
     </p>
 <p>
      The work started with grouping elements (the ones from skinconf). We used css-contracts that 
-     we added as @attributes e.g. <span class="codefrag ">&lt;div id="content-main"/&gt; </span>. That made it 
+     we added as @attributes e.g. <span class="codefrag">&lt;div id="content-main"/&gt; </span>. That made it 
      possible to use the same elements in different skins. For the full list refer to the
       <a href="http://svn.apache.org/repos/asf/forrest/trunk/main/webapp/skins/leather-dev/contracts.initial.txt">
         inicial contract list
@@ -428,8 +428,8 @@
      
 <strong>forrest:hook</strong>'s are container that are only used for layout reasons. They <strong>do not</strong> add 
      any content nor functionality to the output. They add <strong>only</strong> layout information to 
-     the output. Actually a <span class="codefrag ">&lt;forrest:hook name="layoutId"/&gt;</span> will be transformed
-     to <span class="codefrag ">&lt;div id="layoutId"/&gt; </span>
+     the output. Actually a <span class="codefrag">&lt;forrest:hook name="layoutId"/&gt;</span> will be transformed
+     to <span class="codefrag">&lt;div id="layoutId"/&gt; </span>
     
 </p>
 <p>
@@ -458,17 +458,17 @@
 <p>
 				In this section we will create a new view. We will override the default view of the view-plugin
         for the index page of the <a href="../../docs_0_80/howto/howto-view-install.html">newSeed</a>.
-        For that we will create a file called <span class="codefrag ">index.fv</span> and save it in our xdocs directory. 
+        For that we will create a file called <span class="codefrag">index.fv</span> and save it in our xdocs directory. 
         This will make <strong>only</strong> the index.html page look different from the rest of the project.
 			</p>
 <p>
-        Remember: pointing your browser to <span class="codefrag ">http://localhost:8888/ls.contracts.html</span> will
+        Remember: pointing your browser to <span class="codefrag">http://localhost:8888/ls.contracts.html</span> will
         show a page with all contracts that you can use in your project.
       </p>
 <p>
         Let use the blank view from the earlier step and add the content-main contract. In 
         ls.contracts.html we find the information how to use the contract in our view. Our 
-        <span class="codefrag ">index.fv</span> should look like:
+        <span class="codefrag">index.fv</span> should look like:
       </p>
 <pre class="code">&lt;forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" &gt;
   &lt;forrest:view type="xhtml"&gt;    
@@ -477,7 +477,7 @@
 &lt;/forrest:views&gt;
       </pre>
 <p>
-        Let's try our new view by pointing to <span class="codefrag ">http://localhost:8888/index.html</span>. 
+        Let's try our new view by pointing to <span class="codefrag">http://localhost:8888/index.html</span>. 
         We will see only the main content. :) Now let's add the section navigation to our view.
         The contract usage in the view can be looked up in ls.contracts.html. Our view now looks like:
       </p>
@@ -496,7 +496,7 @@
 <a name="N100D1"></a><a name="hookView"></a>
 <h3 class="underlined_5">Hooks in views</h3>
 <p>
-        We will use now the first time a <span class="codefrag ">&lt;forrest:hook name="layoutId"/&gt;</span>.
+        We will use now the first time a <span class="codefrag">&lt;forrest:hook name="layoutId"/&gt;</span>.
         Hooks are the styling side of views. We can imitate arbitrary html skeleton 
         with their help. Before we explain how to use your own css in views we will use the default css.
         In the default.css we can find 
@@ -510,7 +510,7 @@
 }
       </pre>
 <p>
-        With this information we know to use <span class="codefrag ">&lt;forrest:hook name="leftbar"/&gt;</span> 
+        With this information we know to use <span class="codefrag">&lt;forrest:hook name="leftbar"/&gt;</span> 
         and add contracts into that container. 
       </p>
 <p>
@@ -538,10 +538,10 @@
 <p>
         We know now how to place contracts and hooks in our view, till this stage we only used the default.css. 
         CSS-support of views is as easy as placing contracts/hooks. To override the default.css
-        stylesheet we use another tag within our view <span class="codefrag ">&lt;forrest:css url="default.css"/&gt;</span>.
+        stylesheet we use another tag within our view <span class="codefrag">&lt;forrest:css url="default.css"/&gt;</span>.
       </p>
 <p>
-        We will now create a file in <span class="codefrag ">{project:skins-dir}{path}/{name}.css</span>. In our case
+        We will now create a file in <span class="codefrag">{project:skins-dir}{path}/{name}.css</span>. In our case
         we will save a file called howTo.css in newSeed/src/documentation/skins/css/howTo.css containing only 
         the following css:
       </p>
@@ -556,14 +556,14 @@
 <p>
         We just changed the border-style to 'solid', the background to '#CCCCFF' and the color to '#000000'. 
         Now we have to add a new tag to tell that we want to override the default.css. We are doing this 
-        by adding the tag <span class="codefrag ">&lt;forrest:css url="howTo.css"/&gt;</span> to our view.
+        by adding the tag <span class="codefrag">&lt;forrest:css url="howTo.css"/&gt;</span> to our view.
       </p>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
         
-<span class="codefrag ">&lt;forrest:css url="howTo.css"/&gt;</span> has to be direct son of 
-        <span class="codefrag ">&lt;forrest:view type="xhtml"&gt;</span>!!!
+<span class="codefrag">&lt;forrest:css url="howTo.css"/&gt;</span> has to be direct son of 
+        <span class="codefrag">&lt;forrest:view type="xhtml"&gt;</span>!!!
       </div>
 </div>
 <pre class="code">&lt;forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" &gt;
@@ -579,7 +579,7 @@
 <p>
         Now you see a white page where the menu is sourrounded by a solid border with the defined background.
          As second example let us change as well the content-main by adding another hook 
-         <span class="codefrag ">&lt;forrest:hook name="content"/&gt;</span> We need to add the new layout container
+         <span class="codefrag">&lt;forrest:hook name="content"/&gt;</span> We need to add the new layout container
          to our howTo.css:
       </p>
 <pre class="code">

Modified: forrest/site/docs_0_70/howto/howto-view-install.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/howto-view-install.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/howto/howto-view-install.html (original)
+++ forrest/site/docs_0_70/howto/howto-view-install.html Sun Dec 18 17:31:25 2005
@@ -464,7 +464,7 @@
 <h3 class="underlined_5">Available contracts</h3>
 <p> 
 	     To start working with views you need to know which contracts you can use. 
-	     For this we will install another plugin <span class="codefrag ">org.apache.forrest.plugin.input.viewHelper.xhtml.ls</span>.
+	     For this we will install another plugin <span class="codefrag">org.apache.forrest.plugin.input.viewHelper.xhtml.ls</span>.
 	     The setup is:
 	    </p>
 <pre class="code">
@@ -483,7 +483,7 @@
 project.required.plugins=org.apache.forrest.plugin.input.viewHelper.xhtml.ls
       </pre>
 <p>
-        Now point your browser to <span class="codefrag ">http://localhost:8888/ls.contracts.html</span>. 
+        Now point your browser to <span class="codefrag">http://localhost:8888/ls.contracts.html</span>. 
         On this page you will find all contracts that you can use in your project.
       </p>
 </div>

Modified: forrest/site/docs_0_70/libre-intro.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/libre-intro.html?rev=357603&r1=357602&r2=357603&view=diff
==============================================================================
--- forrest/site/docs_0_70/libre-intro.html (original)
+++ forrest/site/docs_0_70/libre-intro.html Sun Dec 18 17:31:25 2005
@@ -481,7 +481,7 @@
   &lt;/collection&gt;
 &lt;/collection&gt;</pre>
 <p>And it's not getting any harder in fact: only 2 elements,
-          <span class="codefrag ">&lt;collection&gt;</span> and <span class="codefrag ">&lt;item&gt;</span> and that should
+          <span class="codefrag">&lt;collection&gt;</span> and <span class="codefrag">&lt;item&gt;</span> and that should
           do. The first maps to a menu-group in the navigation, guess what the second
           maps to?</p>
 <p>The number and value (and its meaning) of the attributes on these
@@ -551,15 +551,15 @@
 <li>libre doesn't yet support external hrefs (should be easy
               though)</li> 
             
-<li>there is no difference between <span class="codefrag ">&lt;menu&gt;</span> and
-              <span class="codefrag ">&lt;menu-item&gt;</span>, there just is <span class="codefrag ">&lt;entry&gt;</span>. It
-              will become a <span class="codefrag ">&lt;collection&gt;</span> or <span class="codefrag ">&lt;item&gt;</span> in
+<li>there is no difference between <span class="codefrag">&lt;menu&gt;</span> and
+              <span class="codefrag">&lt;menu-item&gt;</span>, there just is <span class="codefrag">&lt;entry&gt;</span>. It
+              will become a <span class="codefrag">&lt;collection&gt;</span> or <span class="codefrag">&lt;item&gt;</span> in
               the output based on the fact if the location points to a directory resp. a
               file.</li> 
             
 <li>For locations that point to a filter it doesn't make sense, but
-              when it points to a directory it is nested <span class="codefrag ">&lt;filter&gt;</span> and
-              <span class="codefrag ">&lt;sort&gt;</span> elements get inherited down to the next level. </li> 
+              when it points to a directory it is nested <span class="codefrag">&lt;filter&gt;</span> and
+              <span class="codefrag">&lt;sort&gt;</span> elements get inherited down to the next level. </li> 
           
 </ul> 
           
@@ -573,18 +573,18 @@
 <pre class="code">&lt;auto&gt;</pre>
 <ul> 
             
-<li>Automatically generates more <span class="codefrag ">&lt;collection&gt;</span>
-              and <span class="codefrag ">&lt;item&gt;</span> elements in the output, based on the
-              specifications of the nested elements: <span class="codefrag ">&lt;filter&gt;</span> (which
-              resources?) and <span class="codefrag ">&lt;sort&gt;</span> (in which order?).</li> 
+<li>Automatically generates more <span class="codefrag">&lt;collection&gt;</span>
+              and <span class="codefrag">&lt;item&gt;</span> elements in the output, based on the
+              specifications of the nested elements: <span class="codefrag">&lt;filter&gt;</span> (which
+              resources?) and <span class="codefrag">&lt;sort&gt;</span> (in which order?).</li> 
           
 </ul>
 <pre class="code">&lt;filter logic="inverse" clear="no"&gt;</pre>
 <ul> 
             
 <li>This element wraps a so-called AttributeReader (there are
-              currently two of them: <span class="codefrag ">&lt;xpath&gt;</span> and
-              <span class="codefrag ">&lt;property&gt;</span>)</li> 
+              currently two of them: <span class="codefrag">&lt;xpath&gt;</span> and
+              <span class="codefrag">&lt;property&gt;</span>)</li> 
             
 <li>The AttributeReader is going to specify which
               information-element is going to be retrieved from the file or directory it is
@@ -597,7 +597,7 @@
               acceptance-logic (accept what normally should be rejected and vice versa).</li>
             
             
-<li>Using the <span class="codefrag ">clear="yes"</span> attribute stops the
+<li>Using the <span class="codefrag">clear="yes"</span> attribute stops the
               inheritance of the used filter strategy from the parent directory. Instead the
               default filter strategy (which is to accept all files) is slided in at this
               level.</li> 
@@ -607,20 +607,20 @@
 <ul> 
             
 <li>This element wraps a so called AttributeReader (there are
-              currently two of them: <span class="codefrag ">&lt;xpath&gt;</span> and
-              <span class="codefrag ">&lt;property&gt;</span>).</li> 
+              currently two of them: <span class="codefrag">&lt;xpath&gt;</span> and
+              <span class="codefrag">&lt;property&gt;</span>).</li> 
             
 <li>The AttributeReader is going to specify which
               information-element is going to be retrieved from the file or directory it is
               pointing at. This information element will be considered to be a simple
-              Key-String and <span class="codefrag ">&lt;collection&gt;</span> and <span class="codefrag ">&lt;item&gt;</span>
+              Key-String and <span class="codefrag">&lt;collection&gt;</span> and <span class="codefrag">&lt;item&gt;</span>
               elements in the output will appear in the order defined by the alphabetic
               sorting of these keys.</li> 
             
 <li>This wrapping sort element allows to reverse the order.
               (z-&gt;a instead of a-&gt;z)</li> 
             
-<li>Using the <span class="codefrag ">clear="yes"</span> attribute stops the
+<li>Using the <span class="codefrag">clear="yes"</span> attribute stops the
               inheritance of the used sort strategy from the parent directory. Instead the
               default sort strategy (which is to use default filesystem sorting, alphabetic
               on filename) is slided in at this level.</li> 
@@ -630,9 +630,9 @@
 <ul> 
             
 <li>The remainder of the elements inside the
-              <span class="codefrag ">&lt;auto&gt;</span> tag specify the attributes that need to be applied to
-              the generated <span class="codefrag ">&lt;collection&gt;</span> and <span class="codefrag ">&lt;item&gt;</span>
-              elements in the output: <span class="codefrag ">&lt;item label=".." href=".." YOURTAG=".."
+              <span class="codefrag">&lt;auto&gt;</span> tag specify the attributes that need to be applied to
+              the generated <span class="codefrag">&lt;collection&gt;</span> and <span class="codefrag">&lt;item&gt;</span>
+              elements in the output: <span class="codefrag">&lt;item label=".." href=".." YOURTAG=".."
               /&gt;</span>
 </li> 
             
@@ -653,39 +653,39 @@
 <ul> 
             
 <li>This element specifies an xpath AttributeReader to use inside
-              <span class="codefrag ">&lt;filter&gt;</span>, <span class="codefrag ">&lt;sort&gt;</span> or
+              <span class="codefrag">&lt;filter&gt;</span>, <span class="codefrag">&lt;sort&gt;</span> or
               {AttributeDefinitions}.</li> 
             
 <li>It allows to specify an xpath expression that should result in
               one single text node to be returned when applied to the root node of the xml
               file at the location of any given entry. The contents of this text-node is the
-              string value to sort (<span class="codefrag ">&lt;sort&gt;</span> usage) or to fill in the
-              specified attribute (<span class="codefrag ">&lt;label&gt;</span>, <span class="codefrag ">&lt;href&gt;</span>...
-              use). When inside a <span class="codefrag ">&lt;filter&gt;</span>: the presence of the node
+              string value to sort (<span class="codefrag">&lt;sort&gt;</span> usage) or to fill in the
+              specified attribute (<span class="codefrag">&lt;label&gt;</span>, <span class="codefrag">&lt;href&gt;</span>...
+              use). When inside a <span class="codefrag">&lt;filter&gt;</span>: the presence of the node
               results in passing the test.</li> 
           
 </ul>
 <div class="warning">
 <div class="label">Warning</div>
-<div class="content">This currently breaks for non xml (<span class="codefrag ">*.gif</span>)
+<div class="content">This currently breaks for non xml (<span class="codefrag">*.gif</span>)
             files, so get your filter right please, and in the mean time: sorry for not
-            being able to use it in the filter yet <span class="codefrag ">:-(</span>.</div>
+            being able to use it in the filter yet <span class="codefrag">:-(</span>.</div>
 </div>
 <pre class="code">&lt;property name="path" regex="(\.[\\/])*(.*)" substitute="$2"/&gt;
 &lt;property name="name"  mask="CVS"/&gt;</pre>
 <ul> 
             
 <li>This element specifies an xpath AttributeReader to use inside
-              <span class="codefrag ">&lt;filter&gt;</span>, <span class="codefrag ">&lt;sort&gt;</span> or
+              <span class="codefrag">&lt;filter&gt;</span>, <span class="codefrag">&lt;sort&gt;</span> or
               {AttributeDefinitions}.</li> 
             
 <li>It allows to specify a JavaBean-like property to read (this
               introspection behavior will probably not survive the future release) on the
               file at the 'location' of any given entry. The (object-)value of this property
               is automatically converted to a String (toString()) that becomes the value to
-              sort (<span class="codefrag ">&lt;sort&gt;</span> usage) or to fill in the specified attribute
-              (<span class="codefrag ">&lt;label&gt;</span>, <span class="codefrag ">&lt;href&gt;</span>... use). When inside a
-              <span class="codefrag ">&lt;filter&gt;</span>, the test passes if the read property is not null
+              sort (<span class="codefrag">&lt;sort&gt;</span> usage) or to fill in the specified attribute
+              (<span class="codefrag">&lt;label&gt;</span>, <span class="codefrag">&lt;href&gt;</span>... use). When inside a
+              <span class="codefrag">&lt;filter&gt;</span>, the test passes if the read property is not null
               or "".</li> 
             
 <li>Furthermore this element allows to express more elaborate
@@ -708,28 +708,28 @@
 <p>There are some things that libre is doing that you should be aware of.</p>
 <a name="N10175"></a><a name="No+libre.xml"></a>
 <h4>No libre.xml</h4>
-<p>When using an <span class="codefrag ">&lt;auto&gt; </span>section, the filter will
-            NEVER accept the <span class="codefrag ">libre.xml</span> file to be in the generated output. You
-            can however include a manual <span class="codefrag ">&lt;entry&gt;</span> to point to the
-            <span class="codefrag ">libre.xml</span> file if needed.</p>
+<p>When using an <span class="codefrag">&lt;auto&gt; </span>section, the filter will
+            NEVER accept the <span class="codefrag">libre.xml</span> file to be in the generated output. You
+            can however include a manual <span class="codefrag">&lt;entry&gt;</span> to point to the
+            <span class="codefrag">libre.xml</span> file if needed.</p>
 <a name="N1018B"></a><a name="No+Duplicates"></a>
 <h4>No Duplicates</h4>
-<p>You can combine multiple <span class="codefrag ">&lt;entry&gt;</span> and
-            <span class="codefrag ">&lt;auto&gt;</span> elements after each other. The system will make sure
-            that the resulting list of <span class="codefrag ">&lt;collection&gt;</span> and
-            <span class="codefrag ">&lt;item&gt;</span> will not contain duplicates. So the filters in
-            <span class="codefrag ">&lt;auto&gt;</span> sections lower down the <span class="codefrag ">libre.xml</span> file
+<p>You can combine multiple <span class="codefrag">&lt;entry&gt;</span> and
+            <span class="codefrag">&lt;auto&gt;</span> elements after each other. The system will make sure
+            that the resulting list of <span class="codefrag">&lt;collection&gt;</span> and
+            <span class="codefrag">&lt;item&gt;</span> will not contain duplicates. So the filters in
+            <span class="codefrag">&lt;auto&gt;</span> sections lower down the <span class="codefrag">libre.xml</span> file
             can include already accepted files or directories, they will only show up once
             in the output.</p>
 <a name="N101A8"></a><a name="Example+Constructs"></a>
 <h3 class="underlined_5">Example Constructs</h3>
 <p>Adding sorting and filtering to the filesystem with libre becomes a
           subtle play with editable filesystem properties, smart XML content and
-          <span class="codefrag ">libre.xml</span> configs. This should be considered as the 'extended'
+          <span class="codefrag">libre.xml</span> configs. This should be considered as the 'extended'
           contract between the following roles in the documentation system: the one
           choosing (or creating) the DTDs, the one applying those to create content and
           give the resulting files a name, the one that sets up the directories to store
-          those files and writes the <span class="codefrag ">libre.xml</span> files.</p>
+          those files and writes the <span class="codefrag">libre.xml</span> files.</p>
 <a name="N101B7"></a><a name="Sorting+your+files+or+your+menu+entries%3F"></a>
 <h4>Sorting your files or your menu entries?</h4>
 <p>In every case the very pragmatic approach can become something
@@ -760,14 +760,14 @@
 <ul> 
             
 <li>
-<span class="codefrag ">&lt;filter&gt;</span>: only resources which name starts
+<span class="codefrag">&lt;filter&gt;</span>: only resources which name starts
               with a 3-digit pattern</li> 
             
-<li>No <span class="codefrag ">&lt;sort&gt;</span>: in their natural filesystem order
+<li>No <span class="codefrag">&lt;sort&gt;</span>: in their natural filesystem order
               assured by the digit-prefix</li> 
             
 <li>
-<span class="codefrag ">&lt;label&gt;</span>: hold a label attribute that strips
+<span class="codefrag">&lt;label&gt;</span>: hold a label attribute that strips
               of the ugly number prefix</li> 
           
 </ul>
@@ -889,7 +889,7 @@
 <h4>Separating property-retrieval from formatting and
             testing</h4>
 <p>Playing around with the attributes in
-            <span class="codefrag ">&lt;property&gt;</span>:</p>
+            <span class="codefrag">&lt;property&gt;</span>:</p>
 <ul> 
             
 <li>poses hard to explain combinatory effects (@regex with
@@ -912,23 +912,23 @@
 &lt;/label&gt;</pre>
 <p>Allowing the formatter to be used around the xpath reader as well.
             And opening up the possibility to maybe format other stuff than Strings:
-            <span class="codefrag ">&lt;dateformat format="dd/mmm/yy"&gt; </span>
+            <span class="codefrag">&lt;dateformat format="dd/mmm/yy"&gt; </span>
 </p>
 <p>It would also clearly distinguish the semantical difference of
-            applying a test in the <span class="codefrag ">&lt;filter&gt;</span> context:</p>
+            applying a test in the <span class="codefrag">&lt;filter&gt;</span> context:</p>
 <pre class="code">&lt;filter&gt;
   &lt;regextest match="..."&gt;
     &lt;property ... /&gt;
   &lt;/regextest&gt;
 &lt;/filter&gt;</pre>
-<p>And more logically introduce other tests like <span class="codefrag ">&lt;globtest
-            match="..."&gt;</span> or <span class="codefrag ">&lt;availabletest&gt;</span> or...</p>
+<p>And more logically introduce other tests like <span class="codefrag">&lt;globtest
+            match="..."&gt;</span> or <span class="codefrag">&lt;availabletest&gt;</span> or...</p>
 <a name="N1028B"></a><a name="Replace+the+introspection+with+semantically+richer+named%0A++++++++++++properties+to+read."></a>
 <h4>Replace the introspection with semantically richer named
             properties to read.</h4>
-<p>Currently the <span class="codefrag ">&lt;property
+<p>Currently the <span class="codefrag">&lt;property
             name="someJavaBeanProp"&gt;</span> is applied in a java introspection for the
-            <span class="codefrag ">getSomeJavaBeanProp()</span> on the <span class="codefrag ">java.io.File</span> object that
+            <span class="codefrag">getSomeJavaBeanProp()</span> on the <span class="codefrag">java.io.File</span> object that
             is actually representing the node in the hierarchy at any given time. The DTD
             declares the attribute as of type CDATA. These decisions however:</p>
 <ul> 
@@ -936,7 +936,7 @@
 <li>lead to a lesser user guidance for the libre.xml writer using
               an XML (and DTD) savvy editor </li> 
             
-<li>leads to assuming the <span class="codefrag ">libre.xml</span> editor has access
+<li>leads to assuming the <span class="codefrag">libre.xml</span> editor has access
               to and knows how to interpret jdk javadoc</li> 
             
 <li>leads to poor semantical support and thus more possible RUNTIME
@@ -995,9 +995,9 @@
 <ul> 
           
 <li>do we need support for nested elements inside
-            <span class="codefrag ">&lt;item&gt;</span> output (retrieved by e.g. xpath expressions)?</li> 
+            <span class="codefrag">&lt;item&gt;</span> output (retrieved by e.g. xpath expressions)?</li> 
           
-<li>do we need an extra <span class="codefrag ">&lt;constant&gt;</span> like
+<li>do we need an extra <span class="codefrag">&lt;constant&gt;</span> like
             attributereader that would allow like book.xml to add fixed values for
             expressed attributes</li> 
           



Mime
View raw message