Author: thorsten
Date: Mon Jul 31 15:45:53 2006
New Revision: 427352
URL: http://svn.apache.org/viewvc?rev=427352&view=rev
Log:
restructuring document and change some links to take the new context into
credit.
Modified:
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/documentation/content/xdocs/dispatcher.xml
Modified:
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/documentation/content/xdocs/dispatcher.xml
URL:
http://svn.apache.org/viewvc/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/documentation/content/xdocs/dispatcher.xml?rev=427352&r1=427351&r2=427352&view=diff
==============================================================================
---
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/documentation/content/xdocs/dispatcher.xml
(original)
+++
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/documentation/content/xdocs/dispatcher.xml
Mon Jul 31 15:45:53 2006
@@ -24,58 +24,23 @@
<body>
<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 moving this plugin
+ Forrest distribution. We are working at the moment on moving this plugin
from the whiteboard into the core plugins. Further all dispatcher
related
- documents will be moved into the plugin as well.
- See <a href="site:v0.80//status-themes">Status of Themes: Skins and
Dispatcher</a>.
- </warning>
+ documents will be moved into the plugin as well. See <a
+ href="http://forrest.apache.org/docs_0_80/status-themes.html";>Status of
+ Themes: Skins and Dispatcher</a>. </warning>
<section id="introduction">
<title>Introduction</title>
- <p> As stated in the <a href="site:v0.80//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 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.html";> 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.
- Leather-dev evolved from the "pelt" skin and almost used the same
- functionality (contracts). We had started to encapsulate functional
- code into templates, but there have been still in 4 xsl files and
without
- any documentation what they are doing and how to use them. The
- problems with leather-dev was pointed out in the mail "<a
-
href="http://marc.theaimsgroup.com/?l=forrest-dev&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>
+ <p> As stated in the Skin documentation 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="dispatcher">
<title>Dispatcher - advanced separation of concerns</title>
@@ -115,12 +80,44 @@
pieces of xsl templates created out of pure maintaining
reasons.</p>
</section>
</section>
+ <section id="background">
+ <title>Background</title>
+ <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.html";> 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.
+ Leather-dev evolved from the "pelt" skin and almost used the same
+ functionality (contracts). We had started to encapsulate functional
+ code into templates, but there have been still in 4 xsl files and
without
+ any documentation what they are doing and how to use them. The
+ problems with leather-dev was pointed out in the mail "<a
+
href="http://marc.theaimsgroup.com/?l=forrest-dev&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="info">
<title>Further information</title>
<p> See the various How-to documents about the dispatcher, starting with
- <a href="site:v0.80//dispatcher/install">installing the
- dispatcher</a> and
- <a href="site:v0.80//dispatcher/quickstart">quickstart</a>
+ the <a href="site:v0.80//dispatcher/quickstart">quickstart</a>
</p>
<p> Apache Forrest 1.0 Specification (Draft, not yet published):
<code>site-author/content/xdocs/TR/2005/WD-forrest10.html</code> </p>
