You are viewing a plain text version of this content. The canonical link for it is here.
Posted to svn@forrest.apache.org by cr...@apache.org on 2005/07/18 14:39:30 UTC
svn commit: r219479 - in /forrest/trunk/site-author/content/xdocs/docs_0_80:
locationmap.xml views.xml
Author: crossley
Date: Mon Jul 18 05:39:20 2005
New Revision: 219479
URL: http://svn.apache.org/viewcvs?rev=219479&view=rev
Log:
Minor text tweaks.
Modified:
forrest/trunk/site-author/content/xdocs/docs_0_80/locationmap.xml
forrest/trunk/site-author/content/xdocs/docs_0_80/views.xml
Modified: forrest/trunk/site-author/content/xdocs/docs_0_80/locationmap.xml
URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/docs_0_80/locationmap.xml?rev=219479&r1=219478&r2=219479&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_80/locationmap.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/locationmap.xml Mon Jul 18 05:39:20 2005
@@ -167,7 +167,7 @@
outputting XDoc, or by Forrest switching to using XHTML as its internal format, or through the development of a
plugin for Lenya that will include the necessary processing (whichever comes first).</note>
- <warning>This demo is an example only, it does not work fully work at this time. For example, absolute URLs
+ <warning>This demo is an example only, it does not fully work at this time. For example, absolute URLs
in the source document need to be rewritten to ensure that they are matched by the locationmap.</warning>
</section>
@@ -181,8 +181,8 @@
<location src="http://www.domain.org/{1}.xml" />
</match>
</source>
- <p>With the above match in the locationmap a link which has <code>href="lm:rewriteDemo/index"</code>
- will be rewritten to an offsite address at <code>domain.org</code>.</p>
+ <p>With the above match in the locationmap, a link which has <code>href="lm:rewriteDemo/index"</code>
+ will be rewritten to an offsite address at <code>domain.org</code></p>
</section>
</section>
Modified: 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/views.xml?rev=219479&r1=219478&r2=219479&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/docs_0_80/views.xml (original)
+++ forrest/trunk/site-author/content/xdocs/docs_0_80/views.xml Mon Jul 18 05:39:20 2005
@@ -18,21 +18,21 @@
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
<document>
<header>
- <title>forrest:views concept (Draft -feature planed for 0.8)</title>
+ <title>forrest:views concept (Draft - feature planned for 0.8)</title>
</header>
<body>
<warning>This document is heavily under development</warning>
<section id="introduction">
<title>Introduction</title>
<p>
- Like stated in the <a href="site:v0.80//documentation/skins">Skin documentation
- file</a> the aim of the forrest skins is to provide
- many capabilities so that extra skins are not needed. Our experience showed that many forrest user
- had to create a new skin because the default skin did not offer the feature their wanted to use.
- That leaded us to develop a new concept of creating skins that would be easily extensible by a user.
+ 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.
+ 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 upcoming "forrest:views" skinning concept is to provide a flexible framework for creating
+ The aim of the "forrest:views" concept is to provide a flexible framework for creating
site and page specific layout in different formats.
</p>
@@ -43,17 +43,17 @@
<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 easy extensible by a user.
- Then we decided to support the a standard regarding naming conventions for css elements.
+ 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 informations.
+ OSCOM website</a>, where you can find some more background information.
</p>
</section>
<section id="nc-definition">
<title>Definition of naming conventions</title>
<p>
- "A naming convention is an attempt to systematize names in a field so
+ "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>
@@ -61,9 +61,16 @@
<section id="leather">
<title>leather-dev</title>
<p>
- That leaded to the development of the "leather-dev" skin which established a semantic container approach for div elements.
+ 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 m=111049344517653 w=2" >status on leather-dev?</a>
+ "<a href="http://marc.theaimsgroup.com/?l=forrest-dev&m=111049344517653" >status on leather-dev?</a>".
+ </p>
+ </section>
+ <section id="info">
+ <title>Further information</title>
+ <p>
+ See the various How-to documents about views, starting with
+ <a href="site:v0.80//howto/view/install">installing views</a>.
</p>
</section>
</body>