Author: thorsten
Date: Tue Feb 14 12:26:13 2006
New Revision: 377820

URL: http://svn.apache.org/viewcvs?rev=377820&view=rev
Log:
Minor updated structurer document

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

Modified: 
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-dsl.xml
URL: 
http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-dsl.xml?rev=377820&r1=377819&r2=377820&view=diff
==============================================================================
--- 
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-dsl.xml
 (original)
+++ 
forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-structurer-dsl.xml
 Tue Feb 14 12:26:13 2006
@@ -30,11 +30,11 @@
       of the Forrest distribution. This HowTo is a good start but still needs 
       more work. </warning>
     <p> This part of the the dispatcher is called the structurer and is 
-      dedicated to webdesigner and user with some knowlegde of css. </p>
+      dedicated to webdesigner and user with some knowledge of css. </p>
   </audience>
   
   <purpose title="Purpose">
-    <p> This how-to will show you how to write a <strong>forrest:view</strong> 
+    <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>
@@ -42,7 +42,7 @@
 
   <prerequisites title="Prerequisites">
     <ul>
-      <li> You have a ready-to-go new seed-v2 (v2) based on the dispatcher 
like 
+      <li> You have a ready-to-go new dispatcher based project like 
         described in <a href="site:howto/dispatcher/install">Install</a>. </li>
       <li> Reading that how-to is as well a good idea to understand the used 
         directory structure in this how-to. </li>
@@ -86,12 +86,6 @@
       (which offer configuration parameter in the structurer) and dynamic 
       contracts (which offer semi-static configuration and/or requesting the 
       content).  </p>
-    <p>Till now the processing includes firstly all raw data into the 
-      structurer, then generating a dynamic xsl and last but nor least 
-      response. That is heavy based on xsl processing which is quite slow. A 
-      better way is that we do not include *raw* but the *transformed* (by the 
-      contract) data . This way we do not have to generate a dynamic 
stylesheet 
-      which leads to the upcoming development of standalone contracts.</p>
       <note> The structurer is as well a configuration file for the 
dispatcher. 
         The new think on the dispatcher is that one can include any content 
         from any given business service by dispatching a request against it. 
In 


Reply via email to