forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From thors...@apache.org
Subject svn commit: r372473 - in /forrest/trunk/site-author: content/xdocs/docs_0_80/dispatcher.xml content/xdocs/docs_0_80/howto/howto-dispatcher-quickstart.xml content/xdocs/docs_0_80/views.xml content/xdocs/site.xml status.xml
Date Thu, 26 Jan 2006 07:43:26 GMT
Author: thorsten
Date: Wed Jan 25 23:43:16 2006
New Revision: 372473

URL: http://svn.apache.org/viewcvs?rev=372473&view=rev
Log:
Started to rewrite dispatcher related resources

Added:
    forrest/trunk/site-author/content/xdocs/docs_0_80/dispatcher.xml
      - copied, changed from r370671, forrest/trunk/site-author/content/xdocs/docs_0_80/views.xml
Removed:
    forrest/trunk/site-author/content/xdocs/docs_0_80/views.xml
Modified:
    forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-dispatcher-quickstart.xml
    forrest/trunk/site-author/content/xdocs/site.xml
    forrest/trunk/site-author/status.xml

Copied: forrest/trunk/site-author/content/xdocs/docs_0_80/dispatcher.xml (from r370671, forrest/trunk/site-author/content/xdocs/docs_0_80/views.xml)
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/docs_0_80/dispatcher.xml?p2=forrest/trunk/site-author/content/xdocs/docs_0_80/dispatcher.xml&p1=forrest/trunk/site-author/content/xdocs/docs_0_80/views.xml&r1=370671&r2=372473&rev=372473&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_80/views.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/dispatcher.xml Wed Jan 25 23:43:16 2006
@@ -18,59 +18,77 @@
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
 <document>
   <header>
-    <title>forrest:views (Draft - feature planned for 0.8)</title>
+    <title>Dispatcher (Draft - feature planned for 0.8)</title>
   </header>
   <body>
-<warning>
-"Views" are new functionality which is still in development phase. That is why it is in the
-"whiteboard" section of the Forrest distribution.
-</warning>
+<warning> 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 its release out of the 
+  whiteboard into the official core plugins </warning>
     <section id="introduction">
       <title>Introduction</title>
-      <p>
-        As stated in the <a href="site:v0.80//documentation/skins">Skin documentation

-        </a> the aim of the Forrest skins is to provide
-        many capabilities so that extra skins are not needed. Experience showed that many
Forrest users 
-        decided to create a new skin because the default skin did not offer the features
that they wanted.
-        We introduced skinconf.xml where the user could configure some features of skins
but it was up 
-        to the skin to support it. That led us to develop a new concept of creating skins
that would 
-        be more easily extensible by a user.
-      </p>
-      <p>
-        The aim of the "forrest:views" concept is to provide a flexible framework for creating
-        site and page specific layout in different formats. Further it is a filter that limits
the
-        data-model to a minimum by only requesting what the strucuter (e.g. default.fv) need.
-      </p>
-
+      <p> As stated in the <a href="site:v0.80//documentation/skins">Skin 
+        documentation </a> 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>
     </section>
 
     <section id="background">
       <title>Background</title>
-      <p>
-        The problem with the forrest skins so far has been that "only" the design changed
(html-skeleton),
-        but still we 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 also 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">
-        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"> OSCOM 
+        website</a>, where you can find some more background information.</p>
+      <section id="nc-definition">
+        <title>Definition of naming conventions</title>
+        <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>
+      </section>
+      <section id="leather">
+        <title>leather-dev</title>
+        <p> That led to the development of the "leather-dev" skin which 
+          established a semantic container approach for div elements. 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 was way too limiting regarding design. Since we 
+          had now grouped functionality in named container we were ready to 
+          start the dispatcher (aka forrest:views).</p>
+      </section>
     </section>
-
-    <section id="nc-definition">
-      <title>Definition of naming conventions</title>
-      <p>
-        "A naming convention is an attempt to systematize names in a particular field so

-        they unambiguously convey similar information in a similar manner." 
-        <a href="http://www.wordiq.com/definition/Naming_convention">wordiq-definition</a>

-      </p>
-    </section>
-    <section id="leather">
-      <title>leather-dev</title>
-      <p>
-        That led to the development of the "leather-dev" skin which established a semantic
container approach for div elements. 
-        The problems with leather-dev was pointed out on the mail 
-          "<a href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=111049344517653"
>status on leather-dev?</a>".
-      </p>
+    <section id="dispatcher">
+      <title>Dispatcher - advanced separation of concerns</title>
+       <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. </p>
+      <p>The dispatcher is a filter that limits the data-model to a minimum by 
+        only requesting what the strucuter (e.g. common.fv) need. This leads to 
+        a different URL handling focus - away from document centric. A document 
+        can be (but do not have to) 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 let 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. </p>
     </section>
     <section id="info">
       <title>Further information</title>
@@ -79,8 +97,8 @@
         <code>site-author/content/xdocs/TR/2005/WD-forrest10.html</code>
       </p>
       <p>
-        See the various How-to documents about views, starting with
-        <a href="site:v0.80//howto/dispatcher/install">installing views</a>.
+        See the various How-to documents about the dispatcher, starting with
+        <a href="site:v0.80//howto/dispatcher/install">installing the dispatcher</a>.
       </p>
     </section>
   </body>

Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-dispatcher-quickstart.xml
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-dispatcher-quickstart.xml?rev=372473&r1=372472&r2=372473&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-dispatcher-quickstart.xml
(original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/howto/howto-dispatcher-quickstart.xml
Wed Jan 25 23:43:16 2006
@@ -218,10 +218,10 @@
       we recommend to read the following How-Tos: </p>
     <ul>
       <li>
-        <a href="site:howto/dispatcher/dsl">How to use the structurer</a>
+        <a href="site:v0.80//howto/dispatcher/structurer">How to use the structurer</a>
       </li>
       <li>
-        <a href="site:howto/dispatcher/contracts">Create your own contract 
+        <a href="site:v0.80//howto/dispatcher/structurer">Create your own contract

           implementation</a>
       </li>
     </ul>

Modified: forrest/trunk/site-author/content/xdocs/site.xml
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/site.xml?rev=372473&r1=372472&r2=372473&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/site.xml (original)
+++ forrest/trunk/site-author/content/xdocs/site.xml Wed Jan 25 23:43:16 2006
@@ -224,7 +224,7 @@
         <searching label="Searching" href="searching.html"/>
         <skins label="Default Skins" href="skins.html"/>
         <skin-package label="Skin Packages" href="skin-package.html"/>
-        <views label="Views development" href="views.html"/>
+        <dispatcher-concept label="Dispatcher development" href="dispatcher.html"/>
 
         <forrest-contract label="Our Contract" href="forrest-contract.html"/>
         <compliance label="Standards Compliance" href="compliance.html"/>

Modified: forrest/trunk/site-author/status.xml
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/status.xml?rev=372473&r1=372472&r2=372473&view=diff
==============================================================================
--- forrest/trunk/site-author/status.xml (original)
+++ forrest/trunk/site-author/status.xml Wed Jan 25 23:43:16 2006
@@ -184,8 +184,8 @@
       </action>
 
       <action context="code" type="add" dev="TS">
-        The "views" development work has moved to two new plugins.
-        See <link href="site:v0.80//views">views development</link> and
+        The "dispatcher" development work has moved to two new plugins.
+        See <link href="site:v0.80//dispatcher-concept">dispatcher development</link>
and
         follow to the installation howto.
       </action>
 



Mime
View raw message