forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r348578 - /forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml
Date Wed, 23 Nov 2005 22:00:01 GMT
Author: crossley
Date: Wed Nov 23 13:59:57 2005
New Revision: 348578

URL: http://svn.apache.org/viewcvs?rev=348578&view=rev
Log:
Dispatcher (was Forrest Views).
Other minor edits.

Modified:
    forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml?rev=348578&r1=348577&r2=348578&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-buildPlugin.xml Wed Nov
23 13:59:57 2005
@@ -412,17 +412,17 @@
         </section>
         
         <section>
-          <title>Forrest:Views</title>
+          <title>Dispatcher</title>
           
-          <p>Forrest Views is the collective name for the various peices of functionality
+          <p>Dispatcher (previous codename Forrest Views) is the collective name for
the various pieces of functionality
           that are intended to replace skins in the future. They allow for a much more
           configurable system of defining the contents and look and feel of a site.</p>
           
           <p>Plugins can expose contracts for use in structurer files used within
-          Forrest:Views based sites. In order to do this you should develop your contracts
+          Dispatcher-based sites. In order to do this you should develop your contracts
           as normal and place them in <code>PLUGIN_HOME/resources/themes</code>.
However,
-          this, by itself, is not suficient to export your contracts. You will also need
to
-          add the following match to you plugins <code>locationmap.xml</code>
file:</p>
+          this, by itself, is not sufficient to export your contracts. You will also need
to
+          add the following match to your plugin's <code>locationmap.xml</code>
file:</p>
           
           <source><![CDATA[
     <match pattern="resolvePluginContract.*.**">
@@ -435,13 +435,13 @@
           <p>Of course, you should replace <code>PLUGIN_NAME</code> with
the name of 
           your plugin.</p>
           
-          <p>Once views become stable we will add this match to the default locationmap
-          generated when you seed a new plugin, but for now it must be done manually.</p>
+          <p>Once Dispatcher becomes stable we will add this match to the default locationmap
+          which is generated when you seed a new plugin, but for now it must be done manually.</p>
         </section>
         
         <section>
           <title>Plugin Properties</title>
-          <p>Plugins can define properties that can be overwritten by projects.
+          <p>Plugins can define properties that each project can over-ride.
           For more information see the issue below.</p>
           
           <p>We have an <a href="http://issues.apache.org/jira/browse/FOR-588">issue</a>



Mime
View raw message