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/10/28 09:19:58 UTC
svn commit: r329143 [2/2] - in /forrest/site: ./ docs_0_60/ docs_0_70/
docs_0_70/howto/ docs_0_80/ docs_0_80/howto/ plan/ skin/ tools/
Modified: forrest/site/docs_0_80/howto/sitemap.xmap.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/sitemap.xmap.html?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/sitemap.xmap.html (original)
+++ forrest/site/docs_0_80/howto/sitemap.xmap.html Fri Oct 28 00:18:42 2005
@@ -286,7 +286,7 @@
</li>
</ul>
</div>
-<a name="N1000A"></a><a name="sitemap.xmap"></a>
+<a name="N10010"></a><a name="sitemap.xmap"></a>
<h2 class="underlined_10">sitemap.xmap</h2>
<div class="section">
<pre>
@@ -299,7 +299,7 @@
$Revision: 1.12 $
==================================================== -->
</pre>
-<a name="N10010"></a><a name="Start+of+Sitemap"></a>
+<a name="N10016"></a><a name="Start+of+Sitemap"></a>
<h3 class="underlined_5">Start of Sitemap</h3>
<pre>
<map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
@@ -511,7 +511,7 @@
</map:resources>
</pre>
-<a name="N10016"></a><a name="Start+of+Pipelines"></a>
+<a name="N1001C"></a><a name="Start+of+Pipelines"></a>
<h3 class="underlined_5">Start of Pipelines</h3>
<pre>
<!-- =========================== Pipelines ================================= -->
@@ -519,7 +519,7 @@
<map:pipeline type="caching" internal-only="true">
</pre>
-<a name="N1001C"></a><a name="Test+for+First+Pipeline"></a>
+<a name="N10022"></a><a name="Test+for+First+Pipeline"></a>
<h3 class="underlined_5">Test for First Pipeline</h3>
<pre>
<map:match pattern="*.xlex">
@@ -541,7 +541,7 @@
</map:match>
</map:pipeline>
</pre>
-<a name="N10022"></a><a name="Insertion+Point+for+Project+Sitemap"></a>
+<a name="N10028"></a><a name="Insertion+Point+for+Project+Sitemap"></a>
<h3 class="underlined_5">Insertion Point for Project Sitemap</h3>
<pre>
<!--
@@ -605,7 +605,7 @@
<!-- ============================================================ -->
<!-- http://forrest.apache.org/docs/sitemap-ref.html#source_pipelines -->
</pre>
-<a name="N10028"></a><a name="First+Match+for+%27**.xml%27"></a>
+<a name="N1002E"></a><a name="First+Match+for+%27**.xml%27"></a>
<h3 class="underlined_5">First Match for '**.xml'</h3>
<pre>
<!-- Body content -->
@@ -704,7 +704,7 @@
<map:mount uri-prefix="" src="faq.xmap" check-reload="yes" />
</map:match>
</pre>
-<a name="N1002E"></a><a name="First+Match+for+%27**body-*.html%27"></a>
+<a name="N10034"></a><a name="First+Match+for+%27**body-*.html%27"></a>
<h3 class="underlined_5">First Match for '**body-*.html'</h3>
<pre>
<map:match pattern="**body-*.html">
@@ -719,7 +719,7 @@
</map:select>
</map:match>
</pre>
-<a name="N10034"></a><a name="Second+Match+for+%27**body-*.html%27"></a>
+<a name="N1003A"></a><a name="Second+Match+for+%27**body-*.html%27"></a>
<h3 class="underlined_5">Second Match for '**body-*.html'</h3>
<pre>
<!-- Default matches -->
@@ -727,7 +727,7 @@
<map:match pattern="**body-*.html">
<map:generate src="cocoon:/{1}{2}.xml"/>
</pre>
-<a name="N1003A"></a><a name="Returning+to+the+%27**body-*.html%27+Pipeline"></a>
+<a name="N10040"></a><a name="Returning+to+the+%27**body-*.html%27+Pipeline"></a>
<h3 class="underlined_5">Returning to the '**body-*.html' Pipeline</h3>
<pre>
<map:transform type="idgen"/>
@@ -795,7 +795,7 @@
</map:call>
</map:match>
</pre>
-<a name="N10040"></a><a name="First+Match+for+%22**%2F*.html%22"></a>
+<a name="N10046"></a><a name="First+Match+for+%22**%2F*.html%22"></a>
<h3 class="underlined_5">First Match for "**/*.html"</h3>
<pre>
<map:match pattern="**/*.html">
Modified: forrest/site/docs_0_80/howto/sitemap.xmap.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/sitemap.xmap.pdf?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/docs_0_80/locationmap.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/locationmap.html?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
--- forrest/site/docs_0_80/locationmap.html (original)
+++ forrest/site/docs_0_80/locationmap.html Fri Oct 28 00:18:42 2005
@@ -339,7 +339,7 @@
<a href="#namingConvention">Naming Convention</a>
</li>
<li>
-<a href="#selector">Location Selectors</a>
+<a href="#selector">Multiple Location Selectors</a>
</li>
<li>
<a href="#examples">Locationmap Examples</a>
@@ -388,13 +388,22 @@
the locationmap however the leaf does not identify a pipeline, but instead identifies
a location string.</p>
<p>Apache Forrest looks in the standard location for the source file first (by default
- <span class="codefrag">PROJECT_HOME/src/documentation/content/xdocs/...</span>), if a file is found in this
+ <span class="codefrag">PROJECT_HOME/src/documentation/content/...</span>), if a file is found in this
location then the locationmap is not consulted. However, if one is not found then the
- locationmap is used to resolve the source file.</p>
+ locationmap is used to resolve the source file. The locationmap is resolved via the
+ core sitemap, this means that you can generate it dynamically if you so wish. Simply
+ add a match that looks something like this to your projects sitemap:</p>
+<pre class="code">
+ <map:match pattern="locationmap-project.xml">
+ <map:generate src="..."/>
+ <map:transform src="..."/>
+ <map:serialize type="xml"/>
+ </map:match>
+ </pre>
</div>
-<a name="N10038"></a><a name="namingConvention"></a>
+<a name="N1003C"></a><a name="namingConvention"></a>
<h2 class="underlined_10">Naming Convention</h2>
<div class="section">
<p>For those that are familiar with name
@@ -416,24 +425,30 @@
<pre class="code">
<map:transform src="{lm:transform.xhtml2.html}"/>
</pre>
+<p>Where the resource is provided by a plugin rather than Forrest itself
+ this is prefixed with the last part of the plugin name. For example:</p>
+<pre class="code">
+<map:transform src="{lm:projectInfo.transform.doap.html}"/>
+ </pre>
<p>The format is essentially one of:</p>
<pre class="code">
-resource-type(dot)from-format(dot)to-format
+[PLUGIN_NAME.]resource-type(dot)from-format(dot)to-format
</pre>
<p>or</p>
<pre class="code">
-resource-type(dot)type(dot)name
+[PLUGIN_NAME.]resource-type(dot)type(dot)name
</pre>
<p>Examples of these two:</p>
<pre class="code">
-transform.xslt.xthml2.html
+transform.transform.xthml2.html
graphic.png.project-logo
+projectInfo.transform.changes.rss
</pre>
</div>
-<a name="N10068"></a><a name="selector"></a>
-<h2 class="underlined_10">Location Selectors</h2>
+<a name="N10073"></a><a name="selector"></a>
+<h2 class="underlined_10">Multiple Location Selectors</h2>
<div class="section">
<p>You can define multiple possble locations for a file in the locationmap
with the following code:</p>
@@ -450,10 +465,10 @@
</div>
-<a name="N10079"></a><a name="examples"></a>
+<a name="N10084"></a><a name="examples"></a>
<h2 class="underlined_10">Locationmap Examples</h2>
<div class="section">
-<a name="N1007F"></a><a name="source-via-http"></a>
+<a name="N1008A"></a><a name="source-via-http"></a>
<h3 class="underlined_5">Retrieving an XDoc via HTTP</h3>
<p>Normally files are generated from <span class="codefrag">{project:content.xdocs}</span>.
Using the Locationmap it is possible to make these files come from elsewhere.
@@ -481,7 +496,7 @@
<div class="content">Because of the above limitation many of the links in the
page generated from the above example are broken.</div>
</div>
-<a name="N100A5"></a><a name="source-from-remote-cms"></a>
+<a name="N100B0"></a><a name="source-from-remote-cms"></a>
<h3 class="underlined_5">Retrieving HTML from a CMS</h3>
<p>Using the locationmap you can use Forrest to retrieve data from a
Content Management System (CMS), wither local or remote.
@@ -551,7 +566,7 @@
<div class="content">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.</div>
</div>
-<a name="N100E3"></a><a name="linkrewriting"></a>
+<a name="N100EE"></a><a name="linkrewriting"></a>
<h3 class="underlined_5">Link Rewriting</h3>
<p>The locationmap can be used to rewrite URLs when the page is generated.
For example, when the locationmap has:</p>
Modified: forrest/site/docs_0_80/locationmap.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/locationmap.pdf?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/docs_0_80/sitemap-ref.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/sitemap-ref.html?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
--- forrest/site/docs_0_80/sitemap-ref.html (original)
+++ forrest/site/docs_0_80/sitemap-ref.html Fri Oct 28 00:18:42 2005
@@ -1060,8 +1060,8 @@
InputModule to look up the key value. The <span class="codefrag">scheme:address</span>
URI is then rewritten with the found value. This transformer was
implemented as
- <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15611">LinkRewriterTransformer</a>
- and is distributed as the Cocoon "linkrewriter" block.
+ <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=15611">LinkRewriterTransformer</a>,
+ currently distributed as a "block" in Cocoon 2.1
</p>
<a name="N103A4"></a><a name="implement_rewriting"></a>
<h3 class="underlined_5">Implementing "site:" rewriting</h3>
Modified: forrest/site/docs_0_80/sitemap-ref.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/sitemap-ref.pdf?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/forrest-issues.html
URL: http://svn.apache.org/viewcvs/forrest/site/forrest-issues.html?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Fri Oct 28 00:18:42 2005
@@ -189,13 +189,16 @@
<a href="#%5BFOR-144%5D+define+new+format+for+skinconf.xml">[FOR-144] define new format for skinconf.xml</a>
</li>
<li>
+<a href="#%5BFOR-588%5D+Design+new+configuration+system">[FOR-588] Design new configuration system</a>
+</li>
+<li>
<a href="#%5BFOR-591%5D+MaxMemory+needs+increasing">[FOR-591] MaxMemory needs increasing</a>
</li>
<li>
-<a href="#%5BFOR-588%5D+Design+new+configuration+system">[FOR-588] Design new configuration system</a>
+<a href="#%5BFOR-713%5D+HTML-to-document.xsl+no+longer+generates+an+XDoc">[FOR-713] HTML-to-document.xsl no longer generates an XDoc</a>
</li>
<li>
-<a href="#%5BFOR-675%5D+upgrading+to+commons-jxpath-1.2.jar+causes+failures+with+linkrewriter+protocols+site%3A+etc.">[FOR-675] upgrading to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc.</a>
+<a href="#%5BFOR-572%5D+run+a+memory+profiler+while+forrest+is+operating">[FOR-572] run a memory profiler while forrest is operating</a>
</li>
<li>
<a href="#%5BFOR-427%5D+Need+licensing+element+in+plugins.xml">[FOR-427] Need licensing element in plugins.xml</a>
@@ -213,10 +216,13 @@
<a href="#%5BFOR-701%5D+Missing+locationmap+entry+gives+poor+error">[FOR-701] Missing locationmap entry gives poor error</a>
</li>
<li>
-<a href="#%5BFOR-572%5D+run+a+memory+profiler+while+forrest+is+operating">[FOR-572] run a memory profiler while forrest is operating</a>
+<a href="#%5BFOR-707%5D+Document+i18n+features+of+Forrest">[FOR-707] Document i18n features of Forrest</a>
</li>
<li>
-<a href="#%5BFOR-707%5D+Document+i18n+features+of+Forrest">[FOR-707] Document i18n features of Forrest</a>
+<a href="#%5BFOR-711%5D+Cache+results+from+the+Locationmap">[FOR-711] Cache results from the Locationmap</a>
+</li>
+<li>
+<a href="#%5BFOR-675%5D+upgrading+to+commons-jxpath-1.2.jar+causes+failures+with+linkrewriter+protocols+site%3A+etc.">[FOR-675] upgrading to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc.</a>
</li>
<li>
<a href="#%5BFOR-490%5D+serve+multiple+sites+on+a+single+Forrest+instance">[FOR-490] serve multiple sites on a single Forrest instance</a>
@@ -237,10 +243,10 @@
<a href="#%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes">[FOR-241] character entities (e.g. ampersand) are expanded again for href or src attributes</a>
</li>
<li>
-<a href="#%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs">[FOR-209] First level selected tab is not highlighted when containing 2nd level tabs</a>
+<a href="#%5BFOR-210%5D+whole-site+html+and+pdf%3A+broken+link+faq%2C+broken+image+links">[FOR-210] whole-site html and pdf: broken link faq, broken image links</a>
</li>
<li>
-<a href="#%5BFOR-210%5D+whole-site+html+and+pdf%3A+broken+link+faq%2C+broken+image+links">[FOR-210] whole-site html and pdf: broken link faq, broken image links</a>
+<a href="#%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs">[FOR-209] First level selected tab is not highlighted when containing 2nd level tabs</a>
</li>
<li>
<a href="#%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links">[FOR-211] whole-site html and pdf: broken ext links</a>
@@ -252,13 +258,7 @@
<a href="#%5BFOR-203%5D+2nd+level+tabs+are+not+selected+appropriately">[FOR-203] 2nd level tabs are not selected appropriately</a>
</li>
<li>
-<a href="#%5BFOR-187%5D+Redefine+project+documentation+dirs">[FOR-187] Redefine project documentation dirs</a>
-</li>
-<li>
-<a href="#%5BFOR-184%5D+Switch+to+XHTML2">[FOR-184] Switch to XHTML2</a>
-</li>
-<li>
-<a href="#%5BFOR-157%5D+skin-descriptors+comma+separated+list+fails">[FOR-157] skin-descriptors comma separated list fails</a>
+<a href="#%5BFOR-200%5D+Locationmap+for+Forrest+and+Users">[FOR-200] Locationmap for Forrest and Users</a>
</li>
</ul>
</div>
@@ -277,278 +277,286 @@
<a href="http://issues.apache.org/jira/browse/FOR-144">http://issues.apache.org/jira/browse/FOR-144</a>
</p>
<p>We are attempting to define a new extensible skinconf format. Here is one thread where the discussion is happening (there were some other threads leading up to that).
-<br/>
+<br>
<a href="http://marc.theaimsgroup.com/?t=108315759100005">http://marc.theaimsgroup.com/?t=108315759100005</a>
-<br/>
+<br>
-<br/>
+<br>
-<br/>
+<br>
-<br/>
+<br>
+</p>
+</div>
+<a name="N1001F"></a><a name="%5BFOR-588%5D+Design+new+configuration+system"></a>
+<h2 class="underlined_10">[FOR-588] Design new configuration system</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-588">http://issues.apache.org/jira/browse/FOR-588</a>
</p>
+<p>We need a new config system for Forrest for various reasons: the initial config system was known to be limited; to enable the specification of multiple Forrest sites within a single instance of Forrest; to accommodate the changes brought about by forrest:views, themes, and plugins.</p>
</div>
-<a name="N1001F"></a><a name="%5BFOR-591%5D+MaxMemory+needs+increasing"></a>
+<a name="N1002D"></a><a name="%5BFOR-591%5D+MaxMemory+needs+increasing"></a>
<h2 class="underlined_10">[FOR-591] MaxMemory needs increasing</h2>
<div class="section">
<p>
<a href="http://issues.apache.org/jira/browse/FOR-591">http://issues.apache.org/jira/browse/FOR-591</a>
</p>
<p>Since the docs restructurng for the 0.7 release it has become necessary to increase the maxmemory to be able to build the Forrest site.
-<br/>
+<br>
-<br/>
+<br>
Does this indicate a memory leak?
-<br/>
+<br>
-<br/>
+<br>
Does someone have the tools to run some diagnostics?
-<br/>
+<br>
-<br/>
+<br>
(NB maxmemory has been increased in forrest.properties, if we resolve this issue it should be reduced again)</p>
</div>
-<a name="N1002D"></a><a name="%5BFOR-588%5D+Design+new+configuration+system"></a>
-<h2 class="underlined_10">[FOR-588] Design new configuration system</h2>
+<a name="N1003B"></a><a name="%5BFOR-713%5D+HTML-to-document.xsl+no+longer+generates+an+XDoc"></a>
+<h2 class="underlined_10">[FOR-713] HTML-to-document.xsl no longer generates an XDoc</h2>
<div class="section">
<p>
-<a href="http://issues.apache.org/jira/browse/FOR-588">http://issues.apache.org/jira/browse/FOR-588</a>
+<a href="http://issues.apache.org/jira/browse/FOR-713">http://issues.apache.org/jira/browse/FOR-713</a>
+</p>
+<p>html-to-document.xsl no longer converts content to an XDoc. Instead it renders converts documents to XDoc, instead it allows H1, H2 etc. elements to pass through.
+<br>
+
+<br>
+The result is a page that seems to render correctly and in the single test case I have used it still renders correctly in PDF and Text format. However, this is a backward incompatible change that will break sites that use includes with XPath statements such as /section[@id=&quot;foo&quot;] (sections are no longer created)
+<br>
+
+<br>
</p>
-<p>We need a new config system for Forrest for various reasons: the initial config system was known to be limited; to enable the specification of multiple Forrest sites within a single instance of Forrest; to accommodate the changes brought about by forrest:views, themes, and plugins.</p>
</div>
-<a name="N1003B"></a><a name="%5BFOR-675%5D+upgrading+to+commons-jxpath-1.2.jar+causes+failures+with+linkrewriter+protocols+site%3A+etc."></a>
-<h2 class="underlined_10">[FOR-675] upgrading to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc.</h2>
+<a name="N10049"></a><a name="%5BFOR-572%5D+run+a+memory+profiler+while+forrest+is+operating"></a>
+<h2 class="underlined_10">[FOR-572] run a memory profiler while forrest is operating</h2>
<div class="section">
<p>
-<a href="http://issues.apache.org/jira/browse/FOR-675">http://issues.apache.org/jira/browse/FOR-675</a>
+<a href="http://issues.apache.org/jira/browse/FOR-572">http://issues.apache.org/jira/browse/FOR-572</a>
</p>
-<p>upgrading from commons-jxpath-20030909.jar to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc. This happens in both modes: 'forret run' and 'forrest'.</p>
+<p>We need to run a memory profiler while forrest is operating.</p>
</div>
-<a name="N10049"></a><a name="%5BFOR-427%5D+Need+licensing+element+in+plugins.xml"></a>
+<a name="N10057"></a><a name="%5BFOR-427%5D+Need+licensing+element+in+plugins.xml"></a>
<h2 class="underlined_10">[FOR-427] Need licensing element in plugins.xml</h2>
<div class="section">
<p>
<a href="http://issues.apache.org/jira/browse/FOR-427">http://issues.apache.org/jira/browse/FOR-427</a>
</p>
-<p>Since plugins can be hosted on different sites they can be released under licenses other than the Apache one. We need an element in plugins.xml that records the type of license a plugin is released under. This element should be used by the plugin install process to verify that the user agrees to the terms of that license before download and installation is started.<br/>
+<p>Since plugins can be hosted on different sites they can be released under licenses other than the Apache one. We need an element in plugins.xml that records the type of license a plugin is released under. This element should be used by the plugin install process to verify that the user agrees to the terms of that license before download and installation is started.<br>
</p>
</div>
-<a name="N10057"></a><a name="%5BFOR-388%5D+Use+plugins+in-place+if+src+available"></a>
+<a name="N10065"></a><a name="%5BFOR-388%5D+Use+plugins+in-place+if+src+available"></a>
<h2 class="underlined_10">[FOR-388] Use plugins in-place if src available</h2>
<div class="section">
<p>
<a href="http://issues.apache.org/jira/browse/FOR-388">http://issues.apache.org/jira/browse/FOR-388</a>
</p>
<p>At present Forrest will attempt to download plugins even if they are available in src form in the local filesystem as part of an SVN checkout.
-<br/>
+<br>
-<br/>
+<br>
Have Forrest mount plugins from designated directories in preference to downloading them wherever possible (need more than posible location for src plugins as some people may be developing their own plugins outside of Forrest)
-<br/>
+<br>
-<br/>
+<br>
</p>
</div>
-<a name="N10065"></a><a name="%5BFOR-630%5D+Forrest+strategy+and+direction"></a>
+<a name="N10073"></a><a name="%5BFOR-630%5D+Forrest+strategy+and+direction"></a>
<h2 class="underlined_10">[FOR-630] Forrest strategy and direction</h2>
<div class="section">
<p>
<a href="http://issues.apache.org/jira/browse/FOR-630">http://issues.apache.org/jira/browse/FOR-630</a>
</p>
<p>Topics for discussion gathered at ApacheCon EU 2005.
-<br/>
+<br>
-<br/>
+<br>
WARNING: Only reply to the general theme of this
-<br/>
+<br>
topics list. Please create separate threads for
-<br/>
+<br>
each specific topic.
-<br/>
+<br>
-<br/>
+<br>
Actually we should be using Jira for some of this.
-<br/>
+<br>
How about discussing on the mailing list, and
-<br/>
+<br>
putting summaries into Jira.
-<br/>
+<br>
-<br/>
+<br>
I have the scraps of paper that Nicola Ken wrote.
-<br/>
+<br>
Photographs are in:
-<br/>
+<br>
<a href="http://svn.apache.org/repos/asf/forrest/events/apachecon-eu-2005">http://svn.apache.org/repos/asf/forrest/events/apachecon-eu-2005</a>
-<br/>
+<br>
Ross helped me to interpret some of the sqwiggles,
-<br/>
+<br>
but there are still some obscure parts (marked
-<br/>
+<br>
with #? below). The items are raw, i have not tried
-<br/>
+<br>
to explain any or add others.
-<br/>
+<br>
-<br/>
+<br>
List of topics is in no particular order and
-<br/>
+<br>
it is not complete. We spent maybe 15 minutes
-<br/>
+<br>
brainstorming. We had a first quick pass at
-<br/>
+<br>
assigning some priority.
-<br/>
+<br>
-<br/>
+<br>
I don't understand NKBs priority symbols.
-<br/>
+<br>
Anyway some items where marked with
-<br/>
+<br>
&nbsp;circle ... [C]
-<br/>
+<br>
&nbsp;square ... [S]
-<br/>
+<br>
-<br/>
+<br>
Then we went straight on to the top topic:
-<br/>
+<br>
&quot;configuration&quot; and spent the rest of the day.
-<br/>
+<br>
-<br/>
+<br>
--------------
-<br/>
+<br>
-<br/>
+<br>
* Create lenya/forrest publication.
-<br/>
+<br>
-<br/>
+<br>
* [C] Naming convention for &quot;views&quot;.
-<br/>
+<br>
-<br/>
+<br>
* Roadmap specifically for views.
-<br/>
+<br>
-<br/>
+<br>
* [S] i18n support with locationmap.
-<br/>
+<br>
-<br/>
+<br>
* Locationmap - what is needed to complete it.
-<br/>
+<br>
-<br/>
+<br>
* [C] Configuration |=&gt; apache #? arrow apache #?
-<br/>
+<br>
-<br/>
+<br>
* TraversableSource ...
-<br/>
+<br>
-<br/>
+<br>
&nbsp;&nbsp;* Source resolving for locationmap.
-<br/>
+<br>
-<br/>
+<br>
&nbsp;&nbsp;* [C] How views are interacting with locationmap?
-<br/>
+<br>
-<br/>
+<br>
* [S] Documentation mismatch. Docs are distributed in
-<br/>
+<br>
&nbsp;&nbsp;various places: site, plugins, seed.
-<br/>
+<br>
-<br/>
+<br>
* Block documentation for Cocoon (/Forrest).
-<br/>
+<br>
-<br/>
+<br>
* [C] Pre-processing plugins.
-<br/>
+<br>
-<br/>
+<br>
* Flow of the plugin process.
-<br/>
+<br>
&nbsp;&nbsp;plugins - locationmap / flow #? this line obscure #?
-<br/>
+<br>
-<br/>
+<br>
* Memory profiling.
-<br/>
+<br>
-<br/>
+<br>
* Better use of Jira.
-<br/>
+<br>
-<br/>
+<br>
* [S] XHTML2 transition.
-<br/>
+<br>
-<br/>
+<br>
* [S] Live Forrest for Apache.
-<br/>
+<br>
&nbsp;&nbsp;(a configuration usecase)
-<br/>
+<br>
-<br/>
+<br>
* [S] New skins for views.
-<br/>
+<br>
-<br/>
+<br>
* Views ... body=&quot;true|false&quot; head=&quot;true|false&quot;
-<br/>
+<br>
-<br/>
+<br>
* The *.ft files in a plugin (one-to-many).
-<br/>
+<br>
-<br/>
+<br>
* Move into Java -&gt; 0.9.5 or when needed. #? no idea what #?
-<br/>
+<br>
&nbsp;&nbsp;&nbsp;&nbsp;
-<br/>
+<br>
* [C] View / doctypes.
-<br/>
+<br>
&nbsp;&nbsp;(view in view)
-<br/>
+<br>
-<br/>
+<br>
* [C] Content directory.</p>
</div>
-<a name="N10073"></a><a name="%5BFOR-654%5D+Create+Schema+for+XHTML2+subset"></a>
+<a name="N10081"></a><a name="%5BFOR-654%5D+Create+Schema+for+XHTML2+subset"></a>
<h2 class="underlined_10">[FOR-654] Create Schema for XHTML2 subset</h2>
<div class="section">
<p>
<a href="http://issues.apache.org/jira/browse/FOR-654">http://issues.apache.org/jira/browse/FOR-654</a>
</p>
<p>We need a RelaxNG schema for the subset of XHTML identified in:
-<br/>
+<br>
<a href="http://marc.theaimsgroup.com/?l=forrest-dev&m=112489488330888&w=2">http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=112489488330888&amp;w=2</a></p>
</div>
-<a name="N10081"></a><a name="%5BFOR-701%5D+Missing+locationmap+entry+gives+poor+error"></a>
+<a name="N1008F"></a><a name="%5BFOR-701%5D+Missing+locationmap+entry+gives+poor+error"></a>
<h2 class="underlined_10">[FOR-701] Missing locationmap entry gives poor error</h2>
<div class="section">
<p>
<a href="http://issues.apache.org/jira/browse/FOR-701">http://issues.apache.org/jira/browse/FOR-701</a>
</p>
<p>If there is no locationmap entry for a resource we get a &quot;resource not found&quot; error. This is fine if it is the actual source file that is missing. However, now that we are using the LM to find other intermediate resources, such as stylesheets etc. it can be misleading.
-<br/>
+<br>
-<br/>
+<br>
We need to throw a meaningful error when when a resource cannot be found.</p>
</div>
-<a name="N1008F"></a><a name="%5BFOR-572%5D+run+a+memory+profiler+while+forrest+is+operating"></a>
-<h2 class="underlined_10">[FOR-572] run a memory profiler while forrest is operating</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-572">http://issues.apache.org/jira/browse/FOR-572</a>
-</p>
-<p>We need to run a memory profiler while forrest is operating.</p>
-</div>
<a name="N1009D"></a><a name="%5BFOR-707%5D+Document+i18n+features+of+Forrest"></a>
<h2 class="underlined_10">[FOR-707] Document i18n features of Forrest</h2>
<div class="section">
@@ -556,66 +564,90 @@
<a href="http://issues.apache.org/jira/browse/FOR-707">http://issues.apache.org/jira/browse/FOR-707</a>
</p>
<p>There is next to no documentation about i18n, just a pretty poor FAQ entry that points at an issue that has now been closed.
-<br/>
+<br>
-<br/>
+<br>
Cheche wrote a blog entry on his work:
-<br/>
+<br>
-<br/>
+<br>
<a href="http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/">http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/</a>
-<br/>
+<br>
-<br/>
+<br>
We could, at the very least use the locationmap to pull this content into our site [OT: I wonder if this could be a way to generate more documentation?)</p>
</div>
-<a name="N100AB"></a><a name="%5BFOR-490%5D+serve+multiple+sites+on+a+single+Forrest+instance"></a>
+<a name="N100AB"></a><a name="%5BFOR-711%5D+Cache+results+from+the+Locationmap"></a>
+<h2 class="underlined_10">[FOR-711] Cache results from the Locationmap</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-711">http://issues.apache.org/jira/browse/FOR-711</a>
+</p>
+<p>Now that we are using the locationmap extensively it is showing up just how innefficient it is. The problem is that for the majority of requests there are multiple reqeuests to the locationmap. We can make things much faster (especially on the first page request) by caching results in the locationmap.
+<br>
+
+<br>
+I think a simple cache will sufice, lets just provide a static hashmap using the hint as a key and, of course, the location as the value.
+<br>
+
+<br>
+If we test all locationmaps and find no result we should record that tere is no result in this hashmap. This will also be a good place to throw an exception so that Cocoon can better report such errors (see FOR-701)</p>
+</div>
+<a name="N100B9"></a><a name="%5BFOR-675%5D+upgrading+to+commons-jxpath-1.2.jar+causes+failures+with+linkrewriter+protocols+site%3A+etc."></a>
+<h2 class="underlined_10">[FOR-675] upgrading to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc.</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-675">http://issues.apache.org/jira/browse/FOR-675</a>
+</p>
+<p>upgrading from commons-jxpath-20030909.jar to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc. This happens in both modes: 'forret run' and 'forrest'.</p>
+</div>
+<a name="N100C7"></a><a name="%5BFOR-490%5D+serve+multiple+sites+on+a+single+Forrest+instance"></a>
<h2 class="underlined_10">[FOR-490] serve multiple sites on a single Forrest instance</h2>
<div class="section">
<p>
<a href="http://issues.apache.org/jira/browse/FOR-490">http://issues.apache.org/jira/browse/FOR-490</a>
</p>
-<p>Nicola Ken Barozzi wrote:<br/>
-&gt; After that, it would be beneficial to be able to serve <br/>
-&gt; multiple sites on a single Forrest instance, so that we <br/>
-&gt; can have other projects join and <br/>
-&gt; have their site served.<br/>
-<br/>
-This last point (seving multiple &quot;sites&quot; from one Forrest<br/>
-instance) is important even without moving Forrest to a<br/>
-live server (I'm +1 on this).<br/>
-<br/>
-Right now we have various styleguides in Forrest and if<br/>
-I need to run them at once I have to start Forrest/jetty<br/>
-with different ports.<br/>
-<br/>
-(From Thread &quot;[RT] Serving Apache Forrest site from live Forrest&quot;<br/>
+<p>Nicola Ken Barozzi wrote:<br>
+&gt; After that, it would be beneficial to be able to serve <br>
+&gt; multiple sites on a single Forrest instance, so that we <br>
+&gt; can have other projects join and <br>
+&gt; have their site served.<br>
+<br>
+This last point (seving multiple &quot;sites&quot; from one Forrest<br>
+instance) is important even without moving Forrest to a<br>
+live server (I'm +1 on this).<br>
+<br>
+Right now we have various styleguides in Forrest and if<br>
+I need to run them at once I have to start Forrest/jetty<br>
+with different ports.<br>
+<br>
+(From Thread &quot;[RT] Serving Apache Forrest site from live Forrest&quot;<br>
on dev-list. Will add link later.)</p>
</div>
-<a name="N100B9"></a><a name="%5BFOR-343%5D+Upgrading+Plugins"></a>
+<a name="N100D5"></a><a name="%5BFOR-343%5D+Upgrading+Plugins"></a>
<h2 class="underlined_10">[FOR-343] Upgrading Plugins</h2>
<div class="section">
<p>
<a href="http://issues.apache.org/jira/browse/FOR-343">http://issues.apache.org/jira/browse/FOR-343</a>
</p>
-<p>Currently when installing a plugin Forrest attempts to install the most suitable version available. However, it makes no attempt to upgrade plugins when an upgrade becomes available.<br/>
-<br/>
+<p>Currently when installing a plugin Forrest attempts to install the most suitable version available. However, it makes no attempt to upgrade plugins when an upgrade becomes available.<br>
+<br>
We need a traget in the buildfile that will upgrade an indicated plugin when possible. This can then (optionally) be used when running Forrest to automatically upgrade plugins.</p>
</div>
-<a name="N100C7"></a><a name="%5BFOR-277%5D+investigate+use+of+forrest-0.6-dev+as+webapp+with+Tomcat+5"></a>
+<a name="N100E3"></a><a name="%5BFOR-277%5D+investigate+use+of+forrest-0.6-dev+as+webapp+with+Tomcat+5"></a>
<h2 class="underlined_10">[FOR-277] investigate use of forrest-0.6-dev as webapp with Tomcat 5</h2>
<div class="section">
<p>
<a href="http://issues.apache.org/jira/browse/FOR-277">http://issues.apache.org/jira/browse/FOR-277</a>
</p>
-<p>Some people report having troubles running Forrest as a webapp under Tomcat. Needs investigation before 0.6 release.<br/>
-<br/>
-This is the background email to forrest-users:<br/>
-&nbsp;<a href="http://mail-archives.apache.org/eyebrowse/ReadMsg?listId=260&msgNo=282">http://mail-archives.apache.org/eyebrowse/ReadMsg?listId=260&amp;msgNo=282</a><br/>
-&nbsp;Forrest 0.6 Interaction with Tomcat 5.0.27<br/>
+<p>Some people report having troubles running Forrest as a webapp under Tomcat. Needs investigation before 0.6 release.<br>
+<br>
+This is the background email to forrest-users:<br>
+&nbsp;<a href="http://mail-archives.apache.org/eyebrowse/ReadMsg?listId=260&msgNo=282">http://mail-archives.apache.org/eyebrowse/ReadMsg?listId=260&amp;msgNo=282</a><br>
+&nbsp;Forrest 0.6 Interaction with Tomcat 5.0.27<br>
&nbsp;Wed, 4 Aug 2004 10:18:34 -0500</p>
</div>
-<a name="N100D5"></a><a name="%5BFOR-284%5D+link+rewriting+broken+when+linking+to+xml+source+views+which+contain+site%3A+links"></a>
+<a name="N100F1"></a><a name="%5BFOR-284%5D+link+rewriting+broken+when+linking+to+xml+source+views+which+contain+site%3A+links"></a>
<h2 class="underlined_10">[FOR-284] link rewriting broken when linking to xml source views which contain site: links</h2>
<div class="section">
<p>
@@ -623,86 +655,86 @@
</p>
<p>When linking to *.xml files (e.g. to demonstrate a source file) then if that file contains &quot;site:&quot; or &quot;ext:&quot; links, then they are reported as broken, e.g. docs/site:dtd-docs</p>
</div>
-<a name="N100E3"></a><a name="%5BFOR-247%5D+Tigris+*.css+need+cleanup+to+remove+our+local+changes"></a>
+<a name="N100FF"></a><a name="%5BFOR-247%5D+Tigris+*.css+need+cleanup+to+remove+our+local+changes"></a>
<h2 class="underlined_10">[FOR-247] Tigris *.css need cleanup to remove our local changes</h2>
<div class="section">
<p>
<a href="http://issues.apache.org/jira/browse/FOR-247">http://issues.apache.org/jira/browse/FOR-247</a>
</p>
-<p>We have made some local changes to our copies of the tigris *.css which actually need to go into an over-riding css. Also remove our license notice which was added by accident.<br/>
+<p>We have made some local changes to our copies of the tigris *.css which actually need to go into an over-riding css. Also remove our license notice which was added by accident.<br>
<a href="http://marc.theaimsgroup.com/?l=forrest-dev&m=109169132601758">http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=109169132601758</a></p>
</div>
-<a name="N100F1"></a><a name="%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes"></a>
+<a name="N1010D"></a><a name="%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes"></a>
<h2 class="underlined_10">[FOR-241] character entities (e.g. ampersand) are expanded again for href or src attributes</h2>
<div class="section">
<p>
<a href="http://issues.apache.org/jira/browse/FOR-241">http://issues.apache.org/jira/browse/FOR-241</a>
</p>
<p>If I have a url like this inside the XML source:
-<br/>
+<br>
-<br/>
+<br>
<a href="http://sourceforge.net/sflogo.php?group_id=comics-grabber&type=1">http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;type=1</a>
-<br/>
+<br>
-<br/>
+<br>
validate-xdocs fails because it wants the literal &amp; to be typed out as
-<br/>
+<br>
&amp; instead. So I correct it to become:
-<br/>
+<br>
-<br/>
+<br>
<a href="http://sourceforge.net/sflogo.php?group_id=comics-grabber&type=1">http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;type=1</a>
-<br/>
+<br>
-<br/>
+<br>
However, the generated HTML has the entity resolution UNDONE!:
-<br/>
+<br>
-<br/>
+<br>
<a href="http://sourceforge.net/sflogo.php?group_id=comics-grabber&type=1">http://sourceforge.net/sflogo.php?group_id=comics-grabber&amp;type=1</a>
-<br/>
+<br>
-<br/>
+<br>
This HTML fails validation as 4.01 transitional.
-<br/>
+<br>
-<br/>
+<br>
David Crossley adds:
-<br/>
+<br>
There is a demonstration of the problem in the document
-<br/>
+<br>
src/documentation/content/xdocs/docs/dreams.xml
-<br/>
+<br>
The ampersand in the link element text is properly handled but
-<br/>
+<br>
the ampersand in the link href attribute is not.</p>
</div>
-<a name="N100FF"></a><a name="%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs"></a>
-<h2 class="underlined_10">[FOR-209] First level selected tab is not highlighted when containing 2nd level tabs</h2>
+<a name="N1011B"></a><a name="%5BFOR-210%5D+whole-site+html+and+pdf%3A+broken+link+faq%2C+broken+image+links"></a>
+<h2 class="underlined_10">[FOR-210] whole-site html and pdf: broken link faq, broken image links</h2>
<div class="section">
<p>
-<a href="http://issues.apache.org/jira/browse/FOR-209">http://issues.apache.org/jira/browse/FOR-209</a>
+<a href="http://issues.apache.org/jira/browse/FOR-210">http://issues.apache.org/jira/browse/FOR-210</a>
</p>
-<p>When there are two levels of tabs, the selected first level tab does not get highlighted, nor are there any other visual or structural clues as to which first-level tab is active, and which contains the displayed 2nd level tabs.
-<br/>
-
-<br/>
-This is checked with both the default skin, and with tigris-style.
-<br/>
+<p>The &quot;fresh-site&quot; build from 'forrest seed site' reports some failures for faq.html and various missing images. Wonder if sitemap issue?<br>
+<br>
</p>
</div>
-<a name="N1010D"></a><a name="%5BFOR-210%5D+whole-site+html+and+pdf%3A+broken+link+faq%2C+broken+image+links"></a>
-<h2 class="underlined_10">[FOR-210] whole-site html and pdf: broken link faq, broken image links</h2>
+<a name="N10129"></a><a name="%5BFOR-209%5D+First+level+selected+tab+is+not+highlighted+when+containing+2nd+level+tabs"></a>
+<h2 class="underlined_10">[FOR-209] First level selected tab is not highlighted when containing 2nd level tabs</h2>
<div class="section">
<p>
-<a href="http://issues.apache.org/jira/browse/FOR-210">http://issues.apache.org/jira/browse/FOR-210</a>
+<a href="http://issues.apache.org/jira/browse/FOR-209">http://issues.apache.org/jira/browse/FOR-209</a>
</p>
-<p>The &quot;fresh-site&quot; build from 'forrest seed site' reports some failures for faq.html and various missing images. Wonder if sitemap issue?<br/>
-<br/>
+<p>When there are two levels of tabs, the selected first level tab does not get highlighted, nor are there any other visual or structural clues as to which first-level tab is active, and which contains the displayed 2nd level tabs.
+<br>
+
+<br>
+This is checked with both the default skin, and with tigris-style.
+<br>
</p>
</div>
-<a name="N1011B"></a><a name="%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links"></a>
+<a name="N10137"></a><a name="%5BFOR-211%5D+whole-site+html+and+pdf%3A+broken+ext+links"></a>
<h2 class="underlined_10">[FOR-211] whole-site html and pdf: broken ext links</h2>
<div class="section">
<p>
@@ -710,87 +742,54 @@
</p>
<p>In the the generated site.html all of the external links are broken (i.e. the href attributes are like ... error:#ext:forrest).</p>
</div>
-<a name="N10129"></a><a name="%5BFOR-215%5D+site.lucene+name+colaps+with+site.html+request"></a>
+<a name="N10145"></a><a name="%5BFOR-215%5D+site.lucene+name+colaps+with+site.html+request"></a>
<h2 class="underlined_10">[FOR-215] site.lucene name colaps with site.html request</h2>
<div class="section">
<p>
<a href="http://issues.apache.org/jira/browse/FOR-215">http://issues.apache.org/jira/browse/FOR-215</a>
</p>
-<p>Any link called site.html or site.pdf produce a loop on the search funcionality.<br/>
-<br/>
-The reason is an internal request called <a href="cocoon://site.lucene">cocoon://site.lucene</a> a work around would be to choose another name for this internal request.<br/>
-<br/>
-But this means that a request called /index-creation.html would have the same problem.<br/>
-<br/>
-<br/>
+<p>Any link called site.html or site.pdf produce a loop on the search funcionality.<br>
+<br>
+The reason is an internal request called <a href="cocoon://site.lucene">cocoon://site.lucene</a> a work around would be to choose another name for this internal request.<br>
+<br>
+But this means that a request called /index-creation.html would have the same problem.<br>
+<br>
+<br>
</p>
</div>
-<a name="N10137"></a><a name="%5BFOR-203%5D+2nd+level+tabs+are+not+selected+appropriately"></a>
+<a name="N10153"></a><a name="%5BFOR-203%5D+2nd+level+tabs+are+not+selected+appropriately"></a>
<h2 class="underlined_10">[FOR-203] 2nd level tabs are not selected appropriately</h2>
<div class="section">
<p>
<a href="http://issues.apache.org/jira/browse/FOR-203">http://issues.apache.org/jira/browse/FOR-203</a>
</p>
<p>The 2nd level tabs are not shown for menu entries that caused the issue FOR-111. This happens because the starts-with() path comparison fails for menu entries that do not reside the same directory as is specified in the &quot;dir&quot; attribute of the 2nd level tabs.
-<br/>
+<br>
-<br/>
+<br>
See the attached bug-demo.tgz for an example. Select &quot;Samples/Apache document&quot; and notice that the 2nd level tabs are shown. Now select &quot;Samples/BUG DEMO&quot; and notice that the 2nd level tabs are not shown.
-<br/>
+<br>
-<br/>
+<br>
This is because the document corresponding to &quot;Samples/Apache document&quot; resides in the directory &quot;/samples&quot; whereas the document corresponding to &quot;Samples/BUG DEMO&quot; resides in the directory &quot;/bug-sample&quot;.
-<br/>
+<br>
-<br/>
+<br>
Kind regards,
-<br/>
+<br>
&nbsp;&nbsp;Lorenz Froihofer.</p>
</div>
-<a name="N10145"></a><a name="%5BFOR-187%5D+Redefine+project+documentation+dirs"></a>
-<h2 class="underlined_10">[FOR-187] Redefine project documentation dirs</h2>
+<a name="N10161"></a><a name="%5BFOR-200%5D+Locationmap+for+Forrest+and+Users"></a>
+<h2 class="underlined_10">[FOR-200] Locationmap for Forrest and Users</h2>
<div class="section">
<p>
-<a href="http://issues.apache.org/jira/browse/FOR-187">http://issues.apache.org/jira/browse/FOR-187</a>
-</p>
-<p>We should finalize all discussions about where to put sources and extensions in the projects.</p>
-</div>
-<a name="N10153"></a><a name="%5BFOR-184%5D+Switch+to+XHTML2"></a>
-<h2 class="underlined_10">[FOR-184] Switch to XHTML2</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-184">http://issues.apache.org/jira/browse/FOR-184</a>
-</p>
-<p>Switch to using XHTML2 as a base and intermediate format. This means also using RelaxNG validations, new sitemap pipelines, new stylesheets, new input/output for &quot;views&quot;. See the steps in thread: <a href="http://marc.theaimsgroup.com/?t=112512735800002">http://marc.theaimsgroup.com/?t=112512735800002</a></p>
-</div>
-<a name="N10161"></a><a name="%5BFOR-157%5D+skin-descriptors+comma+separated+list+fails"></a>
-<h2 class="underlined_10">[FOR-157] skin-descriptors comma separated list fails</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-157">http://issues.apache.org/jira/browse/FOR-157</a>
-</p>
-<p>The second link does *not* read the url of the skin correctly.<br/>
-<br/>
-I repeated today the steps with a second skin:<br/>
-1) create the skin<br/>
-2) forrest package-skin<br/>
-3) defined it in my descriptor <br/>
-4) checked with &quot;forrest available-skins&quot;<br/>
-5) forrest<br/>
-<br/>
-and it worked :)<br/>
-<br/>
-... dunno why it have not yesterday.<br/>
-<br/>
-Yes I do! I just changed:<br/>
-forrest.skins.descriptors=<a href="http://www.apache.org/~thorsten/whiteboard/forrestskins/skins.xml">http://www.apache.org/~thorsten/whiteboard/forrestskins/skins.xml</a><br/>
-to<br/>
-forrest.skins.descriptors=<a href="http://xml.apache.org/forrest/skins/skins.xml,http://www.apache.org/~thorsten/whiteboard/forrestskins/skins.xml">http://xml.apache.org/forrest/skins/skins.xml,http://www.apache.org/~thorsten/whiteboard/forrestskins/skins.xml</a><br/>
-<br/>
-Trying to say something wrong with the &quot;comma seperated list,&quot;. The second link do *not* work. In detail the url of the skin. <br/>
-<br/>
-I just double checked as well the <a href="file:///d:/get/skins.xml">file:///d:/get/skins.xml</a> and it worked. When it stands alone but not in the comma seperated list.<br/>
+<a href="http://issues.apache.org/jira/browse/FOR-200">http://issues.apache.org/jira/browse/FOR-200</a>
</p>
+<p>The locationmap gives us the ability to specify where sources are, both for Forrest and for the users.
+<br>
+
+<br>
+Beware that it will not work for raw files that are not linked, as this &quot;feature&quot; currently uses a fixed dir being being copied by Ant.</p>
</div>
</div>
<!--+
Modified: forrest/site/forrest-issues.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/forrest-issues.pdf?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/linkmap.html
URL: http://svn.apache.org/viewcvs/forrest/site/linkmap.html?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
--- forrest/site/linkmap.html (original)
+++ forrest/site/linkmap.html Fri Oct 28 00:18:42 2005
@@ -252,286 +252,7 @@
</div>
<a name="N10007"></a><a name="Table+of+Contents"></a>
<h2 class="underlined_10">Table of Contents</h2>
-<div class="section">
-<ul>
-<li>
-<a href="">Forrest</a> _________________________ <em>site</em>
-</li>
-<ul>
-
-
-
-
-<ul>
-<li>
-<a href="">About</a> _________________________ <em>about</em>
-</li>
-<ul>
-
-<ul>
-<li>
-<a href="index.html">Index</a> _________________________ <em>index</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="license.html">License</a> _________________________ <em>license</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="http://forrest.apache.org/mirrors.cgi">Download</a> _________________________ <em>download</em>
-</li>
-</ul>
-
-
-<ul>
-<li>
-<a href="who.html">Who we are</a> _________________________ <em>who</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="events.html">Events</a> _________________________ <em>events</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="flyer.html">Flyer</a> _________________________ <em>flyer</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="live-sites.html">Example sites</a> _________________________ <em>live-sites</em>
-</li>
-</ul>
-
-</ul>
-</ul>
-
-
-<ul>
-<li>
-<a href="">Getting Involved</a> _________________________ <em>getting-involved</em>
-</li>
-<ul>
-
-<ul>
-<li>
-<a href="contrib.html">Contributing</a> _________________________ <em>contrib</em>
-</li>
-<ul>
-
-
-</ul>
-</ul>
-
-<ul>
-<li>
-<a href="http://svn.apache.org/viewcvs.cgi/forrest/trunk/">Browse SVN</a> _________________________ <em>SVN</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="mail-lists.html">Mail lists</a> _________________________ <em>mail-lists</em>
-</li>
-<ul>
-
-
-
-
-</ul>
-</ul>
-
-<ul>
-<li>
-<a href="issues.html">Bugs and Issues</a> _________________________ <em>bugs</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="forrest-issues.html">Open Issues</a> _________________________ <em>forrest-issues</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="gump.html">Gump Integration</a> _________________________ <em>gump-forrest</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="guidelines.html">Project guidelines</a> _________________________ <em>guidelines</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="committed.html">Being committed</a> _________________________ <em>committed</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="forrest-friday.html">ForrestFriday</a> _________________________ <em>forrest-friday</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="zone.html">Zone notes</a> _________________________ <em>zone</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="plan/">Planning notes</a> _________________________ <em>plan</em>
-</li>
-<ul>
-
-<ul>
-<li>
-<a href="plan/index.html">Overview</a> _________________________ <em>overview</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="plan/internal-xhtml.html">Internal XHTML</a> _________________________ <em>internal-xhtml</em>
-</li>
-</ul>
-
-</ul>
-</ul>
-
-</ul>
-</ul>
-
-
-<ul>
-<li>
-<a href="">Proposals</a> _________________________ <em>proposals</em>
-</li>
-<ul>
-
-<ul>
-<li>
-<a href="proposal-asf-forrestbot.html">ASF Forrestbot</a> _________________________ <em>asf-forrestbot</em>
-</li>
-</ul>
-
-</ul>
-</ul>
-
-
-<ul>
-<li>
-<a href="">Related projects</a> _________________________ <em>references</em>
-</li>
-<ul>
-
-<ul>
-<li>
-<a href="http://gump.apache.org/">Apache Gump</a> _________________________ <em>gump</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="http://cocoon.apache.org/">Apache Cocoon</a> _________________________ <em>cocoon</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="http://lenya.apache.org/">Apache Lenya</a> _________________________ <em>lenya</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="http://xml.apache.org/">Apache XML</a> _________________________ <em>xml</em>
-</li>
-</ul>
-
-</ul>
-</ul>
-
-
-
-
-
-
-
-
-
-
-<ul>
-<li>
-<a href="tools/">Tools</a> _________________________ <em>tools</em>
-</li>
-<ul>
-
-<ul>
-<li>
-<a href="tools/index.html">Index</a> _________________________ <em>index</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="tools/forrestbar.html">ForrestBar</a> _________________________ <em>forrestbar</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="tools/forrestbot.html">Forrestbot</a> _________________________ <em>forrestbot</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="tools/forrestbot-web-interface.html">Forrestbot Webapp</a> _________________________ <em>forrestbot-web-interface</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="tools/eclipse.html">Eclipse Plugin</a> _________________________ <em>eclipse</em>
-</li>
-</ul>
-
-<ul>
-<li>
-<a href="tools/xxe.html">XXE-Editor</a> _________________________ <em>xxe</em>
-</li>
-</ul>
-
-</ul>
-</ul>
-
-
-
-
-
-
-
-
-
-
-
-</ul>
-</ul>
-</div>
+<div class="section"></div>
</div>
<!--+
|end content
Modified: forrest/site/linkmap.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/linkmap.pdf?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/mirrors.html
URL: http://svn.apache.org/viewcvs/forrest/site/mirrors.html?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
--- forrest/site/mirrors.html (original)
+++ forrest/site/mirrors.html Fri Oct 28 00:18:42 2005
@@ -194,14 +194,14 @@
</li>
</ul>
</div>
-<a name="N1000A"></a><a name="how"></a>
+<a name="N10010"></a><a name="how"></a>
<h2 class="underlined_10">How to download</h2>
<div class="section">
<p>Use the links below to download a distribution of Apache Forrest from one of our mirrors. It is good practice to <a href="[location]#verify">verify the integrity</a> of the distribution files.</p>
<p>Apache Forrest is distributed as a <span class="codefrag">zip</span> archive (for Windows) and as a <span class="codefrag">tar.gz</span> archive (for UNIX). The contents are the same, the only difference is the line-endings of all text files.</p>
<p>The distribution contains all of the source code, documentation, and resources, together with the pre-built ready-to-run forrest binary.</p>
</div>
-<a name="N1001F"></a><a name="closest"></a>
+<a name="N10025"></a><a name="closest"></a>
<h2 class="underlined_10">Current official release (closest mirror site selected automatically)</h2>
<div class="section">
<p>You are currently using <strong>[preferred]</strong>. If you encounter a problem with this mirror, then please select another. If all mirrors are failing, there are backup mirrors at the end of the list. See <a href="http://www.apache.org/mirrors/">status</a> of mirrors.</p>
@@ -220,17 +220,17 @@
<li>For Windows operating systems: <a href="[preferred]/forrest/apache-forrest-0.7.zip">apache-forrest-0.7.zip</a> [<a href="http://www.apache.org/dist/forrest/apache-forrest-0.7.zip.asc">PGP</a>] [<a href="http://www.apache.org/dist/forrest/apache-forrest-0.7.zip.md5">MD5</a>]</li>
</ul>
</div>
-<a name="N1006A"></a><a name="svn"></a>
+<a name="N10070"></a><a name="svn"></a>
<h2 class="underlined_10">Snapshots of current development and head SVN repository</h2>
<div class="section">
-<p>If you want to use the latest Apache Forrest features, the source code is under version control with Subversion (read how to <a href="build.html">obtain</a> your working copy). There are also compressed source <a href="http://svn.apache.org/snapshots/forrest/">snapshots</a> that are packed every 6 hours.</p>
+<p>If you want to use the latest Apache Forrest features, the source code is under version control with Subversion (read how to <a href="docs_0_80/build.html">obtain</a> your working copy). There are also compressed source <a href="http://svn.apache.org/snapshots/forrest/">snapshots</a> that are packed every 6 hours.</p>
</div>
-<a name="N10079"></a><a name="archive"></a>
+<a name="N1007F"></a><a name="archive"></a>
<h2 class="underlined_10">Archive of old releases</h2>
<div class="section">
<p>Older releases are available in the <a href="http://archive.apache.org/dist/forrest/">archive</a>. Those releases are only provided as historical artefacts. We strongly recommend to not use those releases, but upgrade to the most recent release.</p>
</div>
-<a name="N10084"></a><a name="verify"></a>
+<a name="N1008A"></a><a name="verify"></a>
<h2 class="underlined_10">Verify releases</h2>
<div class="section">
<p>It is essential that you verify the integrity of the downloaded files using the PGP and MD5 signatures. MD5 verification ensures the file was not corrupted during the download process. PGP verification ensures that the file came from a certain person.</p>
Modified: forrest/site/plan/index.html
URL: http://svn.apache.org/viewcvs/forrest/site/plan/index.html?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
--- forrest/site/plan/index.html (original)
+++ forrest/site/plan/index.html Fri Oct 28 00:18:42 2005
@@ -189,9 +189,6 @@
<a href="#overview">Overview</a>
</li>
<li>
-<a href="#ft">ForrestTuesday get together</a>
-</li>
-<li>
<a href="#topics">Ongoing major development topics</a>
</li>
</ul>
@@ -213,18 +210,7 @@
</div>
-<a name="N1001E"></a><a name="ft"></a>
-<h2 class="underlined_10">ForrestTuesday get together</h2>
-<div class="section">
-<p>
- The next <a href="error:site:forrest-tuesday">Forrest Tuesday</a>
- is on 6 September 2005.
- The main topic is "Internal structure is XHTML2".
- </p>
-</div>
-
-
-<a name="N1002C"></a><a name="topics"></a>
+<a name="N1001E"></a><a name="topics"></a>
<h2 class="underlined_10">Ongoing major development topics</h2>
<div class="section">
<p>Some current topics in no particular order.</p>
Modified: forrest/site/plan/index.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/plan/index.pdf?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/skin/menu.js
URL: http://svn.apache.org/viewcvs/forrest/site/skin/menu.js?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
--- forrest/site/skin/menu.js (original)
+++ forrest/site/skin/menu.js Fri Oct 28 00:18:42 2005
@@ -32,19 +32,17 @@
var title = document.getElementById(obj+'Title');
if(obj.indexOf("_selected_")==0&&el.style.display == ""){
- //nicolaken: doesn't work :-(
- //title.style.backgroundImage = "url('images/chapter_open.gif')";
el.style.display = "block";
+ title.className = "pagegroupselected";
}
- if(el.style.display != "block"){
- //nicolaken: doesn't work :-(
- //title.style.backgroundImage = 'url([url]images/chapter_open.gif[/url])';
+ if(el.style.display != "block"){
el.style.display = "block";
- }else{
- //nicolaken: doesn't work :-(
- //title.style.backgroundImage = "url('images/chapter.gif')";
+ title.className = "pagegroupopen";
+ }
+ else{
el.style.display = "none";
+ title.className = "pagegroup";
}
}// end - if(document.getElementById)
}//end - function SwitchMenu(obj)
Modified: forrest/site/tools/eclipse.html
URL: http://svn.apache.org/viewcvs/forrest/site/tools/eclipse.html?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
--- forrest/site/tools/eclipse.html (original)
+++ forrest/site/tools/eclipse.html Fri Oct 28 00:18:42 2005
@@ -503,7 +503,7 @@
</h2>
<div class="section">
<p>
- Once a Forrest Prject has been created the user can access the context menus to modify and build the site.
+ Once a Forrest Project has been created the user can access the context menus to modify and build the site.
</p>
<a name="N1012C"></a><a name="ModifySettings"></a>
<h3 class="underlined_5">
Modified: forrest/site/tools/eclipse.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/tools/eclipse.pdf?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/tools/xxe.html
URL: http://svn.apache.org/viewcvs/forrest/site/tools/xxe.html?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
--- forrest/site/tools/xxe.html (original)
+++ forrest/site/tools/xxe.html Fri Oct 28 00:18:42 2005
@@ -167,6 +167,14 @@
<li>
<a href="#Developer+Instructions">Developer Instructions</a>
</li>
+<li>
+<a href="#History">History</a>
+<ul class="minitoc">
+<li>
+<a href="#1.3">1.3</a>
+</li>
+</ul>
+</li>
</ul>
</div>
@@ -196,7 +204,15 @@
<li>Delete the <span class="codefrag">forrest</span> directory from the XXE application
config directory. (e.g. <span class="codefrag">D:\Program
- Files\XMLmind_XML_Editor\config</span>)</li>
+ Files\XMLmind_XML_Editor\config</span>)
+ <ul>
+
+<li>if you have installed the config in your XXE user directory (see
+ below), this step is not necessary</li>
+
+</ul>
+
+</li>
<li>Install normally</li>
@@ -205,19 +221,27 @@
</div>
-<a name="N1002F"></a><a name="Install"></a>
+<a name="N10035"></a><a name="Install"></a>
<h2 class="underlined_10">Install</h2>
<div class="section">
<ol>
<li>Extract into the XXE application config directory (e.g.
- <span class="codefrag">D:\Program Files\XMLmind_XML_Editor\config</span>)</li>
+ <span class="codefrag">D:\Program Files\XMLmind_XML_Editor\config</span>)<br>
+
+<strong>OR</strong>
+</li>
+
+<li>Extract into your XXE user directory (e.g.
+ <span class="codefrag">~/.xxe/addon/config</span>) (only in version 1.3+ of this config).
+ From version 1.3, this is the recommended installation location, as it
+ permits upgrading XXE without having to reinstall this config</li>
</ol>
</div>
-<a name="N1003F"></a><a name="Developer+Instructions"></a>
+<a name="N1004F"></a><a name="Developer+Instructions"></a>
<h2 class="underlined_10">Developer Instructions</h2>
<div class="section">
<p>To build the configuration:</p>
@@ -242,6 +266,35 @@
Custom Configuration Info</a>
</p>
</div>
+
+
+<a name="N10078"></a><a name="History"></a>
+<h2 class="underlined_10">History</h2>
+<div class="section">
+<a name="N1007E"></a><a name="1.3"></a>
+<h3 class="underlined_5">1.3</h3>
+<ul>
+
+<li>Fixed a bug that prevented this config to work with XXE 3.x
+ (FOR-720)</li>
+
+<li>Fixed a bug that prevented correct loading of the common css
+ stylesheet (FOR-581)</li>
+
+<li>Changed icon references to be installation independent
+ (FOR-581)</li>
+
+<li>Added a Forrest menu, with more robust table manipulation, and for
+ v2 docs some link traversals (both taken from the XXE XHTML config)</li>
+
+<li>Added more entries to the Table button (menu) in the Forrest
+ toolbar, replicating the entries in the Forrest menu</li>
+
+<li>Added a History section to the README and documentation</li>
+
+</ul>
+</div>
+
</div>
<!--+
Modified: forrest/site/tools/xxe.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/tools/xxe.pdf?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/zone.html
URL: http://svn.apache.org/viewcvs/forrest/site/zone.html?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
--- forrest/site/zone.html (original)
+++ forrest/site/zone.html Fri Oct 28 00:18:42 2005
@@ -254,7 +254,17 @@
directories /ft/ and /fts/ are the forrestbot config and results, see below.
</pre>
<p>
- Files here are owned in the group "other" so any one of us can
+
+<strong>test-sources</strong>
+
+</p>
+<pre class="code">
+A place to hold sources for various test sites.
+Normally these would be in the relevant project's SVN.
+Hold them here until building properly.
+</pre>
+<p>
+ All files are owned in the group "other" so any one of us can
edit/update. Make sure that your 'umask' is set properly so that
new files have group write permissions.
See the <a href="#admin-user">notes</a> about user administration.
@@ -268,7 +278,7 @@
</div>
-<a name="N10048"></a><a name="software"></a>
+<a name="N10052"></a><a name="software"></a>
<h2 class="underlined_10">Software</h2>
<div class="section">
<p>
@@ -279,7 +289,7 @@
Various local software is installed in
<span class="codefrag">/export/opt/</span> (not managed with SVN) ...
</p>
-<a name="N1005B"></a><a name="s-forrest"></a>
+<a name="N10065"></a><a name="s-forrest"></a>
<h3 class="underlined_5">Forrest</h3>
<p>
@@ -305,7 +315,6 @@
</p>
<pre class="code">
svn checkout of current release branch, manually updated as needed.
-FIXME: Not yet done.
</pre>
<p>
To manually update -stable or -release do this:
@@ -320,7 +329,7 @@
</div>
-<a name="N10088"></a><a name="fb"></a>
+<a name="N10092"></a><a name="fb"></a>
<h2 class="underlined_10">The forrestbots</h2>
<div class="section">
<p>
@@ -353,11 +362,14 @@
Forrestbot logs are at
$CONFIG/forrestbot-trunk*/logs/
and old ones are cleaned up by the crontab.
+ There is also a log file for each site that forrestbot builds
+ which captures the output of cron (cronout-*.txt).
+ Be sure to verify this logfile after making configuration changes.
</p>
</div>
-<a name="N100A9"></a><a name="admin"></a>
+<a name="N100B3"></a><a name="admin"></a>
<h2 class="underlined_10">Administration</h2>
<div class="section">
<p>
@@ -386,7 +398,7 @@
Also it seems that /var/run/apache2 is wiped out on reboot,
so need to mkdir again.
</p>
-<a name="N100C6"></a><a name="admin-user"></a>
+<a name="N100D0"></a><a name="admin-user"></a>
<h3 class="underlined_5">User administration</h3>
<p>After receiving your account, please be sure to configure it properly.</p>
<p>See some notes at
Modified: forrest/site/zone.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/zone.pdf?rev=329143&r1=329142&r2=329143&view=diff
==============================================================================
Binary files - no diff available.