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 [1/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
Author: thorsten
Date: Wed Apr 11 14:33:35 2007
New Revision: 527684

URL: http://svn.apache.org/viewvc?view=rev&rev=527684
Log:
Deployment of docs for org.apache.forrest.plugin.internal.dispatcher plugin (deployed by 'deploy-docs' target of plugin build script)

Added:
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/images/fix.jpg   (with props)
Modified:
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/changes.dispatcher.css
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/changes.html
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/changes.rss
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/dispatcher-glossary.dispatcher.css
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/dispatcher-glossary.html
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-contracts.dispatcher.css
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-contracts.html
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-quickstart.dispatcher.css
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-quickstart.html
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-structurer.dispatcher.css
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-structurer.html
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/images/project.png
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/index.dispatcher.css
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/index.html
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/int/index.dispatcher.css
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/int/index.html
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/linkmap.dispatcher.css
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/linkmap.html
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/skin/CommonMessages_de.xml
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/skin/CommonMessages_es.xml
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/skin/CommonMessages_fr.xml
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/todo.dispatcher.css
    forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/todo.html

Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/changes.dispatcher.css
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/changes.dispatcher.css?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/changes.dispatcher.css (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/changes.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/changes.html
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/changes.html?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/changes.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/changes.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="changes.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 */ 
@@ -222,7 +222,7 @@
 <a name="introduction" title="Introduction and explanation of symbols"> </a>
 <h2 class="underlined_10">Introduction and explanation of symbols</h2>
 <div class="section">
-<p>Changes are sorted by "type" and then chronologically with the most recent at the top. These symbols denote the various action types:<img alt="add" class="icon" src="images/add.jpg" />=add, <img alt="update" class="icon" src="images/update.jpg" />=update</p>
+<p>Changes are sorted by "type" and then chronologically with the most recent at the top. These symbols denote the various action types:<img alt="add" class="icon" src="images/add.jpg" />=add, <img alt="fix" class="icon" src="images/fix.jpg" />=fix, <img alt="update" class="icon" src="images/update.jpg" />=update</p>
 </div>
 <a name="version_0.1" title="Version 0.1 (unreleased)"> </a>
 <h2 class="underlined_10">Version 0.1 (unreleased)</h2>
@@ -243,6 +243,10 @@
 <ul>
 <li>
 <img alt="add" class="icon" src="images/add.jpg" />
+        More i18n work by Sjur on Dispatcher. This patch correctly localizes menus &amp; tabs.
+       Committed by TS. Thanks to Sjur Moshagen. See Issue <a href="http://issues.apache.org/jira/browse/FOR-937">FOR-937</a>.</li>
+<li>
+<img alt="add" class="icon" src="images/add.jpg" />
         Add ability to get a list of contracts provided by a plugin. For
         this to work the plugin name must have "plugin" within it, e.g.
         "org.apache.forrest.plugin.input.doap". Requesting
@@ -273,6 +277,14 @@
 <img alt="add" class="icon" src="images/add.jpg" />
         Added contracts and nuggets to the "view" plugins.
        Committed by TS.</li>
+<li>
+<img alt="fix" class="icon" src="images/fix.jpg" />
+        FOR-975 Renaming tiles to panel.
+       Committed by TS. See Issue <a href="http://issues.apache.org/jira/browse/FOR-975">FOR-975</a>.</li>
+<li>
+<img alt="fix" class="icon" src="images/fix.jpg" />
+        Rename to ContractsMessages_en.xml, part of i18n changes by Sjur.
+       Committed by DC. Thanks to Sjur Moshagen. See Issue <a href="http://issues.apache.org/jira/browse/FOR-939">FOR-939</a>.</li>
 <li>
 <img alt="update" class="icon" src="images/update.jpg" />
         i18n: Add LocaleAction action wrapper, and use the locale provided by it.

Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/changes.rss
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/changes.rss?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/changes.rss (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/changes.rss Wed Apr 11 14:33:35 2007
@@ -1,236 +1,296 @@
-<?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE rss PUBLIC "-//Netscape Communications//DTD RSS 0.91//EN" "http://my.netscape.com/publish/formats/rss-0.91.dtd">
-<rss version="0.91"><channel><title>Plugin: dispatcher internal (0.1) Changes</title><link>changes.html</link><description>Plugin: dispatcher internal (0.1) Changes</description><language>en-us</language>
-
-  
-    
-    
-    
-    
-    
-  
-
-    
-  
-   
-   
-   
-   
-   
-   
-
-  
-    
-    
-      <item><title>code add</title><link>changes.html</link><description>code add
-        by
-        RDG
-        :
-        
-        Add ability to get a list of contracts provided by a plugin. For
-        this to work the plugin name must have "plugin" within it, e.g.
-        "org.apache.forrest.plugin.input.doap". Requesting
-        ls.contracts.org.apache.forrest.plugin.input.doap.source.xml
-        will return a source listing of plugins provided by the named plugin.
-        Requesting ls.contracts.org.apache.forrest.plugin.input.doap.[FORMAT] 
-        will return a formatted output document listing all templates supplied
-        by the identified plugin.        
-      </description></item>
-      <item><title>code update
-          (bug FOR-935)
-        </title><link>changes.html</link><description>code update
-        by
-        DC
-          (fixes bug FOR-935)
-        
-        :
-        
-        i18n: Add LocaleAction action wrapper, and use the locale provided by it.
-        Was taking the locale directly from the request instead of using the standard method in Forrest: LocaleAction.
-       Thanks to Sjur Moshagen.</description></item>
-      <item><title>docs add</title><link>changes.html</link><description>docs add
-        by
-        TS
-        :
-        
-        Adding the "how tos" from the site-author to this plugin.
-      </description></item>
-      
-      <item><title>code add</title><link>changes.html</link><description>code add
-        by
-        TS
-        :
-         Extending the dispatcher 
-          with an internal format. This internal format is our xdoc or 
-          xhtml2. The internal format will then be contacted by e.g. html 
-          contracts. </description></item>
-      
-      <item><title>admin add</title><link>changes.html</link><description>admin add
-        by
-        TS
-        :
-        
-        Initial plugin code extracted from the old views plugin.
-</description></item>
-      <item><title>code add</title><link>changes.html</link><description>code add
-        by
-        TS
-        :
-         Added first implementation of 
-        the dispatcher. Including contract bean implementation and interface; 
-        dispatcher exception and dispatcher transformers. </description></item>
-      <item><title>docs add</title><link>changes.html</link><description>docs add
-        by
-        GM
-        :
-        
-        Added a dispatcher glossary. Thanks to Thorsten for moving to the plugin.
-      </description></item>
-
-      <item><title>docs add</title><link>changes.html</link><description>docs add
-        by
-        TS
-        :
-        
-        Added infos of the pattern the plugin is using.
-      </description></item>
-      <item><title>docs add</title><link>changes.html</link><description>docs add
-        by
-        TS
-        :
-        
-        Updated the "how it works" section and moved it to its own site.
-      </description></item>
-      <item><title>code add</title><link>changes.html</link><description>code add
-        by
-        TS
-        :
-        
-        Adding the dispatcher concept documentation from the site-author.
-      </description></item>
-      <item><title>docs update
-          (bug FOR-768)
-        </title><link>changes.html</link><description>docs update
-        by
-        TS
-          (fixes bug FOR-768)
-        
-        :
-        
-       Added section "linking to external css files" to howto-structurer-dsl doc.
-       Thanks to Paul Bolger.</description></item>
-      <item><title>code add</title><link>changes.html</link><description>code add
-        by
-        TS
-        :
-        
-        Activated multiple output formats to be configured via a View.
-      </description></item>
-      <item><title>code add</title><link>changes.html</link><description>code add
-        by
-        TS
-        :
-        
-        Added contracts and nuggets to the "view" plugins.
-      </description></item>
-
-    
-  
-
-  
-
-<item><title>code add</title><link>changes.html</link><description>code add
-        by
-        RDG
-        :
-        
-        Add ability to get a list of contracts provided by a plugin. For
-        this to work the plugin name must have "plugin" within it, e.g.
-        "org.apache.forrest.plugin.input.doap". Requesting
-        ls.contracts.org.apache.forrest.plugin.input.doap.source.xml
-        will return a source listing of plugins provided by the named plugin.
-        Requesting ls.contracts.org.apache.forrest.plugin.input.doap.[FORMAT] 
-        will return a formatted output document listing all templates supplied
-        by the identified plugin.        
-      </description></item><item><title>code update
-          (bug FOR-935)
-        </title><link>changes.html</link><description>code update
-        by
-        DC
-          (fixes bug FOR-935)
-        
-        :
-        
-        i18n: Add LocaleAction action wrapper, and use the locale provided by it.
-        Was taking the locale directly from the request instead of using the standard method in Forrest: LocaleAction.
-       Thanks to Sjur Moshagen.</description></item><item><title>docs add</title><link>changes.html</link><description>docs add
-        by
-        TS
-        :
-        
-        Adding the "how tos" from the site-author to this plugin.
-      </description></item><item><title>code add</title><link>changes.html</link><description>code add
-        by
-        TS
-        :
-         Extending the dispatcher 
-          with an internal format. This internal format is our xdoc or 
-          xhtml2. The internal format will then be contacted by e.g. html 
-          contracts. </description></item><item><title>admin add</title><link>changes.html</link><description>admin add
-        by
-        TS
-        :
-        
-        Initial plugin code extracted from the old views plugin.
-</description></item><item><title>code add</title><link>changes.html</link><description>code add
-        by
-        TS
-        :
-         Added first implementation of 
-        the dispatcher. Including contract bean implementation and interface; 
-        dispatcher exception and dispatcher transformers. </description></item><item><title>docs add</title><link>changes.html</link><description>docs add
-        by
-        GM
-        :
-        
-        Added a dispatcher glossary. Thanks to Thorsten for moving to the plugin.
-      </description></item><item><title>docs add</title><link>changes.html</link><description>docs add
-        by
-        TS
-        :
-        
-        Added infos of the pattern the plugin is using.
-      </description></item><item><title>docs add</title><link>changes.html</link><description>docs add
-        by
-        TS
-        :
-        
-        Updated the "how it works" section and moved it to its own site.
-      </description></item><item><title>code add</title><link>changes.html</link><description>code add
-        by
-        TS
-        :
-        
-        Adding the dispatcher concept documentation from the site-author.
-      </description></item><item><title>docs update
-          (bug FOR-768)
-        </title><link>changes.html</link><description>docs update
-        by
-        TS
-          (fixes bug FOR-768)
-        
-        :
-        
-       Added section "linking to external css files" to howto-structurer-dsl doc.
-       Thanks to Paul Bolger.</description></item><item><title>code add</title><link>changes.html</link><description>code add
-        by
-        TS
-        :
-        
-        Activated multiple output formats to be configured via a View.
-      </description></item><item><title>code add</title><link>changes.html</link><description>code add
-        by
-        TS
-        :
-        
-        Added contracts and nuggets to the "view" plugins.
+<?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE rss PUBLIC "-//Netscape Communications//DTD RSS 0.91//EN" "http://my.netscape.com/publish/formats/rss-0.91.dtd">
+<rss version="0.91"><channel><title> (0.1) Changes</title><link>changes.html</link><description>
+              (
+              0.1
+              ) Changes
+            </description><language>en-us</language>
+  
+    
+    
+    
+    
+    
+  
+
+  
+    
+    
+    
+    
+    
+  
+  
+
+    
+      <item><title>code fix
+          (bug FOR-975)
+        </title><link>changes.html</link><description>code fix
+        by
+        TS
+          (fixes bug FOR-975)
+        
+        :
+        
+        FOR-975 Renaming tiles to panel.
+      </description></item>
+      <item><title>code add
+          (bug FOR-937)
+        </title><link>changes.html</link><description>code add
+        by
+        TS
+          (fixes bug FOR-937)
+        
+        :
+        
+        More i18n work by Sjur on Dispatcher. This patch correctly localizes menus &amp; tabs.
+       Thanks to Sjur Moshagen.</description></item>
+      <item><title>code fix
+          (bug FOR-939)
+        </title><link>changes.html</link><description>code fix
+        by
+        DC
+          (fixes bug FOR-939)
+        
+        :
+        
+        Rename to ContractsMessages_en.xml, part of i18n changes by Sjur.
+       Thanks to Sjur Moshagen.</description></item>
+      <item><title>code add</title><link>changes.html</link><description>code add
+        by
+        RDG
+        :
+        
+        Add ability to get a list of contracts provided by a plugin. For
+        this to work the plugin name must have "plugin" within it, e.g.
+        "org.apache.forrest.plugin.input.doap". Requesting
+        ls.contracts.org.apache.forrest.plugin.input.doap.source.xml
+        will return a source listing of plugins provided by the named plugin.
+        Requesting ls.contracts.org.apache.forrest.plugin.input.doap.[FORMAT] 
+        will return a formatted output document listing all templates supplied
+        by the identified plugin.        
+      </description></item>
+      <item><title>code update
+          (bug FOR-935)
+        </title><link>changes.html</link><description>code update
+        by
+        DC
+          (fixes bug FOR-935)
+        
+        :
+        
+        i18n: Add LocaleAction action wrapper, and use the locale provided by it.
+        Was taking the locale directly from the request instead of using the standard method in Forrest: LocaleAction.
+       Thanks to Sjur Moshagen.</description></item>
+      <item><title>docs add</title><link>changes.html</link><description>docs add
+        by
+        TS
+        :
+        
+        Adding the "how tos" from the site-author to this plugin.
+      </description></item>
+
+      <item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+         Extending the dispatcher 
+          with an internal format. This internal format is our xdoc or 
+          xhtml2. The internal format will then be contacted by e.g. html 
+          contracts. </description></item>
+
+      <item><title>admin add</title><link>changes.html</link><description>admin add
+        by
+        TS
+        :
+        
+        Initial plugin code extracted from the old views plugin.
+</description></item>
+      <item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+         Added first implementation of 
+        the dispatcher. Including contract bean implementation and interface; 
+        dispatcher exception and dispatcher transformers. </description></item>
+      <item><title>docs add</title><link>changes.html</link><description>docs add
+        by
+        GM
+        :
+        
+        Added a dispatcher glossary. Thanks to Thorsten for moving to the plugin.
+      </description></item>
+      <item><title>docs add</title><link>changes.html</link><description>docs add
+        by
+        TS
+        :
+        
+        Added infos of the pattern the plugin is using.
+      </description></item>
+      <item><title>docs add</title><link>changes.html</link><description>docs add
+        by
+        TS
+        :
+        
+        Updated the "how it works" section and moved it to its own site.
+      </description></item>
+      <item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+        
+        Adding the dispatcher concept documentation from the site-author.
+      </description></item>
+      <item><title>docs update
+          (bug FOR-768)
+        </title><link>changes.html</link><description>docs update
+        by
+        TS
+          (fixes bug FOR-768)
+        
+        :
+        
+       Added section "linking to external css files" to howto-structurer-dsl doc.
+       Thanks to Paul Bolger.</description></item>
+      <item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+        
+        Activated multiple output formats to be configured via a View.
+      </description></item>
+      <item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+        
+        Added contracts and nuggets to the "view" plugins.
+      </description></item>
+    
+  
+  
+<item><title>code fix
+          (bug FOR-975)
+        </title><link>changes.html</link><description>code fix
+        by
+        TS
+          (fixes bug FOR-975)
+        
+        :
+        
+        FOR-975 Renaming tiles to panel.
+      </description></item><item><title>code add
+          (bug FOR-937)
+        </title><link>changes.html</link><description>code add
+        by
+        TS
+          (fixes bug FOR-937)
+        
+        :
+        
+        More i18n work by Sjur on Dispatcher. This patch correctly localizes menus &amp; tabs.
+       Thanks to Sjur Moshagen.</description></item><item><title>code fix
+          (bug FOR-939)
+        </title><link>changes.html</link><description>code fix
+        by
+        DC
+          (fixes bug FOR-939)
+        
+        :
+        
+        Rename to ContractsMessages_en.xml, part of i18n changes by Sjur.
+       Thanks to Sjur Moshagen.</description></item><item><title>code add</title><link>changes.html</link><description>code add
+        by
+        RDG
+        :
+        
+        Add ability to get a list of contracts provided by a plugin. For
+        this to work the plugin name must have "plugin" within it, e.g.
+        "org.apache.forrest.plugin.input.doap". Requesting
+        ls.contracts.org.apache.forrest.plugin.input.doap.source.xml
+        will return a source listing of plugins provided by the named plugin.
+        Requesting ls.contracts.org.apache.forrest.plugin.input.doap.[FORMAT] 
+        will return a formatted output document listing all templates supplied
+        by the identified plugin.        
+      </description></item><item><title>code update
+          (bug FOR-935)
+        </title><link>changes.html</link><description>code update
+        by
+        DC
+          (fixes bug FOR-935)
+        
+        :
+        
+        i18n: Add LocaleAction action wrapper, and use the locale provided by it.
+        Was taking the locale directly from the request instead of using the standard method in Forrest: LocaleAction.
+       Thanks to Sjur Moshagen.</description></item><item><title>docs add</title><link>changes.html</link><description>docs add
+        by
+        TS
+        :
+        
+        Adding the "how tos" from the site-author to this plugin.
+      </description></item><item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+         Extending the dispatcher 
+          with an internal format. This internal format is our xdoc or 
+          xhtml2. The internal format will then be contacted by e.g. html 
+          contracts. </description></item><item><title>admin add</title><link>changes.html</link><description>admin add
+        by
+        TS
+        :
+        
+        Initial plugin code extracted from the old views plugin.
+</description></item><item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+         Added first implementation of 
+        the dispatcher. Including contract bean implementation and interface; 
+        dispatcher exception and dispatcher transformers. </description></item><item><title>docs add</title><link>changes.html</link><description>docs add
+        by
+        GM
+        :
+        
+        Added a dispatcher glossary. Thanks to Thorsten for moving to the plugin.
+      </description></item><item><title>docs add</title><link>changes.html</link><description>docs add
+        by
+        TS
+        :
+        
+        Added infos of the pattern the plugin is using.
+      </description></item><item><title>docs add</title><link>changes.html</link><description>docs add
+        by
+        TS
+        :
+        
+        Updated the "how it works" section and moved it to its own site.
+      </description></item><item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+        
+        Adding the dispatcher concept documentation from the site-author.
+      </description></item><item><title>docs update
+          (bug FOR-768)
+        </title><link>changes.html</link><description>docs update
+        by
+        TS
+          (fixes bug FOR-768)
+        
+        :
+        
+       Added section "linking to external css files" to howto-structurer-dsl doc.
+       Thanks to Paul Bolger.</description></item><item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+        
+        Activated multiple output formats to be configured via a View.
+      </description></item><item><title>code add</title><link>changes.html</link><description>code add
+        by
+        TS
+        :
+        
+        Added contracts and nuggets to the "view" plugins.
       </description></item></channel></rss>

Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/dispatcher-glossary.dispatcher.css
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/dispatcher-glossary.dispatcher.css?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/dispatcher-glossary.dispatcher.css (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/dispatcher-glossary.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/dispatcher-glossary.html
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/dispatcher-glossary.html?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/dispatcher-glossary.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/dispatcher-glossary.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="dispatcher-glossary.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 */ 
@@ -225,8 +225,10 @@
 <h2 class="underlined_10">Introduction</h2>
 <div class="section">
 <introduction>
-    <p>This is a glossary of terms and their definitions for the 
-    Dispatcher (aka views).</p>
+    <p>
+      This is a glossary of terms and their definitions for the Dispatcher (aka
+      views).
+    </p>
   </introduction>
 </div>
 <a name="a" title="A"> </a>
@@ -253,10 +255,10 @@
         <li>See 
         <a href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=112596689428172&amp;w=2#1">
         Archive Mail</a>
-</li>
+        </li>
         <li>See 
         <a href="http://issues.apache.org/jira/browse/FOR-639">Issue FOR-639</a>
-</li>
+        </li>
       </ul>
 </td>
 </tr>
@@ -276,10 +278,10 @@
 <td class="term" id="Contracts">Contracts</td>
 <td class="definitions">
 <p>
-              1. A contract is a snippet of re-usable code that gets used in a structurer file.<br />
-              2. Contracts can be used or omitted as neccessary, though a few are really compulsary in
+        1. A contract is a snippet of re-usable code that gets used in a structurer file.<br />
+        2. Contracts can be used or omitted as neccessary, though a few are really compulsary in
                       order to define a basic skeleton structure and to include some styling (CSS)<br />
-              3. Contracts mainly come in three (3) types, static, semi-static &amp; dynamic.<br />
+        3. Contracts mainly come in three (3) types, static, semi-static &amp; dynamic.<br />
                       Static Contracts are pre-defined snippets of code that need no further information.<br />
                       Semi-static Contracts can include extra configuration variables, these would over-ride otherwise
                       default variables.<br />
@@ -294,10 +296,11 @@
 <td class="term" id="Class">Class</td>
 <td class="definitions">
 <p>
-                    1. In the context of the dispatcher, a <strong>Class</strong> is used as an optional attribute to
-                            the forrest:hook. This converts to <span class="codefrag">&lt;div class="example"&gt;&lt;/div&gt;</span>.
+        1. In the context of the dispatcher, a <strong>Class</strong> is used as an optional attribute to
+                            the forrest:hook. This converts to <span class="codefrag">
+&lt;div class="example"&gt;&lt;/div&gt;</span>.
                     <br />
-            </p>
+      </p>
 <br />See Also: <a href="#Name" role="glossary">Name</a>
 </td>
 <td class="notes" />
@@ -352,10 +355,13 @@
         2. Hooks are used to help define the layout of a page. Hooks are only used to
         define the structure in our output that is required to enable a theme to apply its look and
         feel.<br />
-3. Hooks convert to layout &lt;div&gt;&lt;/div&gt; container blocks and usually only consist
+        3. Hooks convert to layout &lt;div&gt;&lt;/div&gt; container blocks and usually only consist
         of forrest:contracts<br />
-4. Hooks are applied currently in the themes.core plugin as part of a themes structurer configuration
-        file such as %themename%-html.vt.xml (e.g pelt-html.vt.xml)<br />
+        4. Hooks are applied currently in the themes.core plugin as
+part of a themes structurer configuration file such as %themename
+%-html.panel.xml (e.g pelt-html.panel.xml) or included in such configuration
+files via a panel file such as %themename%-%format%.panel.xml (e.g
+pelt-html.panel.xml)<br />
       </p>
 <br />See Also: <a href="#Contracts" role="glossary">Contracts</a>, <a href="#Structurer" role="glossary">Structurer</a>
 </td>
@@ -378,7 +384,8 @@
 <td class="definitions">
 <p>
         1. In the context of the dispatcher, a <strong>name</strong> is used as an optional attribute to 
-                the forrest:hook. This converts to <span class="codefrag">&lt;div id="example"&gt;&lt;/div&gt;</span>.<br />
+                the forrest:hook. This converts to <span class="codefrag">
+&lt;div id="example"&gt;&lt;/div&gt;</span>.<br />
       </p>
 <br />See Also: <a href="#Class" role="glossary">Class</a>
 </td>
@@ -400,18 +407,18 @@
 <td class="term" id="Property">Property</td>
 <td class="definitions">
 <p>
-                          1. forrest:property - Todo:open<br />
-                  </p>
+        1. forrest:property - Todo:open<br />
+      </p>
 </td>
 <td class="notes" />
 </tr>
 <tr>
-<a name="Panel" />
-<td class="term" id="Panel">Panel</td>
+<a name="Panels" />
+<td class="term" id="Panels">Panels</td>
 <td class="definitions">
 <p>
-                          1. Panel is the new name for a tile - a collection of contracts. Not yet implemented.<br />
-                                  </p>
+        1. Panels is the new name for a tile - a collection of contracts. <br />
+      </p>
 <br />See Also: <a href="#Tiles" role="glossary">Tiles</a>
 </td>
 <td class="notes" />
@@ -432,9 +439,9 @@
 <td class="term" id="Structurer">Structurer</td>
 <td class="definitions">
 <p>
-              1. The Structurer allows a user to define the layout and content of a site or parts of a site.<br />
-              2. Structurer files contain hooks &amp; contracts which you can include to build up a site structure template<br />
-              3. A completed structurer file defines an overall theme (look and feel) for a site<br />
+        1. The Structurer allows a user to define the layout and content of a site or parts of a site.<br />
+        2. Structurer files contain hooks &amp; contracts which you can include to build up a site structure template<br />
+        3. A completed structurer file defines an overall theme (look and feel) for a site<br />
       </p>
 <br />See Also: <a href="#Contracts" role="glossary">Contracts</a>, <a href="#Hooks" role="glossary">Hooks</a>, <a href="#Property" role="glossary">Property</a>, <a href="#Themes" role="glossary">Themes</a>
 </td>
@@ -448,7 +455,7 @@
         1. Skins is the name of the older alternative way for structuring and styling your site pages.<br />
         2. Skins is still used in Forrest versions 0.7 and 0.8-dev, though for 0.8-dev and beyond it can be
                 concidered an option with Dispatcher being the other.(It is enabled as the default option currently)<br />
-</p>
+      </p>
 <br />See Also: <a href="#Themes" role="glossary">Themes</a>, <a href="#Dispatcher" role="glossary">Dispatcher</a>
 </td>
 <td class="notes" />
@@ -469,11 +476,11 @@
 <td class="term" id="Tiles">Tiles</td>
 <td class="definitions">
 <p>
-                          1. A tile is a collection of contracts that are grouped together for easy inclusion into a theme.<br />
-                          2. Tiles is the current but soon to be deprecated name for a collection of contracts, it is soon to be
-                                  re-named and re-implemented as a 'Panel'<br />
-                  </p>
-<br />See Also: <a href="#Panel" role="glossary">Panel</a>
+        1. A tile is a collection of contracts that are grouped together for easy inclusion into a theme.<br />
+        2. Tiles was the original but deprecated name for a collection of contracts, it is now
+                                  re-named and re-implemented as a 'Panels'<br />
+      </p>
+<br />See Also: <a href="#Panels" role="glossary">Panels</a>
 </td>
 <td class="notes" />
 </tr>
@@ -482,8 +489,8 @@
 <td class="term" id="Themes">Themes</td>
 <td class="definitions">
 <p>
-              1. A more extensible and adaptable solution than its alternative 'Skins'. A 'Theme' is an overall content &amp; style set.<br />
-              2. A master 'common' theme provides the basis in which you can extend, over-ride or add to in order to make your own theme, you do not
+        1. A more extensible and adaptable solution than its alternative 'Skins'. A 'Theme' is an overall content &amp; style set.<br />
+        2. A master 'common' theme provides the basis in which you can extend, over-ride or add to in order to make your own theme, you do not
                       have to create a complete theme from scratch, simply include/exclude/over-ride/add what you need. The current 'Pelt Theme' based on its
                       'Pelt Skin' counterpart, but uses functionality and extends/inherits what it needs to from the 'common' theme.<br />
       </p>
@@ -506,10 +513,10 @@
 <td class="term" id="Views">Views</td>
 <td class="definitions">
 <p>
-                          1. Views is the older now deprecated name for what is now the 'Dispatcher'<br />
-                          2. Views also, confusingly, was used as a term for the Structurer, and forrest:views is a 
+        1. Views is the older now deprecated name for what is now the 'Dispatcher'<br />
+        2. Views also, confusingly, was used as a term for the Structurer, and forrest:views is a 
                                   deprecated code that has been replaced with forrest:template.<br />
-                  </p>
+      </p>
 <br />See Also: <a href="#Dispatcher" role="glossary">Dispatcher</a>
 </td>
 <td class="notes" />

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

Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-contracts.html
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-contracts.html?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-contracts.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-contracts.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-contracts.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 */ 
@@ -156,8 +156,9 @@
 <h1 class="content-title">How to write a forrest:contract</h1>
 <!--+ |end content-title +-->
 <!--+ |start content-abstract +-->
-    This How-To will explain how we wrote the contracts for the dispatcher and hope afterwards you will be able to do the same.
-  <!--+ |end content-abstract +--><!--+ |start content-minitoc +--><div id="content-minitoc-area">
+      This How-To will explain how we wrote the contracts for the dispatcher and
+      hope afterwards you will be able to do the same.
+    <!--+ |end content-abstract +--><!--+ |start content-minitoc +--><div id="content-minitoc-area">
 <ul class="minitoc">
 <li>
 <a href="#Intended Audience">Intended Audience</a>
@@ -204,23 +205,25 @@
 <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>
+      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>
-      Devs and skin developer that wants to get started with forrest:contract development. 
-      To really understand this how-to you need basic and sometimes advanced understanding of 
-      the "old fashion" skin development process.
+      Devs and skin developer that wants to get started with forrest:contract
+      development. To really understand this how-to you need basic and sometimes
+      advanced understanding of the "old fashion" skin development process.
     </p>
 </div>
 <a name="Purpose" title="Purpose"> </a>
 <h2 class="underlined_10">Purpose</h2>
 <div class="section">
 <p>
-      This setup guide will explain how to create a forrest:contract from scratch and 
-      how this forrest:contract work with the core parts of forrest.
+      This setup guide will explain how to create a forrest:contract from
+      scratch and how this forrest:contract work with the core parts of forrest.
     </p>
 </div>
 <a name="Prerequisites" title="Prerequisites"> </a>
@@ -235,20 +238,27 @@
 <div class="section">
 <div class="note">
 <div class="label">Note</div>
-<div class="content">The following content is from many mails around the topic, this how-to tries to be the 
-      consolidation of this thread. It is mainly based on the thread "[RT] Why using views" - 
-      in comparison with "old fashion" skins - usecase i18n</div>
+<div class="content">
+      The following content is from many mails around the topic, this how-to
+      tries to be the consolidation of this thread. It is mainly based on the
+      thread "[RT] Why using views" - in comparison with "old fashion" skins -
+      usecase i18n
+    </div>
 </div>
 <p>
-      By working on the i18n integration for "pelt" we again encountered the reasons for using the dispatcher. ;-)
-      The maintenance 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. 
+      By working on the i18n integration for "pelt" we again encountered the
+      reasons for using the dispatcher. ;-) The maintenance 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.
     </p>
 <p>
-      For example the "last-publish"-contract could be found 2 times in the code.  
-      This is not the only contract that was (is) doubled in the code. The problem with that is that 
-      we needed to search the code for each caption and senselessly repeat the following 
-      maintenance step of adding the &lt;i18n:text/&gt;-tags.
+      For example the "last-publish"-contract could be found 2 times in the
+      code. This is not the only contract that was (is) doubled in the code. The
+      problem with that is that we needed to search the code for each caption
+      and senselessly repeat the following maintenance step of adding the
+&lt;i18n:text/&gt;
+      -tags.
     </p>
 <pre class="code">
 
@@ -262,16 +272,18 @@
 <a name="enhanceMaintenance" title="Enhance the maintenance"> </a>
 <h3 class="underlined_5">Enhance the maintenance</h3>
 <div class="section">
-<p>Now we can enhance the maintenance for the future and we give these code snippets 
-        contracts names (based on their functionality). This naming enables us to keep
-the contract separate from the position code itself. In xsl you would
-simply do:
+<p>
+        Now we can enhance the maintenance for the future and we give these code
+        snippets contracts names (based on their functionality). This naming
+        enables us to keep the contract separate from the position code itself.
+        In xsl you would simply do:
       </p>
 <ol>
         <li>replace the script by &lt;xsl:call-template name="siteinfo-last-published"/&gt;</li>
         <li>and add:</li>
       </ol>
-<pre class="code">&lt;xsl:template name="siteinfo-last-published"&gt;
+<pre class="code">
+&lt;xsl:template name="siteinfo-last-published"&gt;
  &lt;script type="text/javascript"&gt;
   document.write("&lt;i18n:text &gt;Last Published:&lt;/i18n:text&gt;&amp;#160;" + document.lastModified);
  &lt;/script&gt;
@@ -279,13 +291,14 @@
       </pre>
 <p>
         This allows us in a next maintenance to just change the code of
-        &lt;xsl:template name="siteinfo-last-published"/&gt; and apply it in any position where
-        it is placed.  
+&lt;xsl:template name="siteinfo-last-published"/&gt;
+        and apply it in any position where it is placed.
       </p>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-        Now this refactoring of the site2xhtml.xsl is exactly what we doing in creating contracts for the dispatcher.
+        Now this refactoring of the site2xhtml.xsl is exactly what we doing in
+        creating contracts for the dispatcher.
       </div>
 </div>
 </div>
@@ -294,11 +307,11 @@
 <div class="section">
 <p>
         To start a new forrest:contract you can copy the 'blank.ft' from
-        <span class="codefrag">org.apache.forrest.plugin.themes.core/themes/common/html/blank.ft</span>. 
+        <span class="codefrag">org.apache.forrest.plugin.themes.core/themes/common/html/blank.ft</span>.
       </p>
 <p>
-        The 'blank.ft' is a simple xml file with the following code which you can use to base new contracts 
-        on:
+        The 'blank.ft' is a simple xml file with the following code which you
+        can use to base new contracts on:
       </p>
 <pre class="code">
 &lt;forrest:contract 
@@ -330,50 +343,67 @@
 &lt;/forrest:contract&gt;
       </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>
-<div class="content">This is a <strong>naming convention</strong> that you need
-        to always meet. All @name attributes must be the file name of the contract without file extension.
+<div class="content">
+        This is a <strong>naming convention</strong> that you need to always
+        meet. All @name attributes must be the file name of the contract without
+        file extension.
       </div>
 </div>
 <p>
-        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 web designer to pick the right contract.
+        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 web designer to pick the right contract.
       </p>
-<pre class="code">&lt;description&gt;
+<pre class="code">
+&lt;description&gt;
   siteinfo-last-published-howto will output the last published date of the site with the help of jscript.
 &lt;/description&gt;
       </pre>
 <p>
-        In the <span class="codefrag">&lt;usage/&gt;</span> tag we have to explain how the designer can use 
-        the contract in his structurer.
+        In the <span class="codefrag">
+&lt;usage/&gt;
+        </span> tag we have to explain how the designer can use the contract in
+        his structurer.
       </p>
-<pre class="code">&lt;usage&gt;&lt;![CDATA[&lt;forrest:contract name="siteinfo-last-published-howto"/&gt;]]&gt;&lt;/usage&gt;
+<pre class="code">
+&lt;usage&gt;&lt;![CDATA[&lt;forrest:contract name="siteinfo-last-published-howto"/&gt;]]&gt;&lt;/usage&gt;
       </pre>
 <p>
-              To put contract code into the <span class="codefrag">&lt;head&gt;&lt;/head&gt;</span> section, this needs to be declared in the contract as :-
-        <span class="codefrag">&lt;forrest:part xpath="/html/head"&gt;...&lt;/forrest:part&gt;</span>
-        Simply by leaving out the xpath declaration and the code will go into body. You can use 
-        <span class="codefrag">&lt;forrest:part xpath="/html/head"&gt;...&lt;/forrest:part&gt;&lt;forrest:part&gt;...&lt;/forrest:part&gt;</span>
-        if you need content in both head and body.
+        To put contract code into the <span class="codefrag">
+&lt;head&gt;&lt;/head&gt;
+        </span> section, this needs to be declared in the contract as :- <span class="codefrag">
+&lt;forrest:part xpath="/html/head"&gt;...&lt;/forrest:part&gt;
+        </span> Simply by leaving out the xpath declaration and the code will go
+        into body. You can use <span class="codefrag">
+&lt;forrest:part xpath="/html/head"&gt;...&lt;/forrest:part&gt;&lt;forrest:part&gt;...&lt;/forrest:part&gt;
+        </span> if you need content in both head and body.
       </p>
 <div class="warning">
 <div class="label">Warning</div>
 <div class="content">
-              The last paragraph about &lt;forrest:part/&gt; has replaced the older way of
-              &lt;forrest:template name="blank" body="false" head="false"&gt;.
-        Please be aware that this part of the dispatcher is still a moving target and may change still.
+        The last paragraph about
+&lt;forrest:part/&gt;
+        has replaced the older way of
+&lt;forrest:template name="blank" body="false" head="false"&gt;
+        . Please be aware that this part of the dispatcher is still a moving
+        target and may change still.
       </div>
 </div>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-        It is possible to use contracts in different input/output formats. 
-        We are focusing for now on format="html" as output and the inputFormat="xsl".
+        It is possible to use contracts in different input/output formats. We
+        are focusing for now on format="html" as output and the
+        inputFormat="xsl".
       </div>
 </div>
 </div>
@@ -383,13 +413,14 @@
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-        We use basic naming convention for contracts. Like
-        "naming does not say anything about layout position, but functionality of the contract".
+        We use basic naming convention for contracts. Like "naming does not say
+        anything about layout position, but functionality of the contract".
       </div>
 </div>
-<p> 
-        Now let us 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/themes/common/html/siteinfo-last-published-howto.ft</span>.
+<p>
+        Now let us 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/themes/common/html/siteinfo-last-published-howto.ft</span>.
       </p>
 <p>
         Now the maintenance-optimized code (xpath="/html/body/*") was:
@@ -399,9 +430,11 @@
  &lt;script type="text/javascript"&gt;
   document.write("&lt;i18n:text &gt;Last Published:&lt;/i18n:text&gt;&amp;#160;" + document.lastModified);
  &lt;/script&gt;
-&lt;/xsl:template&gt;</pre>
+&lt;/xsl:template&gt;
+      </pre>
 <p>
-        In this code we have to do the following steps to use it in our contract:
+        In this code we have to do the following steps to use it in our
+        contract:
       </p>
 <ul>
         <li>Search and replace "siteinfo-last-published" with "siteinfo-last-publish-howto-body"</li>
@@ -416,8 +449,11 @@
  &lt;script type="text/javascript"&gt;
   document.write("&lt;i18n:text &gt;Last Published:&lt;/i18n:text&gt;&amp;#160;" + document.lastModified);
  &lt;/script&gt;
-&lt;/xsl:template&gt;</pre>
-<p>Now we have to do some last steps in the siteinfo-last-publish-howto.ft</p>
+&lt;/xsl:template&gt;
+      </pre>
+<p>
+        Now we have to do some last steps in the siteinfo-last-publish-howto.ft
+      </p>
 <ul>
         <li>Search and replace "blank" with "siteinfo-last-publish-howto"</li>
         <li>Add description and usage of the contract</li>
@@ -426,7 +462,8 @@
 <p>
         As the result your code should look like this:
       </p>
-<pre class="code">&lt;forrest:contract xmlns:forrest="http://apache.org/forrest/templates/1.0"
+<pre class="code">
+&lt;forrest:contract xmlns:forrest="http://apache.org/forrest/templates/1.0"
   name="siteinfo-last-published-howto"&gt;
   &lt;description&gt;
     siteinfo-last-published-howto will output the last published date of the site with the help of jscript.
@@ -456,34 +493,42 @@
 <h3 class="underlined_5">Activating the contract</h3>
 <div class="section">
 <p>
-        To see whether the new contract works we need to add it to our structurer.
-        The contract usage contains the contract-tag <span class="codefrag">&lt;forrest:contract name="siteinfo-last-published-howto"/&gt;</span>
-        Please see <a href="../how/howto-dispatcher-structurer.html">Getting started with the "structurer"</a> for more details.
+        To see whether the new contract works we need to add it to our
+        structurer. The contract usage contains the contract-tag <span class="codefrag">
+&lt;forrest:contract name="siteinfo-last-published-howto"/&gt;
+        </span> Please see <a href="../how/howto-dispatcher-structurer.html">Getting started
+        with the "structurer"</a> for more details.
       </p>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-        Next to write are parameter-contracts with advanced features of the dispatcher. 
+        Next to write are parameter-contracts with advanced features of the
+        dispatcher.
       </div>
 </div>
 </div>
 <a name="pluginContracts" title="Plugin Supplied Contracts"> </a>
 <h3 class="underlined_5">Plugin Supplied Contracts</h3>
 <div class="section">
-<p>It is possible for plugins to provide contracts for use in the dispatcher.
-      For details on how this is done see the <a href="http://forrest.apache.org/docs/howto/howto-buildPlugin.html#Dispatcher">Plugin HowTo</a>.</p>
+<p>
+        It is possible for plugins to provide contracts for use in the
+        dispatcher. For details on how this is done see the
+        <a href="http://forrest.apache.org/docs/howto/howto-buildPlugin.html#Dispatcher">Plugin
+        HowTo</a>.
+      </p>
 </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 structurer contracts. 
-      From here we recommend to read the following How-To's (if not already done):
+      Congratulations you are now able to work with structurer contracts. From
+      here we recommend to read the following How-To's (if not already done):
     </p>
 <ul>
       <li>
-<a href="../how/howto-dispatcher-structurer.html">Getting started with the "structurer"</a> </li>
+<a href="../how/howto-dispatcher-structurer.html">Getting started with the "structurer"</a>
+</li>
     </ul>
 </div>
 <a name="Feedback" title="Feedback"> </a>

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

Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-quickstart.html
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-quickstart.html?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-quickstart.html (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-quickstart.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-quickstart.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 */ 
@@ -211,15 +211,18 @@
 <a name="Intended Audience" title="Intended Audience"> </a>
 <h2 class="underlined_10">Intended Audience</h2>
 <div class="section">
-<p>People who are helping to develop the Dispatcher.</p>
+<p>
+      People who are helping to develop the Dispatcher.
+    </p>
 <div class="warning">
 <div class="label">Warning</div>
-<div class="content"> The "Dispatcher" (previously known as "Views") is new functionality which is 
-      still in development phase. That is why it is in the "whiteboard" section 
-      of Forrest. This document will also need to change to keep pace.
-      We are working at the moment on moving this plugin
-      from the whiteboard into the core plugins.
-      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" (previously known as "Views") is new functionality which
+      is still in development phase. That is why it is in the "whiteboard"
+      section of Forrest. This document will also need to change to keep pace.
+      We are working at the moment on moving this plugin from the whiteboard
+      into the core plugins. See <a href="http://forrest.apache.org/docs_0_80/status-themes.html">Status of
+      Themes: Skins and Dispatcher</a>.
     </div>
 </div>
 </div>
@@ -227,22 +230,21 @@
 <h2 class="underlined_10">Purpose</h2>
 <div class="section">
 <p>
-      This document will get you started. We will Dispatcher-enable an
-      existing site and show how to add/remove ready-made contacts.
-      Then we will discuss how add your own new contracts.
+      This document will get you started. We will Dispatcher-enable an existing
+      site and show how to add/remove ready-made contacts. Then we will discuss
+      how add your own new contracts.
     </p>
 <p>
-      This document encourages developers to get involved with
-      fine-tuning and testing the dispatcher. Please help to
-      enhance the current core contracts so that people do not
-      need to re-invent the wheel.
+      This document encourages developers to get involved with fine-tuning and
+      testing the dispatcher. Please help to enhance the current core contracts
+      so that people do not need to re-invent the wheel.
     </p>
 </div>
 <a name="Prerequisites" title="Prerequisites"> </a>
 <h2 class="underlined_10">Prerequisites</h2>
 <div class="section">
 <ul>
-      <li>Using Forrest trunk of SVN (i.e. forrest-0.8-dev).
+      <li>Using Forrest trunk of SVN (i.e. head of development).
       </li>
       <li>Followed the installation instructions below.</li>
       <li>You have an existing forrest site and want to try the
@@ -254,11 +256,13 @@
 <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 
-      <a href="http://forrest.apache.org/tools/forrestbar.html">Forrestbar</a> helps a lot with developing,
-      but is not necessary.
+<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
+      <a href="http://forrest.apache.org/tools/forrestbar.html">Forrestbar</a> helps a lot with developing, but
+      is not necessary.
     </div>
 </div>
 <a name="patch" title="Get ready"> </a>
@@ -266,7 +270,7 @@
 <div class="section">
 <ul>
         <li>Do 'svn update' on forrest/trunk</li>
-        <li>Do the 'build clean; build' (necessary because the Dispatcher is changing rapidly and uses some Java)</li>
+        <li>Do the 'cd main; build clean; build' (necessary because the Dispatcher is changing rapidly and uses some Java)</li>
       </ul>
 </div>
 <a name="enable" title="Dispatcher-enable the existing site"> </a>
@@ -299,29 +303,31 @@
 <div class="label">Note</div>
 <div class="content">
         At this stage of rapid development of the Dispatcher, be sure to keep
-        your copy synchronised. Use 'diff' against the known svn version of
-        the core pelt.fv to track your local changes.
-        Also please consider contributing new contracts and changes to the
-        default structurers to the Forrest projects. That eases your local
-        version management and everyone will benefit.
+        your copy synchronised. Use 'diff' against the known svn version of the
+        core pelt.fv to track your local changes. Also please consider
+        contributing new contracts and changes to the default structurers to the
+        Forrest projects. That eases your local version management and everyone
+        will benefit.
       </div>
 </div>
 <div class="note">
 <div class="label">Note</div>
 <div class="content">
-        We use <span class="codefrag">${themer.project.dir}</span> for PROJECT_HOME/src/documentation/resources/themes
-        (create the new directory folder first).
-        You can change this location by adding &lt;match pattern="themer.project.dir"&gt;
+        We use <span class="codefrag">${themer.project.dir}</span> for
+        PROJECT_HOME/src/documentation/resources/themes (create the new
+        directory folder first). You can change this location by adding
+&lt;match pattern="themer.project.dir"&gt;
           &lt;location src="{properties:resources}/themes" /&gt;
-        &lt;/match&gt;  to your locationmap and point to another directory.
+        &lt;/match&gt; 
+        to your locationmap and point to another directory.
       </div>
 </div>
 <ul>
         <li>Copy THEMER_PLUGIN/themes/pelt.fv into your project at
           ${themer.project.dir}/pelt.fv
   </li>
-  <li>Copy THEMER_PLUGIN/themes/pelt/html/pelt-html.vt.xml into your
-          project at  ${themer.project.dir}/pelt/html/pelt-html.vt.xml
+        <li>Copy THEMER_PLUGIN/themes/pelt/panels/pelt-html.panel.xml into your
+          project at  ${themer.project.dir}/pelt/panels/pelt-html.panel.xml
   </li>
         <li>Re-start 'forrest run'</li>
         <li>localhost:8888/index.html ... See the same view, now structured
@@ -329,15 +335,15 @@
         </li>
       </ul>
 <p>
-        From here on there is no need to re-start 'forrest run'. Just edit
-        the structurer and see the effect.
+        From here on there is no need to re-start 'forrest run'. Just edit the
+        structurer and see the effect.
       </p>
 </div>
 <a name="remove-default-contract" title="Remove a default contract"> </a>
 <h3 class="underlined_5">Remove a default contract</h3>
 <div class="section">
 <ul>
-        <li>Remove the top breadcrumb trail. Edit your pelt-html.vt.xml and find the
+        <li>Remove the top breadcrumb trail. Edit your pelt-html.panel.xml and find the
           "branding-breadcrumbs" contract and comment it out.
         </li>
       </ul>
@@ -346,8 +352,8 @@
 <h3 class="underlined_5">Add a default contract</h3>
 <div class="section">
 <p>
-        Forrest provides many default contracts. If you are using the
-        Forrestbar then choose "Devs =&gt; ls.contracts". Otherwise visit
+        Forrest provides many default contracts. If you are using the Forrestbar
+        then choose "Devs =&gt; ls.contracts". Otherwise visit
         localhost:8888/ls.contracts.html
       </p>
 <ul>
@@ -358,20 +364,37 @@
         <li>
           Insert it at the appropriate point in your structurer. Note that it
           will need to go inside the appropriate CSS hook, e.g.
-        <pre class="code">  ...
+        <pre class="code">
+  ...
   &lt;forrest:hook name="footer"&gt;
     &lt;forrest:contract name="siteinfo-current-time"/&gt;
     ...
-</pre>
-        </li>
+
+          </pre>
+</li>
       </ul>
 <p>
-        Notice that you did not need to copy any other code to your project space.
-        Forrest finds the default contract in its core (the themes.core plugin).
-</p>
-<p>You will find some commonly used contracts in place but commented out in both the common 
-        and the pelt structurer files. Feel free to umcomment them to activate them, move them
-around into other hooks or create new hooks for them.</p>
+        Notice that you did not need to copy any other code to your project
+        space. Forrest finds the default contract in its core (the themes.core
+        plugin).
+      </p>
+<p>
+        You will find some commonly used contracts in place but commented out in
+        both the common and the pelt structurer files. Feel free to uncomment
+        them to activate them, move them around into other hooks or create new
+        hooks for them.
+      </p>
+<div class="note">
+<div class="label">Note</div>
+<div class="content">
+        Work is currently under way for implementing Panels (was tiles).
+        Currently we now have a 'panels' sub-dir for each 'theme'. This panels
+        sub-dir currently contains a main html panel
+        '%themename%-html.panel.xml' and a CSS panel
+        '%themename%-css.panel.xml'. So you can change a collection of HTML and
+        CSS outputs from these two XML files.
+      </div>
+</div>
 </div>
 <a name="add-project-contract" title="Add a new project contract"> </a>
 <h3 class="underlined_5">Add a new project contract</h3>
@@ -379,9 +402,9 @@
 <div class="warning">
 <div class="label">Warning</div>
 <div class="content">
-        Carefully consider the purpose of your contracts. If they are useful
-        in a wider context, then they belong in plugins or the core of Forrest.
-        See below for further discussion on this important topic.
+        Carefully consider the purpose of your contracts. If they are useful in
+        a wider context, then they belong in plugins or the core of Forrest. See
+        below for further discussion on this important topic.
       </div>
 </div>
 <p>
@@ -390,12 +413,13 @@
         ${themer.project.dir}/THEME_NAME/OUTPUT_FORMAT/
       </p>
 <p>
-       Project-based contracts common to all themes go in
+        Project-based contracts common to all themes go in
         ${themer.project.dir}/common/OUTPUT_FORMAT/
       </p>
 <p>
         To get started quickly (it is not a project-based contract but a demo),
-        copy one of the default contracts. e.g. copy siteinfo-current-time.ft to become siteinfo-doodad.ft ...
+        copy one of the default contracts. e.g. copy siteinfo-current-time.ft to
+        become siteinfo-doodad.ft ...
       </p>
 <ul>
         <li>
@@ -415,7 +439,7 @@
         </li>
       </ul>
 <p>
-        See a list of your project-based contracts and their usage notes via 
+        See a list of your project-based contracts and their usage notes via
         Forrestbar "Devs =&gt; ls.contracts.project". Otherwise visit
         localhost:8888/ls.contracts.project.html
       </p>
@@ -426,31 +450,37 @@
 <div class="fixme">
 <div class="label">Fixme (open)</div>
 <div class="content">
-Glean content from Ross' discussion:
-<a href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=113748831226697">Re: Dispatcher quickstart</a>.
-</div>
+        Glean content from Ross' discussion:
+        <a href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=113748831226697">Re:
+        Dispatcher quickstart</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 Dispatcher. From here 
-      we recommend to read the following How-Tos: </p>
+<p>
+      Congratulations you are now able to work with the Dispatcher. From here we
+      recommend to read the following How-Tos:
+    </p>
 <ul>
       <li>
-        <a href="../how/howto-dispatcher-structurer.html">How to use the structurer</a>
-      </li>
+<a href="../how/howto-dispatcher-structurer.html">How to use the structurer</a>
+</li>
       <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>

Modified: forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-structurer.dispatcher.css
URL: http://svn.apache.org/viewvc/forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-structurer.dispatcher.css?view=diff&rev=527684&r1=527683&r2=527684
==============================================================================
--- forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-structurer.dispatcher.css (original)
+++ forrest/site/pluginDocs/plugins_0_80/org.apache.forrest.plugin.internal.dispatcher/how/howto-dispatcher-structurer.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;
 }
             
-  
+
   



Mime
View raw message