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 2004/10/31 09:32:28 UTC

svn commit: rev 56132 - in forrest/trunk/forrestcore: . src/documentation/content/xdocs/docs src/documentation/content/xdocs/images

Author: crossley
Date: Sun Oct 31 01:32:28 2004
New Revision: 56132

Added:
   forrest/trunk/forrestcore/src/documentation/content/xdocs/images/
   forrest/trunk/forrestcore/src/documentation/content/xdocs/images/snapshot-leather-dev.png   (contents, props changed)
   forrest/trunk/forrestcore/src/documentation/content/xdocs/images/snapshot-plain-dev.png   (contents, props changed)
Modified:
   forrest/trunk/forrestcore/src/documentation/content/xdocs/docs/skins.xml
   forrest/trunk/forrestcore/status.xml
Log:
Added links to example websites to demonstrate each available default skin
and snapshots for current leather-dev and plain-dev skins.


Modified: forrest/trunk/forrestcore/src/documentation/content/xdocs/docs/skins.xml
==============================================================================
--- forrest/trunk/forrestcore/src/documentation/content/xdocs/docs/skins.xml	(original)
+++ forrest/trunk/forrestcore/src/documentation/content/xdocs/docs/skins.xml	Sun Oct 31 01:32:28 2004
@@ -14,7 +14,7 @@
   See the License for the specific language governing permissions and
   limitations under the License.
 -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd">
+<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd">
 <document>
   <header>
     <title>Default skins</title>
@@ -34,7 +34,7 @@
       <p>
         The skin names are based on playing with the word "skin". See our
         technique for
-        <link href="http://svn.apache.org/repos/asf/forrest/trunk/src/core/context/skins/new-skin-names.txt">choosing skin names</link>.
+        <a href="http://svn.apache.org/repos/asf/forrest/trunk/src/core/context/skins/new-skin-names.txt">choosing skin names</a>.
         A name with "-dev" extension signifies that it is under development.
         There is no concept of versions of default skins.
         New skins have new names.
@@ -42,7 +42,7 @@
     </section>
 
     <section id="skins">
-      <title>Skin descriptions</title>
+      <title>Skin descriptions and examples</title>
 
       <section id="pelt">
         <title>pelt</title>
@@ -50,6 +50,10 @@
           Uses CSS "div" and no HTML tables.
           During its earlier development, this skin used to be called "css-style-dev".
         </p>
+        <p>Examples:
+          <a href="site:forrest">Apache Forrest</a> |
+          <a href="site:references/lenya">Apache Lenya</a>
+        </p>
       </section>
 
       <section id="leather-dev">
@@ -58,15 +62,22 @@
           This is the evolution of the "pelt" skin, to have naming
           conventions for css elements. It is still in development.
         </p>
+
+        <p>Examples:
+          <a href="../images/snapshot-leather-dev.png">snapshot</a>
+        </p>
       </section>
   
       <section id="tigris">
         <title>tigris</title>
         <p>
           This skin is based on version 1.1 of the 
-          <link href="http://style.tigris.org/">style.tigris.org</link> project.
+          <a href="http://style.tigris.org/">style.tigris.org</a> project.
           (It deliberately contravenes our skin naming convention.)
         </p>
+        <p>Examples:
+          <a href="http://www.core.gen.tr/">Core Computer Security Group</a>
+        </p>
       </section>
 
       <section id="plain-dev">
@@ -76,6 +87,10 @@
           Such capability might be useful to generate a collection of
           documents for some off-line product's user help system.
         </p>
+
+        <p>Examples:
+          <a href="../images/snapshot-plain-dev.png">snapshot</a>
+        </p>
       </section>
     </section>
 
@@ -92,12 +107,18 @@
           This is the old skin that we have been dragging around since early
           days. Uses HTML tables.
         </p>
+        <p>Examples:
+          <a href="site:references/xml">Apache XML</a>
+        </p>
       </section>
 
       <section id="krysalis-site">
         <title>krysalis-site</title>
         <p>
           Uses HTML tables.
+        </p>
+
+        <p>Examples:
         </p>
       </section>
     </section>

Added: forrest/trunk/forrestcore/src/documentation/content/xdocs/images/snapshot-leather-dev.png
==============================================================================
Binary file. No diff available.

Added: forrest/trunk/forrestcore/src/documentation/content/xdocs/images/snapshot-plain-dev.png
==============================================================================
Binary file. No diff available.

Modified: forrest/trunk/forrestcore/status.xml
==============================================================================
--- forrest/trunk/forrestcore/status.xml	(original)
+++ forrest/trunk/forrestcore/status.xml	Sun Oct 31 01:32:28 2004
@@ -44,9 +44,13 @@
 
   <changes>
     <release version="0.7-dev" date="not yet released">
+      <action dev="DC" type="add" context="docs">
+        Added links to example websites to demonstrate each available
+        <link href="site:skins">default skin</link>. 
+      </action>
       <action dev="DC" type="add" context="core"
         due-to="Tamara Harpster" fixes-bug="FOR-322">
-        Added to the document-v20 DTD to support usemap attribute in img tag.
+        Added to the document-v20 DTD to support "usemap" attribute in img tag.
         Also added demonstration of client-side imagemap to the "seed site".
       </action>
       <action dev="JJP" type="update" context="docs"
@@ -60,9 +64,9 @@
         See <link href="site:plugins">Extending Forrest with Plugins</link>.
       </action>
       <action dev="JJP" type="update" context="core">
-        Update fop0.20.5 just with  optional jimi support.
-        This fixes the issue building the apache fop site.
-        Replace libraries from the cocoon 2.2.0-dev version.
+        Update fop-0.20.5 just with optional jimi support.
+        This fixes the issue building the Apache FOP site.
+        Replace libraries to use the cocoon-2.2.0-dev version.
       </action>
       <action dev="DC" type="add" context="core"
         due-to="Upayavira" fixes-bug="FOR-204">