forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r384122 - in /forrest/site: docs_0_80/linking.html docs_0_80/linking.pdf docs_0_80/your-project.html docs_0_80/your-project.pdf live-sites.html live-sites.pdf
Date Wed, 08 Mar 2006 05:25:36 GMT
Author: crossley
Date: Tue Mar  7 21:25:33 2006
New Revision: 384122

Automatic publish from forrestbot


Modified: forrest/site/docs_0_80/linking.html
--- forrest/site/docs_0_80/linking.html (original)
+++ forrest/site/docs_0_80/linking.html Tue Mar  7 21:25:33 2006
@@ -700,6 +700,10 @@
+            See the various notes above, not repeated in this list of tips.
+          </li>
             View your site's 
             <a href="../abs-menulinks">abs-menulinks</a> pipeline in a
             browser. This is part of the internal Cocoon machinery, but like
@@ -758,7 +762,7 @@
-<a name="N10229"></a><a name="toc-generation"></a>
+<a name="N1022C"></a><a name="toc-generation"></a>
 <h2 class="underlined_10">Table of Contents Generation</h2>
 <div class="section">
 <p>Each page can have an automatically generated table of contents. This
@@ -804,10 +808,10 @@
-<a name="N1025E"></a><a name="linking"></a>
+<a name="N10261"></a><a name="linking"></a>
 <h2 class="underlined_10">Linking systems</h2>
 <div class="section">
-<a name="N10264"></a><a name="direct-linking"></a>
+<a name="N10267"></a><a name="direct-linking"></a>
 <h3 class="underlined_5">Direct linking</h3>
           In earlier versions of Forrest (and in similar systems), there has
@@ -826,7 +830,7 @@
           typically renders to multiple output formats (HTML and PDF), links in
           one of them (here, the PDF) are likely to break.
-<a name="N10289"></a><a name="indirect-linking"></a>
+<a name="N1028C"></a><a name="indirect-linking"></a>
 <h3 class="underlined_5">Indirect linking</h3>
           Forrest's solution is simple: instead of &lt;a href="todo.html"&gt;,
@@ -854,7 +858,7 @@
           "idea" of "the todo file".  It doesn't matter where it physically lives;
           that will be sorted out by Forrest.
-<a name="N102B0"></a><a name="resolve-site-uris"></a>
+<a name="N102B3"></a><a name="resolve-site-uris"></a>
 <h4>Resolving site: URIs</h4>
             So how does "<span class="codefrag">site:v0.80//todo</span>" get
resolved?  A full answer
@@ -889,7 +893,7 @@
             "new_content_type" its own XML file, or a node in another file, in
             another category.
-<a name="N102EE"></a><a name="resolve-ext-uris"></a>
+<a name="N102F1"></a><a name="resolve-ext-uris"></a>
 <h4>ext: URIs: linking to external URLs</h4>
             The "<span class="codefrag">ext:</span>" scheme was created partly
to demonstrate the
@@ -924,7 +928,7 @@
             Specifically, the "@href" aggregation makes defining large numbers of
             related URLs easy.
-<a name="N10321"></a><a name="source-uris"></a>
+<a name="N10324"></a><a name="source-uris"></a>
 <h4>Theory: source URIs</h4>
             The "<span class="codefrag">site:</span>" URIs like "<span class="codefrag">site:v0.80//todo</span>"
are examples of
@@ -940,7 +944,7 @@
             in the destination URI space, just like exotic XML source formats are
             translated into plain old HTML in the output.
-<a name="N10340"></a><a name="future-schemes"></a>
+<a name="N10343"></a><a name="future-schemes"></a>
 <h4>Future schemes</h4>
             So far, the "<span class="codefrag">site:</span>" and "<span class="codefrag">ext:</span>"
schemes are defined.
@@ -1010,7 +1014,7 @@
-<a name="N103E3"></a><a name="concept"></a>
+<a name="N103E6"></a><a name="concept"></a>
 <h2 class="underlined_10">Concept</h2>
 <div class="section">
@@ -1025,7 +1029,7 @@
-<a name="N103FA"></a><a name="implementation"></a>
+<a name="N103FD"></a><a name="implementation"></a>
 <h2 class="underlined_10">Implementation</h2>
 <div class="section">
 <p>Full details on the implementation of

Modified: forrest/site/docs_0_80/linking.pdf
Binary files - no diff available.

Modified: forrest/site/docs_0_80/your-project.html
--- forrest/site/docs_0_80/your-project.html (original)
+++ forrest/site/docs_0_80/your-project.html Tue Mar  7 21:25:33 2006
@@ -1584,6 +1584,13 @@
 <div class="warning">
 <div class="label">Warning</div>
+<div class="content">See issue
+        <a href="">FOR-145</a>
+        which causes clashes of Ant target names.
+      </div>
+<div class="warning">
+<div class="label">Warning</div>
 <div class="content">There is a bug in the plugin download mechanism in
       Forrest 0.7 that may prevent
       your plugins being installed correctly when calling Forrest from ANT. You

Modified: forrest/site/docs_0_80/your-project.pdf
Binary files - no diff available.

Modified: forrest/site/live-sites.html
--- forrest/site/live-sites.html (original)
+++ forrest/site/live-sites.html Tue Mar  7 21:25:33 2006
@@ -497,6 +497,12 @@
 <a href="">Apache Lenya 
           Zone</a> - this site is using v2 with some nice demonstrations of 
           new features like the theme switcher.</li>
+<a href="">tarGET-X</a> - know the 
+          unknown. The original idea of this site is to be a service broker. It 
+          is the website of Forrest committer: Thorsten Scherler.
+          </li>
         <!--  <li><link href=""></link></li> -->

Modified: forrest/site/live-sites.pdf
Binary files - no diff available.

View raw message