forrest-site-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From thors...@apache.org
Subject svn commit: r527684 [2/2] - in /forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher: ./ how/ images/ int/ skin/
Date Wed, 11 Apr 2007 21:33:37 GMT
Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-structurer.html
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-structurer.html?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-structurer.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-structurer.html Wed Apr 11 14:33:35 2007
@@ -4,7 +4,7 @@
         <link href="../themes/common.css" media="screen" rel="alternate stylesheet" title="common" type="text/css" />
         <link href="../themes/leather-dev.css" media="screen" rel="alternate stylesheet" title="common" type="text/css" />
         <link href="../themes/pelt.screen.css" media="screen" rel="stylesheet" title="Pelt" type="text/css" />
-        
+
         <link href="../how/howto-dispatcher-structurer.dispatcher.css" media="screen" rel="stylesheet" title="Pelt" type="text/css" />
         <link href="../themes/pelt.print.css" media="print" rel="stylesheet" title="Pelt" type="text/css" />
         <style type="text/css">/* Extra css */ 
@@ -157,8 +157,10 @@
 <!--+ |start content-title +-->
 <h1 class="content-title">How to use the structurer</h1>
 <!--+ |end content-title +-->
-<!--+ |start content-abstract +--> This How-To describes the usage of the structurer config domain 
-    specific language to create beautiful websites in no time. <!--+ |end content-abstract +--><!--+ |start content-minitoc +--><div id="content-minitoc-area">
+<!--+ |start content-abstract +-->
+      This How-To describes the usage of the structurer config domain specific
+      language to create beautiful websites in no time.
+    <!--+ |end content-abstract +--><!--+ |start content-minitoc +--><div id="content-minitoc-area">
 <ul class="minitoc">
 <li>
 <a href="#Intended Audience">Intended Audience</a>
@@ -204,23 +206,27 @@
 <div class="section">
 <div class="warning">
 <div class="label">Warning</div>
-<div class="content"> The "Dispatcher" (aka "Views") is new functionality which is 
-      still in development phase. That is why it is in the "whiteboard" section 
-      of the Forrest distribution. This HowTo is a good start but still needs 
-      more work.
-      See <a href="http://forrest.apache.org/docs_0_80/status-themes.html">Status of Themes: Skins and Dispatcher</a>.
+<div class="content">
+      The "Dispatcher" (aka "Views") is new functionality which is still in
+      development phase. That is why it is in the "whiteboard" section of the
+      Forrest distribution. This HowTo is a good start but still needs more
+      work. See <a href="http://forrest.apache.org/docs_0_80/status-themes.html">Status of Themes: Skins and
+      Dispatcher</a>.
     </div>
 </div>
-<p> This part of the the dispatcher is called the structurer and is 
-      dedicated to webdesigner and user with some knowledge of css. </p>
+<p>
+      This part of the the dispatcher is called the structurer and is dedicated
+      to webdesigner and user with some knowledge of css.
+    </p>
 </div>
 <a name="Purpose" title="Purpose"> </a>
 <h2 class="underlined_10">Purpose</h2>
 <div class="section">
-<p> This how-to will show you how to write a <strong>structurer</strong> 
-      from the ground up. We will focus on html as the output format. As well 
-      it will show how to add your own css implementation to the structurer. 
-      </p>
+<p>
+      This how-to will show you how to write a <strong>structurer</strong> from
+      the ground up. We will focus on html as the output format. As well it will
+      show how to add your own css implementation to the structurer.
+    </p>
 </div>
 <a name="Prerequisites" title="Prerequisites"> </a>
 <h2 class="underlined_10">Prerequisites</h2>
@@ -235,57 +241,78 @@
 <div class="section">
 <div class="note">
 <div class="label">Note</div>
-<div class="content"> When developing with the dispatcher we assume you are using 'forrest 
-      run' and the following workflow "change files -&gt; refresh browser"<br /> 
-      Installing a mozilla browser and the forrestbar helps a lot in 
-      developing. Many instructions assumes that you have the forrestbar 
-      installed. </div>
+<div class="content">
+      When developing with the dispatcher we assume you are using 'forrest run'
+      and the following workflow "change files -&gt; refresh browser"
+      <br />
+      Installing a mozilla browser and the forrestbar helps a lot in developing.
+      Many instructions assumes that you have the forrestbar installed.
+    </div>
 </div>
 <a name="emptystructurer" title="Empty structurer file"> </a>
 <h3 class="underlined_5">Empty structurer file</h3>
 <div class="section">
-<pre class="code">&lt;forrest:views 
+<pre class="code">
+&lt;forrest:views 
   xmlns:forrest="http://apache.org/forrest/templates/1.0"
   xmlns:jx="http://apache.org/cocoon/templates/jx/1.0"&gt;
   &lt;forrest:view type="html"&gt;
   &lt;/forrest:view&gt;
 &lt;/forrest:views&gt;
       </pre>
-<p> <strong> The structurer</strong> is designed to be open for any 
-        format that can use<strong> forrest:view</strong> as configuration 
-        file. The only format we implemented is html for now. This is as well 
-        true for the delivered contracts. </p>
+<p>
+        <strong> The structurer</strong> is designed to be open for any format
+        that can use<strong> forrest:view</strong> as configuration file. The
+        only format we implemented is html for now. This is as well true for the
+        delivered contracts.
+      </p>
 </div>
 <a name="firststructurer" title="Creating your first structurer"> </a>
 <h3 class="underlined_5">Creating your first structurer</h3>
 <div class="section">
 <div class="warning">
 <div class="label">Warning</div>
-<div class="content"> The structurer is based on jx templates to allow simple 
-        presentation logic (all code starting with "jx:"). Please refer to the 
-        cocoon documentation about jx. </div>
-</div>
-<p> In this section we will create a new structurer. We will override the 
-        default structurer of the core themes for the index page of a new seed. 
-        For that we will create a file called <span class="codefrag">index.fv</span> and save it 
-        in the directory <span class="codefrag">{properties:resources}/structurer/url</span> 
-        (create it if needed). This will make <strong>only</strong> the 
-        index.html page look different from the rest of the project. </p>
+<div class="content">
+        The structurer is based on jx templates to allow simple presentation
+        logic (all code starting with "jx:"). Please refer to the cocoon
+        documentation about jx.
+      </div>
+</div>
+<p>
+        In this section we will create a new structurer. We will override the
+        default structurer of the core themes for the index page of a new seed.
+        For that we will create a file called <span class="codefrag">index.fv</span> and save it
+        in the directory <span class="codefrag">{properties:resources}/structurer/url</span>
+        (create it if needed). This will make <strong>only</strong> the
+        index.html page look different from the rest of the project.
+      </p>
 <div class="note">
 <div class="label">RecursiveDirectoryTraversalAction</div>
-<div class="content"> You can set a view for an individual file, a directory, or the whole site. To address multiple files in a directory call your  <span class="codefrag">.fv</span> file <span class="codefrag">common.fv</span>. If Forrest doesn't find a <span class="codefrag">.fv</span> file with the same name as the current file it will use the common.fv file in that directory, or the first one it finds going upwards through the directory structure. 
-	<span class="codefrag">common.fv</span> files affect all subdirectories unless they are overidden by another <span class="codefrag">common.fv</span> or a file-specific <span class="codefrag">foo.fv</span> file. 
-	</div>
-</div>
-<p> Remember: pointing your browser to 
-        <span class="codefrag">http://localhost:8888/ls.contracts.html</span> will show a page 
-        with all contracts and themes that you can use in your project provided 
-        by forrest. </p>
-<p> Let us use the blank structurer from the earlier step and add the 
-        content-main contract. In ls.contracts.html we find the information for 
-        how to use the contract in our structurer. Our <span class="codefrag">index.fv</span> 
-        should look like: </p>
-<pre class="code">&lt;forrest:views 
+<div class="content">
+        You can set a view for an individual file, a directory, or the whole
+        site. To address multiple files in a directory call your
+        <span class="codefrag">.fv</span> file <span class="codefrag">common.fv</span>. If Forrest doesn't find a
+        <span class="codefrag">.fv</span> file with the same name as the current file it will use
+        the common.fv file in that directory, or the first one it finds going
+        upwards through the directory structure. <span class="codefrag">common.fv</span> files
+        affect all subdirectories unless they are overidden by another
+        <span class="codefrag">common.fv</span> or a file-specific <span class="codefrag">foo.fv</span> file.
+      </div>
+</div>
+<p>
+        Remember: pointing your browser to
+        <span class="codefrag">http://localhost:8888/ls.contracts.html</span> will show a page
+        with all contracts and themes that you can use in your project provided
+        by forrest.
+      </p>
+<p>
+        Let us use the blank structurer from the earlier step and add the
+        content-main contract. In ls.contracts.html we find the information for
+        how to use the contract in our structurer. Our <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"
   xmlns:jx="http://apache.org/cocoon/templates/jx/1.0"&gt;
   &lt;forrest:view type="html"&gt;
@@ -303,23 +330,31 @@
   &lt;/forrest:view&gt;
 &lt;/forrest:views&gt;
       </pre>
-<p>A contract has to request the data model it want to transform. This 
-        happends by defining forrest:properties which have the same name like 
-        the contract. In our case we want the HTML rendered from intermediate 
-        format (**.body.xml). This we are going to include via: <span class="codefrag">&lt;jx:import uri="cocoon://#{$cocoon/parameters/getRequest}.body.xml"/&gt;
-         </span>
-</p>
-<p>Contracts can offer some property configuration of the outcome of 
-            the transformation. In our case <span class="codefrag">&lt;forrest:property name="content-main-conf"&gt;
+<p>
+        A contract has to request the data model it want to transform. This
+        happends by defining forrest:properties which have the same name like
+        the contract. In our case we want the HTML rendered from intermediate
+        format (**.body.xml). This we are going to include via: <span class="codefrag">
+&lt;jx:import uri="cocoon://#{$cocoon/parameters/getRequest}.body.xml"/&gt;
+        </span>
+      </p>
+<p>
+        Contracts can offer some property configuration of the outcome of the
+        transformation. In our case <span class="codefrag">
+&lt;forrest:property name="content-main-conf"&gt;
         &lt;headings type="underlined"/&gt;
-      &lt;/forrest:property&gt;. </span>
-</p>
-<p> Lets try our new structurer by pointing to 
-        <span class="codefrag">http://localhost:8888/index.html</span>. We will see only the 
-        main content. Now let us add the section navigation to our structurer. 
-        The contract usage in the structurer can be looked up in 
-        ls.contracts.html. Our structurer now looks like: </p>
-<pre class="code">&lt;forrest:views 
+      &lt;/forrest:property&gt;
+        . </span>
+      </p>
+<p>
+        Lets try our new structurer by pointing to
+        <span class="codefrag">http://localhost:8888/index.html</span>. We will see only the main
+        content. Now let us add the section navigation to our structurer. The
+        contract usage in the structurer can be looked up in ls.contracts.html.
+        Our structurer now looks like:
+      </p>
+<pre class="code">
+&lt;forrest:views 
   xmlns:forrest="http://apache.org/forrest/templates/1.0"
   xmlns:jx="http://apache.org/cocoon/templates/jx/1.0"&gt;
   &lt;forrest:view type="html"&gt;
@@ -345,20 +380,24 @@
   &lt;/forrest:view&gt;
 &lt;/forrest:views&gt;
       </pre>
-<p> We now find the main content and the section navigation after each 
-        other and in the order we placed them in the structurer, but we want it 
-        next to each other (left: nav-section; right: content-main). </p>
+<p>
+        We now find the main content and the section navigation after each other
+        and in the order we placed them in the structurer, but we want it next
+        to each other (left: nav-section; right: content-main).
+      </p>
 </div>
 <a name="hookstructurer" title="Hooks in the structurer"> </a>
 <h3 class="underlined_5">Hooks in the structurer</h3>
 <div class="section">
-<p> We will use now the first time a <span class="codefrag">&lt;forrest:hook name="layoutId"/&gt;
-         </span>. Hooks are the styling side of the structurer. We can imitate 
-        arbitrary html skeleton with their help. Before we explain how to use 
-        your own css in the structurer, we will use the default css. You can 
-        see in our example that we have css included. That is a default 
-        fallback coming from the implementation. In this common.css we can find 
-        </p>
+<p>
+        We will use now the first time a <span class="codefrag">
+&lt;forrest:hook name="layoutId"/&gt;
+        </span>. Hooks are the styling side of the structurer. We can imitate
+        arbitrary html skeleton with their help. Before we explain how to use
+        your own css in the structurer, we will use the default css. You can see
+        in our example that we have css included. That is a default fallback
+        coming from the implementation. In this common.css we can find
+      </p>
 <pre class="code">/* menu */
 #leftbar {
     width: 25%;
@@ -367,17 +406,25 @@
     border: thin dashed #565248;
 }
       </pre>
-<p> 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> If we want to put the nav-section contract into the left-hand side 
-        position of the site we need to place the contract into that hook. 
-        Like: </p>
-<pre class="code">&lt;forrest:hook name="leftbar"&gt;
+<p>
+        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>
+        If we want to put the nav-section contract into the left-hand side
+        position of the site we need to place the contract into that hook. Like:
+      </p>
+<pre class="code">
+&lt;forrest:hook name="leftbar"&gt;
   &lt;!-- Include contract here --&gt;
 &lt;/forrest:hook&gt;
       </pre>
-<p> Our structurer will then look like: </p>
-<pre class="code">&lt;forrest:views 
+<p>
+        Our structurer will then look like:
+      </p>
+<pre class="code">
+&lt;forrest:views 
   xmlns:forrest="http://apache.org/forrest/templates/1.0"
   xmlns:jx="http://apache.org/cocoon/templates/jx/1.0"&gt;
   &lt;forrest:view type="html"&gt;
@@ -409,16 +456,23 @@
 <a name="cssstructurer" title="CSS in the structurer"> </a>
 <h3 class="underlined_5">CSS in the structurer</h3>
 <div class="section">
-<p>We now know how to place contracts and hooks in our structurer. Until 
-        this stage we only used the common.css. CSS-support of the structurer 
-        is as easy as placing contracts/hooks. To override the common.css 
-        stylesheet we use another tag within our structurer <span class="codefrag">&lt;forrest:css /&gt;
-        </span>. </p>
-<p>You can add inline and linked css with the structurer. As soon as you 
-        use forrest:css you will disable the fallback css support from 
-        forrest. With this tag we tell the dispatcher that we want to override the common.css.  
-        After adding the following to our index.fv the design will be different.</p>
-<pre class="code">&lt;forrest:css &gt;
+<p>
+        We now know how to place contracts and hooks in our structurer. Until
+        this stage we only used the common.css. CSS-support of the structurer is
+        as easy as placing contracts/hooks. To override the common.css
+        stylesheet we use another tag within our structurer <span class="codefrag">
+&lt;forrest:css /&gt;
+        </span>.
+      </p>
+<p>
+        You can add inline and linked css with the structurer. As soon as you
+        use forrest:css you will disable the fallback css support from forrest.
+        With this tag we tell the dispatcher that we want to override the
+        common.css. After adding the following to our index.fv the design will
+        be different.
+      </p>
+<pre class="code">
+&lt;forrest:css &gt;
 /* Extra css */
 /* menu */
 #leftbar {
@@ -427,18 +481,25 @@
   background: #CCCCFF;
   border: thin solid #000000;
 }
-&lt;/forrest:css&gt; </pre>
-<p> We just changed the border-style to 'solid', the background to 
-        '#CCCCFF' and the color to '#000000'.  So you see a white page where the menu is surrounded by a solid 
-        border with the defined background.</p>
+&lt;/forrest:css&gt;
+      </pre>
+<p>
+        We just changed the border-style to 'solid', the background to '#CCCCFF'
+        and the color to '#000000'. So you see a white page where the menu is
+        surrounded by a solid border with the defined background.
+      </p>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-        <span class="codefrag">&lt;forrest:css /&gt;</span> needs to be the direct child of 
-        <span class="codefrag">&lt;forrest:view type="html"&gt;</span>
+        <span class="codefrag">
+&lt;forrest:css /&gt;
+        </span> needs to be the direct child of <span class="codefrag">
+&lt;forrest:view type="html"&gt;
+        </span>
       </div>
 </div>
-<pre class="code">&lt;forrest:views 
+<pre class="code">
+&lt;forrest:views 
   xmlns:forrest="http://apache.org/forrest/templates/1.0"
   xmlns:jx="http://apache.org/cocoon/templates/jx/1.0"&gt;
   &lt;forrest:view type="html"&gt;
@@ -476,9 +537,12 @@
   &lt;/forrest:view&gt;
 &lt;/forrest:views&gt;
       </pre>
-<p>As a 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 to our inline css: </p>
+<p>
+        As a 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 to our inline css:
+      </p>
 <pre class="code">
 /* The actual content */
 #content {
@@ -486,9 +550,12 @@
   padding: 0 20px 0 20px;
   background: #B9D3EE;
 }</pre>
-<p> Then we have to add the 'content-main' contract to the 'content' 
-        hook. The resulting structurer looks like: </p>
-<pre class="code">&lt;forrest:views 
+<p>
+        Then we have to add the 'content-main' contract to the 'content' hook.
+        The resulting structurer looks like:
+      </p>
+<pre class="code">
+&lt;forrest:views 
   xmlns:forrest="http://apache.org/forrest/templates/1.0"
   xmlns:jx="http://apache.org/cocoon/templates/jx/1.0"&gt;
   &lt;forrest:view type="html"&gt;
@@ -534,42 +601,65 @@
   &lt;/forrest:view&gt;
 &lt;/forrest:views&gt;
       </pre>
-<p> We are now able to place contracts into the layout container and add 
-        custom css to the structurer. </p>
+<p>
+        We are now able to place contracts into the layout container and add
+        custom css to the structurer.
+      </p>
 </div>
 <a name="Linking+to+an+external+css+file" title="Linking to an external css file"> </a>
 <h3 class="underlined_5">Linking to an external css file</h3>
 <div class="section">
 <div class="note">
 <div class="label">Note</div>
-<div class="content">This will change for the next version of views (v3) where we use a 
-        generic contract instead of the standalone element (forrest:css). </div>
+<div class="content">
+        This will change for the next version of views (v3) where we use a
+        generic contract instead of the standalone element (forrest:css).
+      </div>
 </div>
-<p>Make sure your project has the following directory structure. If it 
-        doesn't you'll have to create it. "common" is the fallback for all 
-        themes, if you want to override the css for a specific theme replace 
-        "common" with "themeName". This is where Forrest will look for external 
-        css stylesheets. </p>
+<p>
+        Make sure your project has the following directory structure. If it
+        doesn't you'll have to create it. "common" is the fallback for all
+        themes, if you want to override the css for a specific theme replace
+        "common" with "themeName". This is where Forrest will look for external
+        css stylesheets.
+      </p>
 <pre class="code">
         $projectHome\src\documentation\resources\themes\common\css</pre>
-<p>Where $projectHome is the directory where your project exists.</p>
-<p>Put your css stylesheets in this directory. For arguement's sake let's say 
-        it's called mystyles.css</p>
-<p>Edit your common.fv structurer (or whatever structurer (theme) you are using). This 
-        will probably be some where in: </p>
+<p>
+        Where $projectHome is the directory where your project exists.
+      </p>
+<p>
+        Put your css stylesheets in this directory. For arguement's sake let's
+        say it's called mystyles.css
+      </p>
+<p>
+        Edit your common.fv structurer (or whatever structurer (theme) you are
+        using). This will probably be some where in:
+      </p>
 <pre class="code">$projectHome\src\documentation\content\xdocs</pre>
-<p>or if you want to override it for the whole project in:</p>
+<p>
+        or if you want to override it for the whole project in:
+      </p>
 <pre class="code">$projectHome\src\documentation\resources\themes\</pre>
-<p>Add the following element to the *.fv file:</p>
-<pre class="code">&lt;forrest:css url="styles.css" media="screen" theme="pelt"/&gt;
-        </pre>
-<p>
-<strong>Important!</strong> This must appear straight after the "view 
-        type" element (as first child): </p>
-<pre class="code">&lt;forrest:view type="html"&gt;</pre>
-<pre class="code">&lt;forrest:css url="mystyles.css" media="screen" theme="pelt"/&gt;
-        </pre>
-<p>The attributes are: </p>
+<p>
+        Add the following element to the *.fv file:
+      </p>
+<pre class="code">
+&lt;forrest:css url="styles.css" media="screen" theme="pelt"/&gt;
+      </pre>
+<p>
+        <strong>Important!</strong> This must appear straight after the "view
+        type" element (as first child):
+      </p>
+<pre class="code">
+&lt;forrest:view type="html"&gt;
+      </pre>
+<pre class="code">
+&lt;forrest:css url="mystyles.css" media="screen" theme="pelt"/&gt;
+      </pre>
+<p>
+        The attributes are:
+      </p>
 <ol>
         <li>the url where the css exist (NOTE: it will be rewritten to "../themes/mystyles.css").</li>
         <li>the media type, you can set different styles for screen and print. 
@@ -578,33 +668,41 @@
         <li>the theme, "pelt" is the default theme (another is the "common" theme). Change this if you 
           are using your own theme.</li>
       </ol>
-<p>You can have as many css links as you like, and they'll appear in the 
-        head of your document in same order as they are in the .fv file.</p>
+<p>
+        You can have as many css links as you like, and they'll appear in the
+        head of your document in same order as they are in the .fv file.
+      </p>
 <div class="fixme">
 <div class="label">Fixme (thorsten)</div>
-<div class="content"> Add more information of recent threads around 
-        css in the structurer and information how you add an @import? Use e.g. 
-        <a href="http://marc.theaimsgroup.com/?t=113471292700001&amp;r=1&amp;w=2">http://marc.theaimsgroup.com/?t=113471292700001&amp;r=1&amp;w=2</a> 
-        </div>
+<div class="content">
+        Add more information of recent threads around css in the structurer and
+        information how you add an @import? Use e.g.
+        <a href="http://marc.theaimsgroup.com/?t=113471292700001&amp;r=1&amp;w=2">http://marc.theaimsgroup.com/?t=113471292700001&amp;r=1&amp;w=2</a>
+      </div>
 </div>
 </div>
 </div>
 <a name="Further Reading" title="Further Reading"> </a>
 <h2 class="underlined_10">Further Reading</h2>
 <div class="section">
-<p> Congratulations you are now able to work with the structurer. From here 
-      we recommend to read the following How-Tos: </p>
+<p>
+      Congratulations you are now able to work with the structurer. From here we
+      recommend to read the following How-Tos:
+    </p>
 <ul>
       <li>
-        <a href="../how/howto-dispatcher-contracts.html">Create your own contract 
+<a href="../how/howto-dispatcher-contracts.html">Create your own contract 
           implementation</a>
-      </li>
+</li>
     </ul>
 </div>
 <a name="Feedback" title="Feedback"> </a>
 <h2 class="underlined_10">Feedback</h2>
 <div class="section">
-<p> Please provide feedback about this document via the <a href="http://forrest.apache.org/mail-lists.html">mailing lists</a>. </p>
+<p>
+      Please provide feedback about this document via the
+      <a href="http://forrest.apache.org/mail-lists.html">mailing lists</a>.
+    </p>
 </div>
 <!--+ |end content-main +-->
 </div>

Added: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/images/fix.jpg
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/images/fix.jpg?view=auto&rev=527684
==============================================================================
Binary file - no diff available.

Propchange: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/images/fix.jpg
------------------------------------------------------------------------------
    svn:mime-type = image/jpeg

Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/images/project.png
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/images/project.png?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
Binary files - no diff available.

Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/index.dispatcher.css
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/index.dispatcher.css?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/index.dispatcher.css (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/index.dispatcher.css Wed Apr 11 14:33:35 2007
@@ -1,8 +1,8 @@
 
+
   
   
-  
-  
+
   
 /* branding-theme-profiler-theme: Pelt */ 
 #header .round-top-left-small {
@@ -46,5 +46,5 @@
     background-position: bottom left;
 }
             
-  
+
   

Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/index.html
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/index.html?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/index.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/index.html Wed Apr 11 14:33:35 2007
@@ -4,7 +4,7 @@
         <link href="themes/common.css" media="screen" rel="alternate stylesheet" title="common" type="text/css" />
         <link href="themes/leather-dev.css" media="screen" rel="alternate stylesheet" title="common" type="text/css" />
         <link href="themes/pelt.screen.css" media="screen" rel="stylesheet" title="Pelt" type="text/css" />
-        
+
         <link href="index.dispatcher.css" media="screen" rel="stylesheet" title="Pelt" type="text/css" />
         <link href="themes/pelt.print.css" media="print" rel="stylesheet" title="Pelt" type="text/css" />
         <style type="text/css">/* Extra css */ 
@@ -219,152 +219,199 @@
 <!--+ |start content-main +-->
 <div class="warning">
 <div class="label">Warning</div>
-<div class="content"> The "dispatcher" is new functionality which is still in 
-      development phase. That is why it is in the "whiteboard" section of the 
-      Forrest distribution. We are working at the moment on moving this plugin 
-      from the whiteboard into the core plugins. Further all dispatcher related 
-      documents will be moved into the plugin as well. See <a href="http://forrest.apache.org/docs_0_80/status-themes.html">Status of 
-      Themes: Skins and Dispatcher</a>. </div>
+<div class="content">
+      The "dispatcher" is new functionality which is still in development phase.
+      That is why it is in the "whiteboard" section of the Forrest distribution.
+      We are working at the moment on moving this plugin from the whiteboard
+      into the core plugins. Further all dispatcher related documents will be
+      moved into the plugin as well. See
+      <a href="http://forrest.apache.org/docs_0_80/status-themes.html">Status
+      of Themes: Skins and Dispatcher</a>.
+    </div>
 </div>
 <a name="introduction" title="Introduction"> </a>
 <h2 class="underlined_10">Introduction</h2>
 <div class="section">
-<p> As stated in the Skin documentation the aim of the Forrest skins is 
-        to provide many capabilities so that extra skins are not needed. 
-        Experience showed that many Forrest users still decided to create a new 
-        skin because the default skin did not offer the features that they 
-        wanted or they "just" needed extra content in some pages. We introduced 
-        skinconf.xml where the user could configure some features of skins but 
-        it was up to the skin to support it and did not solve the problem to 
-        add page specific extra content. That led us to develop a new concept 
-        of creating skins (we called the result "themes") which would be more 
-        easily extensible by a user. </p>
+<p>
+        As stated in the Skin documentation the aim of the Forrest skins is to
+        provide many capabilities so that extra skins are not needed. Experience
+        showed that many Forrest users still decided to create a new skin
+        because the default skin did not offer the features that they wanted or
+        they "just" needed extra content in some pages. We introduced
+        skinconf.xml where the user could configure some features of skins but
+        it was up to the skin to support it and did not solve the problem to add
+        page specific extra content. That led us to develop a new concept of
+        creating skins (we called the result "themes") which would be more
+        easily extensible by a user.
+      </p>
 </div>
 <a name="dispatcher" title="Dispatcher - advanced separation of concerns"> </a>
 <h2 class="underlined_10">Dispatcher - advanced separation of concerns</h2>
 <div class="section">
-<p> The aim of the "dispatcher" concept is to provide a flexible 
-        framework for creating site and page specific layout in different 
-        formats from different content through an advanced seperation of 
-        concerns.</p>
-<p>The dispatcher is a filter that limits the data-model to a minimum by 
-        only requesting what the structurer (e.g. common-html.vt.xml) need. This leads to 
-        a different URL handling focus - away from document centric. A document 
-        can (but does not have to) be behind a certain URL. Like said a 
-        structurer can request any given data as input not only a document and 
-        the forrest core contracts (like navigation). It may be the main 
-        enhancement in comparison to skins that this concept lets you easily 
-        extend the default data models provided by forrest.</p>
-<p>Since the dispatcher has implemented a fallback concept it makes 
-        maintenance of custom themes which are based on forrest core ones very 
-        easy and less time consuming. The principal is to override or extend 
-        only certain parts (contracts) of the core. This is based on the 
-        observation that normally only a small percentage of core skin 
-        contracts have been changed. At the same time the new plugin system 
-        emerged. Plugins are a way of extending Forrest to satisfy 
-        site-specific needs. This includes to provide for plugin specific 
-        contracts.</p>
+<p>
+        The aim of the "dispatcher" concept is to provide a flexible framework
+        for creating site and page specific layout in different formats from
+        different content through an advanced seperation of concerns.
+      </p>
+<p>
+        The dispatcher is a filter that limits the data-model to a minimum by
+        only requesting what the structurer (e.g. common-html.vt.xml) need. This
+        leads to a different URL handling focus - away from document centric. A
+        document can (but does not have to) be behind a certain URL. Like said a
+        structurer can request any given data as input not only a document and
+        the forrest core contracts (like navigation). It may be the main
+        enhancement in comparison to skins that this concept lets you easily
+        extend the default data models provided by forrest.
+      </p>
+<p>
+        Since the dispatcher has implemented a fallback concept it makes
+        maintenance of custom themes which are based on forrest core ones very
+        easy and less time consuming. The principal is to override or extend
+        only certain parts (contracts) of the core. This is based on the
+        observation that normally only a small percentage of core skin contracts
+        have been changed. At the same time the new plugin system emerged.
+        Plugins are a way of extending Forrest to satisfy site-specific needs.
+        This includes to provide for plugin specific contracts.
+      </p>
 <a name="structurer" title="Structurer - configuration for themes"> </a>
 <h3 class="underlined_5">Structurer - configuration for themes</h3>
 <div class="section">
-<p> We developed<strong> the structurer</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 
-      their positions. These elements were 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 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"> 
-      initial contract list </a> </p>
-<p> Around this contracts we developed a configuration Domain Specific 
-      Language - called <strong>the structurer</strong>. The 
-      <strong>structurer</strong> allows us to define the order in which 
-      <strong>forrest:contract</strong>s appear, and also to group them using 
-      <strong>forrest:hook</strong>s. </p>
-<p> <strong>forrest:hook</strong>s are containers 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 e.g. 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> <strong>forrest:contract</strong>s are functionality or extra content 
-      that a theme can use to display the request. Sometimes a contract 
-      delivers <strong>format-specific markup</strong>, other times it delivers 
-      a <strong>format-independent string</strong>. We decide different kind of 
-      contracts, static one (like described in the contract howto), semi static 
-      (which offer configuration parameter in the structurer) and dynamic 
-      contracts (which offer semi-static configuration and/or requesting the 
-      content).  </p>
-<p> The structurer is also a configuration file for the dispatcher. 
-        The new thinking on the dispatcher is that one can include any content 
-        from any given business service by dispatching a request against it. In 
-        "old fashion" skins and in v1 contracts we assumed a given data model. 
-        In the dispatcher there is <strong>no</strong> given data model any 
-        more. All data has to be defined in the structurer so that they can be 
-        dispatched. </p>
+<p>
+          We developed<strong> the structurer</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 their positions. These elements were 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 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">
+          initial contract list </a>
+        </p>
+<p>
+          Around this contracts we developed a configuration Domain Specific
+          Language - called <strong>the structurer</strong>. The
+          <strong>structurer</strong> allows us to define the order in which
+          <strong>forrest:contract</strong>s appear, and also to group them
+          using <strong>forrest:hook</strong>s.
+        </p>
+<p>
+          <strong>forrest:hook</strong>s are containers 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 e.g. 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>
+          <strong>forrest:contract</strong>s are functionality or extra content
+          that a theme can use to display the request. Sometimes a contract
+          delivers <strong>format-specific markup</strong>, other times it
+          delivers a <strong>format-independent string</strong>. We decide
+          different kind of contracts, static one (like described in the
+          contract howto), semi static (which offer configuration parameter in
+          the structurer) and dynamic contracts (which offer semi-static
+          configuration and/or requesting the content).
+        </p>
+<p>
+          The structurer is also a configuration file for the dispatcher. The
+          new thinking on the dispatcher is that one can include any content
+          from any given business service by dispatching a request against it.
+          In "old fashion" skins and in v1 contracts we assumed a given data
+          model. In the dispatcher there is <strong>no</strong> given data model
+          any more. All data has to be defined in the structurer so that they
+          can be dispatched.
+        </p>
 </div>
 <a name="contracts" title="Contracts - grouped functionality"> </a>
 <h3 class="underlined_5">Contracts - grouped functionality</h3>
 <div class="section">
-<p>The result of the leather-dev development was grouped functionality 
-          in named containers. We gave those code snippets names (based on their 
-          functionality) and called them <strong>contracts</strong>. This naming enabled us to 
-          keep the contract separate from the positioning of the code itself. Furthermore, 
-          since major parts of the code of skins has never been documented, 
-          we started to add for each contract a description and an explanation on
-          how to use this contract. The skinconf.xml gave an excellent 
-          source for this documentation effort, since it described most 
-          features of the pelt skin.</p>
-<p>Contracts are standalone, self explaining, configurable 
-            pieces of xsl templates created purely for ease of maintenance.</p>
-<p>Since these contracts are working from the input given in the <a href="#structurer">structurer</a>, it works on different input 
-            sources. One can pass variables into the contracts that can 
-            be used to apply presentation logic in the xsl (like sorting order, 
-            ...).</p>
+<p>
+          The result of the leather-dev development was grouped functionality in
+          named containers. We gave those code snippets names (based on their
+          functionality) and called them <strong>contracts</strong>. This naming
+          enabled us to keep the contract separate from the positioning of the
+          code itself. Furthermore, since major parts of the code of skins has
+          never been documented, we started to add for each contract a
+          description and an explanation on how to use this contract. The
+          skinconf.xml gave an excellent source for this documentation effort,
+          since it described most features of the pelt skin.
+        </p>
+<p>
+          Contracts are standalone, self explaining, configurable pieces of xsl
+          templates created purely for ease of maintenance.
+        </p>
+<p>
+          Since these contracts are working from the input given in the
+          <a href="#structurer">structurer</a>, it works on
+          different input sources. One can pass variables into the contracts
+          that can be used to apply presentation logic in the xsl (like sorting
+          order, ...).
+        </p>
 </div>
 </div>
 <a name="background" title="Background"> </a>
 <h2 class="underlined_10">Background</h2>
 <div class="section">
-<p> The problem with the forrest skins so far has been that even if 
-        "only" the design changed (html-skeleton), we still had to write a 
-        completely new skin and implement all functionality. Another problem 
-        was that the functionality was not easily extensible by a user. We 
-        decided to support a standard regarding naming conventions for css 
-        elements. This standard has been developed on the <a href="http://www.oscom.org/events/oscom4/proposals/skins.html"> OSCOM 
-        website</a>, where you can find some more background information.</p>
+<p>
+        The problem with the forrest skins so far has been that even if "only"
+        the design changed (html-skeleton), we still had to write a completely
+        new skin and implement all functionality. Another problem was that the
+        functionality was not easily extensible by a user. We decided to support
+        a standard regarding naming conventions for css elements. This standard
+        has been developed on the
+        <a href="http://www.oscom.org/events/oscom4/proposals/skins.html">
+        OSCOM website</a>, where you can find some more background information.
+      </p>
 <a name="nc-definition" title="Definition of naming conventions"> </a>
 <h3 class="underlined_5">Definition of naming conventions</h3>
 <div class="section">
-<p> "A naming convention is an attempt to systematize names in a field 
-          so they unambiguously convey similar information in a similar 
-          manner." <a href="http://en.wikipedia.org/wiki/Naming_conventions">wikipedia</a> 
-          </p>
+<p>
+          "A naming convention is an attempt to systematize names in a field so
+          they unambiguously convey similar information in a similar manner."
+          <a href="http://en.wikipedia.org/wiki/Naming_conventions">wikipedia</a>
+        </p>
 </div>
 <a name="leather" title="leather-dev"> </a>
 <h3 class="underlined_5">leather-dev</h3>
 <div class="section">
-<p> That led to the development of the "leather-dev" skin which 
-          established a semantic container approach for div elements. 
-          Leather-dev evolved from the "pelt" skin and used almost the same 
-          functionality (contracts). We had started to encapsulate functional 
-          code into templates, but there have been still in 4 xsl files and without 
-          any documentation on what they are doing and how to use them. The 
-          problems with leather-dev was pointed out in the mail "<a href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=111049344517653">status on leather-dev?</a>". The main proplem was to limit users to 
-          only one html-skeleton which was way too limiting regarding design. Since 
-          we had now grouped functionality in named containers we were ready to 
-          start the dispatcher (aka forrest:views).</p>
+<p>
+          That led to the development of the "leather-dev" skin which
+          established a semantic container approach for div elements.
+          Leather-dev evolved from the "pelt" skin and used almost the same
+          functionality (contracts). We had started to encapsulate functional
+          code into templates, but there have been still in 4 xsl files and
+          without any documentation on what they are doing and how to use them.
+          The problems with leather-dev was pointed out in the mail
+          "<a href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=111049344517653">status
+          on leather-dev?</a>". The main proplem was to limit users to only one
+          html-skeleton which was way too limiting regarding design. Since we
+          had now grouped functionality in named containers we were ready to
+          start the dispatcher (aka forrest:views).
+        </p>
 </div>
 </div>
 <a name="info" title="Further information"> </a>
 <h2 class="underlined_10">Further information</h2>
 <div class="section">
-<p> See the various How-to documents about the dispatcher, starting with 
-              the <a href="how/howto-dispatcher-quickstart.html">quickstart</a>. It would also be useful to familiarise yourself with some of the terms used in the dispatcher, the <a href="dispatcher-glossary.html">Dispatcher Glossary</a> contains some of the terms used.
+<p>
+        See the various How-to documents about the dispatcher, starting with the
+        <a href="how/howto-dispatcher-quickstart.html">quickstart</a>. It would also be
+        useful to familiarise yourself with some of the terms used in the
+        dispatcher, the <a href="dispatcher-glossary.html">Dispatcher Glossary</a>
+        contains some of the terms used.
+      </p>
+<p>
+        Apache Forrest 1.0 Specification (Draft, not yet published):
+        <span class="codefrag">site-author/content/xdocs/TR/2005/WD-forrest10.html</span>
       </p>
-<p> Apache Forrest 1.0 Specification (Draft, not yet published): 
-        <span class="codefrag">site-author/content/xdocs/TR/2005/WD-forrest10.html</span> </p>
 </div>
 <!--+ |end content-main +-->
 </div>

Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/int/index.dispatcher.css
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/int/index.dispatcher.css?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/int/index.dispatcher.css (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/int/index.dispatcher.css Wed Apr 11 14:33:35 2007
@@ -1,9 +1,4 @@
 
-  
-  
-  
-  
-  
 /* branding-theme-profiler-theme: Pelt */ 
 #header .round-top-left-small {
     background-image: url(../themes/images/roundcorner-t-l-5-bg294563-stroke4A6D8C-fg4A6D8C.png);
@@ -46,5 +41,5 @@
     background-position: bottom left;
 }
             
-  
+
   

Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/int/index.html
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/int/index.html?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/int/index.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/int/index.html Wed Apr 11 14:33:35 2007
@@ -4,7 +4,7 @@
         <link href="../themes/common.css" media="screen" rel="alternate stylesheet" title="common" type="text/css" />
         <link href="../themes/leather-dev.css" media="screen" rel="alternate stylesheet" title="common" type="text/css" />
         <link href="../themes/pelt.screen.css" media="screen" rel="stylesheet" title="Pelt" type="text/css" />
-        
+
         <link href="../int/index.dispatcher.css" media="screen" rel="stylesheet" title="Pelt" type="text/css" />
         <link href="../themes/pelt.print.css" media="print" rel="stylesheet" title="Pelt" type="text/css" />
         <style type="text/css">/* Extra css */ 
@@ -173,19 +173,24 @@
 <a name="introduction" title="Introduction"> </a>
 <h2 class="underlined_10">Introduction</h2>
 <div class="section">
-<p> Since the dispatcher is in the whiteboard, we can afford to use the 
-        latest features available in forrest. This helps to test these new 
-        features and to be prepared for the future when this feature is 
-        standard.</p>
+<p>
+        Since the dispatcher is in the whiteboard, we can afford to use the
+        latest features available in forrest. This helps to test these new
+        features and to be prepared for the future when this feature is
+        standard.
+      </p>
 </div>
 <a name="fpx" title="forrest.properties.xml"> </a>
 <h2 class="underlined_10">forrest.properties.xml</h2>
 <div class="section">
-<p> We needed to prevent having references from the core to a plugin. 
-        This can be done with the new properties system. You can override any 
-        of the following values via a <span class="codefrag">forrest.properties.xml</span> in your 
-        project.</p>
-<pre class="code">  &lt;property name="dispatcher.theme" value="pelt"/&gt;
+<p>
+        We needed to prevent having references from the core to a plugin. This
+        can be done with the new properties system. You can override any of the
+        following values via a <span class="codefrag">forrest.properties.xml</span> in your
+        project.
+      </p>
+<pre class="code">
+  &lt;property name="dispatcher.theme" value="pelt"/&gt;
   &lt;property name="dispatcher.fallback.theme" value="common"/&gt;
   &lt;property name="dispatcher.theme-ext" value=".fv"/&gt;
   &lt;property name="dispatcher.fallback.theme-ext" value=".fv"/&gt;
@@ -196,17 +201,22 @@
 <a name="lm" title="locationmap.xml"> </a>
 <h2 class="underlined_10">locationmap.xml</h2>
 <div class="section">
-<p> One of the main features of the dispatcher is its fallback mechanism. 
-        We are not only looking into one or two places but a sophisticated list 
-        of locations. These locations are defined in the locationmap.xml. Like 
-        with the forrest.properties.xml you can override any match in there by 
-        implementing it in your project locationmap.xml.</p>
+<p>
+        One of the main features of the dispatcher is its fallback mechanism. We
+        are not only looking into one or two places but a sophisticated list of
+        locations. These locations are defined in the locationmap.xml. Like with
+        the forrest.properties.xml you can override any match in there by
+        implementing it in your project locationmap.xml.
+      </p>
 <a name="handson" title="Hands on the lm"> </a>
 <h3 class="underlined_5">Hands on the lm</h3>
 <div class="section">
-<p>The resolving process of the structurer responsible for the URL 
-            has implemented a high amount of fallbacks. Let us have a look.</p>
-<pre class="code">&lt;match pattern="resolve.structurer.**"&gt;
+<p>
+          The resolving process of the structurer responsible for the URL has
+          implemented a high amount of fallbacks. Let us have a look.
+        </p>
+<pre class="code">
+&lt;match pattern="resolve.structurer.**"&gt;
   &lt;!-- 
       FIXME - Problem with the pattern
       ********************************
@@ -301,7 +311,8 @@
       src="{lm:dispatcher.themer}/themes/{properties:dispatcher.fallback.theme}{properties:dispatcher.fallback.theme-ext}" 
       /&gt;
   &lt;/select&gt;
-&lt;/match&gt; </pre>
+&lt;/match&gt;
+        </pre>
 </div>
 </div>
 <!--+ |end content-main +-->

Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/linkmap.dispatcher.css
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/linkmap.dispatcher.css?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/linkmap.dispatcher.css (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/linkmap.dispatcher.css Wed Apr 11 14:33:35 2007
@@ -41,5 +41,5 @@
     background-position: bottom left;
 }
             
-  
+
   

Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/linkmap.html
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/linkmap.html?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/linkmap.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/linkmap.html Wed Apr 11 14:33:35 2007
@@ -4,7 +4,7 @@
         <link href="themes/common.css" media="screen" rel="alternate stylesheet" title="common" type="text/css" />
         <link href="themes/leather-dev.css" media="screen" rel="alternate stylesheet" title="common" type="text/css" />
         <link href="themes/pelt.screen.css" media="screen" rel="stylesheet" title="Pelt" type="text/css" />
-        
+
         <link href="linkmap.dispatcher.css" media="screen" rel="stylesheet" title="Pelt" type="text/css" />
         <link href="themes/pelt.print.css" media="print" rel="stylesheet" title="Pelt" type="text/css" />
         <style type="text/css">/* Extra css */ 
@@ -27,7 +27,7 @@
 <!--+|start favicon +-->
 <script src="themes/menu.js" type="text/javascript"> </script>
 <!--+ |start content-title +-->
-<title>Site Linkmap</title>
+<title>Site Linkmap Table of Contents</title>
 <!--+ |end content-title +-->
 </head>
 <body>
@@ -176,98 +176,83 @@
 </div>
 <div id="content">
 <!--+ |start content-title +-->
-<h1 class="content-title">Site Linkmap</h1>
+<h1 class="content-title">Site Linkmap Table of Contents</h1>
 <!--+ |end content-title +-->
 <!--+ |start content-abstract +-->
 <!--+ |end content-abstract +-->
 <!--+ |start content-minitoc +-->
-<div id="content-minitoc-area">
-<ul class="minitoc">
-<li>
-<a href="#Table+of+Contents">Table of Contents</a>
-</li>
-</ul>
-</div>
 <!--+ |end minitoc +-->
 <!--+ |start content-main +-->
-<a name="Table+of+Contents" title="Table of Contents"> </a>
-<h2 class="underlined_10">Table of Contents</h2>
-<div class="section">
+<p>
+          This is a map of the complete site and its structure.
+        </p>
 <ul>
 <li>
-<a href="">org.apache.forrest.plugin.internal.views</a>   _________________________  <em>site</em>
+<a>org.apache.forrest.plugin.internal.views</a>  ___________________  <em>site</em>
 </li>
 <ul>
-
   <ul>
 <li>
-<a href="">About</a>   _________________________  <em>about</em>
+<a>About</a>  ___________________  <em>about</em>
 </li>
 <ul>
     <ul>
 <li>
-<a href="index.html">Dispatcher development</a>   _________________________  <em>dispatcher-concept</em>
+<a href="index.html">Dispatcher development</a>  ___________________  <em>dispatcher-concept</em>
 </li>
 </ul>
     <ul>
 <li>
-<a href="dispatcher-glossary.html">Glossary</a>   _________________________  <em>glossary</em>
-</li>
+<a href="dispatcher-glossary.html">Glossary</a>  ___________________  <em>glossary</em> : (FIXME: add content) Dispactcher related terms and meanings</li>
 </ul>
     <ul>
 <li>
-<a href="changes.html">Changes</a>   _________________________  <em>changes</em>
-</li>
+<a href="changes.html">Changes</a>  ___________________  <em>changes</em> : History of Changes</li>
 </ul>
     <ul>
 <li>
-<a href="todo.html">Todo</a>   _________________________  <em>todo</em>
-</li>
+<a href="todo.html">Todo</a>  ___________________  <em>todo</em> : Todo List</li>
 </ul>
   </ul>
 </ul>
   <ul>
 <li>
-<a href="">How to</a>   _________________________  <em>dispatcher</em>
+<a>How to</a>  ___________________  <em>dispatcher</em>
 </li>
 <ul>
     <ul>
 <li>
-<a href="how/howto-dispatcher-quickstart.html">Quickstart</a>   _________________________  <em>quickstart</em>
+<a href="how/howto-dispatcher-quickstart.html">Quickstart</a>  ___________________  <em>quickstart</em>
 </li>
 </ul>
     <ul>
 <li>
-<a href="how/howto-dispatcher-structurer.html">Structurer</a>   _________________________  <em>structurer</em>
+<a href="how/howto-dispatcher-structurer.html">Structurer</a>  ___________________  <em>structurer</em>
 </li>
 </ul>
     <ul>
 <li>
-<a href="how/howto-dispatcher-contracts.html">Contracts</a>   _________________________  <em>contracts</em>
+<a href="how/howto-dispatcher-contracts.html">Contracts</a>  ___________________  <em>contracts</em>
 </li>
 </ul>
   </ul>
 </ul>
   <ul>
 <li>
-<a href="int/">Internals</a>   _________________________  <em>internals</em>
+<a href="int/">Internals</a>  ___________________  <em>internals</em>
 </li>
 <ul>
     <ul>
 <li>
-<a href="int/index.html">Overview</a>   _________________________  <em>index</em>
+<a href="int/index.html">Overview</a>  ___________________  <em>index</em>
 </li>
 </ul>
   </ul>
 </ul>
 
   
-
-  
-
 </ul>
 </ul>
-</div>
 <!--+ |end content-main +-->
 </div>
 </div>

Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/skin/CommonMessages_de.xml
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/skin/CommonMessages_de.xml?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/skin/CommonMessages_de.xml (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/skin/CommonMessages_de.xml Wed Apr 11 14:33:35 2007
@@ -16,8 +16,8 @@
   limitations under the License.
 -->
 <catalogue>
-  <message key="Font size:">Schriftgrösse:</message>
-  <message key="Last Published:">Zuletzt veröffentlicht:</message>
+  <message key="Font size:">Schriftgr�sse:</message>
+  <message key="Last Published:">Zuletzt ver�ffentlicht:</message>
   <message key="Search">Suche:</message>
   <message key="Search the site with">Suche auf der Seite mit</message>
 </catalogue>

Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/skin/CommonMessages_es.xml
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/skin/CommonMessages_es.xml?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/skin/CommonMessages_es.xml (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/skin/CommonMessages_es.xml Wed Apr 11 14:33:35 2007
@@ -16,9 +16,8 @@
   limitations under the License.
 -->
 <catalogue>
-  <message key="Font size:">Tamaño del texto:</message>
-  <message key="Last Published:">Fecha de publicación:</message>
+  <message key="Font size:">Tama�o del texto:</message>
+  <message key="Last Published:">Fecha de publicaci�n:</message>
   <message key="Search">Buscar</message>
   <message key="Search the site with">Buscar en</message>
 </catalogue>
-

Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/skin/CommonMessages_fr.xml
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/skin/CommonMessages_fr.xml?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/skin/CommonMessages_fr.xml (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/skin/CommonMessages_fr.xml Wed Apr 11 14:33:35 2007
@@ -17,7 +17,7 @@
 -->
 <catalogue>
   <message key="Font size:">Taille :</message>
-  <message key="Last Published:">Dernière publication :</message>
+  <message key="Last Published:">Derni�re publication :</message>
   <message key="Search">Rechercher</message>
   <message key="Search the site with">Rechercher sur le site avec</message>
 </catalogue>

Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/todo.dispatcher.css
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/todo.dispatcher.css?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/todo.dispatcher.css (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/todo.dispatcher.css Wed Apr 11 14:33:35 2007
@@ -1,8 +1,8 @@
 
+
   
   
-  
-  
+
   
 /* branding-theme-profiler-theme: Pelt */ 
 #header .round-top-left-small {
@@ -46,5 +46,5 @@
     background-position: bottom left;
 }
             
-  
+
   

Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/todo.html
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/todo.html?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/todo.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/todo.html Wed Apr 11 14:33:35 2007
@@ -4,7 +4,7 @@
         <link href="themes/common.css" media="screen" rel="alternate stylesheet" title="common" type="text/css" />
         <link href="themes/leather-dev.css" media="screen" rel="alternate stylesheet" title="common" type="text/css" />
         <link href="themes/pelt.screen.css" media="screen" rel="stylesheet" title="Pelt" type="text/css" />
-        
+
         <link href="todo.dispatcher.css" media="screen" rel="stylesheet" title="Pelt" type="text/css" />
         <link href="themes/pelt.print.css" media="print" rel="stylesheet" title="Pelt" type="text/css" />
         <style type="text/css">/* Extra css */ 



Mime
View raw message