forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r448065 - in /forrest/trunk/site-author/content/xdocs: docs_0_80/status-themes.xml site.xml
Date Wed, 20 Sep 2006 04:51:07 GMT
Author: crossley
Date: Tue Sep 19 21:51:06 2006
New Revision: 448065

Summarised the discussion about the future of skins and dispatcher.
Issue: FOR-867


Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/status-themes.xml
--- forrest/trunk/site-author/content/xdocs/docs_0_80/status-themes.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/status-themes.xml Tue Sep 19 21:51:06
@@ -30,7 +30,7 @@
         href="site:skins">"pelt" skin</a> is the only one that the Forrest 
         project is maintaining. It is configurable enough to meet many 
         purposes. The main configuration file for skins is the skinconf.xml 
-        (themes have a similar configuration file called structurer). There is 
+        file. There is 
         an ability for users to create their own skins, although we have not 
         encouraged that.</p>
       <p>For the Forrest-0.8 release, skins are still available and are still the main
@@ -41,12 +41,23 @@
       <p>"Dispatcher" is the term used to describe a new method which aims to 
         be a more flexible and complete solution to build a reliable common 
         structure for documents, incorporate other content, and provide hooks 
-        for applying themes. Themes get configurated by structurer definitions 
+        for applying themes. Themes get configured by structurer definitions 
         (a wee bit like the skinconf.xml). Although strong progress has been 
         made, it is still under development. We encourage developers to use 
         Dispatcher and contribute to its development. See the <a 
         plugin documentation</a> for more information.</p>
+    </section>
+    <section id="framework">
+      <title>Plan for future framework</title>
+      <p>The desired direction is to use xhtml2 as the internal format, move the current
+        into a plugin, and develop input plugins for xdoc and html sources. This would enable
+        any theme engine to be used, whether that be Skins or Dispatcher or some other.
+      </p>
+      <p>See the development discussion:
+        <a href="">Re: status
of skins and dispatcher</a>.
+        This is planned for immediately following the 0.8 release. New developers please
+      </p>

Modified: forrest/trunk/site-author/content/xdocs/site.xml
--- forrest/trunk/site-author/content/xdocs/site.xml (original)
+++ forrest/trunk/site-author/content/xdocs/site.xml Tue Sep 19 21:51:06 2006
@@ -357,14 +357,14 @@
               <searching label="Search Options in Forrest" href="searching.html"/>
              <locationmap label="Locationmap" href="locationmap.html"/>
-              <skins label="Skins" href="skins.html" description="About default skins,
their naming and features"/>
               <sitemap-ref label="Sitemap Reference" href="sitemap-ref.html">
                   <linkrewriting_impl href="#linkrewriting_impl"/>
                   <menu_generation_impl href="#menu_generation_impl"/>
                   <source_pipelines href="#source_pipelines"/>
                   <forrest_xmap href="#forrest_xmap"/>
-              <status-themes label="Themes and Dispatcher vs. Skins" href="status-themes.html"/>
+              <skins label="Skins" href="skins.html" description="About default skins,
their naming and features"/>
+              <status-themes label="Dispatcher versus Skins" href="status-themes.html"/>
               <cap label="Sourcetype Action" href="cap.html"/>
               <validation label="XML Validation" href="validation.html"/>

View raw message