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/17 11:26:14 UTC
svn commit: r219381 - in /forrest/site: ./ docs_0_70/howto/ docs_0_80/howto/
tools/
Author: crossley
Date: Sun Jul 17 02:26:13 2005
New Revision: 219381
URL: http://svn.apache.org/viewcvs?rev=219381&view=rev
Log:
publish-with-local-forrestbot
Modified:
forrest/site/docs_0_70/howto/howto-view-dsl.html
forrest/site/docs_0_80/howto/howto-view-contracts.html
forrest/site/docs_0_80/howto/howto-view-contracts.pdf
forrest/site/docs_0_80/howto/howto-view-dsl.html
forrest/site/docs_0_80/howto/howto-view-dsl.pdf
forrest/site/docs_0_80/howto/howto-view-install.html
forrest/site/docs_0_80/howto/howto-view-install.pdf
forrest/site/tools/forrestbot.html
forrest/site/tools/forrestbot.pdf
forrest/site/who.html
forrest/site/who.pdf
Modified: forrest/site/docs_0_70/howto/howto-view-dsl.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/howto-view-dsl.html?rev=219381&r1=219380&r2=219381&view=diff
==============================================================================
--- forrest/site/docs_0_70/howto/howto-view-dsl.html (original)
+++ forrest/site/docs_0_70/howto/howto-view-dsl.html Sun Jul 17 02:26:13 2005
@@ -361,7 +361,7 @@
The work started with grouping elements (the ones from skinconf). We used css-contracts that
we added as @attributes e.g. <span class="codefrag"><div id="content-main"/> </span>. That made it
possible to use the same elements in different skins. For the full list refer to the
- <a href="http://svn.apache.org/viewcvs.cgi/*checkout*/forrest/trunk/main/webapp/skins/leather-dev/contracts.inicial.txt">
+ <a href="http://svn.apache.org/repos/asf/forrest/trunk/main/webapp/skins/leather-dev/contracts.initial.txt">
inicial contract list
</a>
Modified: forrest/site/docs_0_80/howto/howto-view-contracts.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-view-contracts.html?rev=219381&r1=219380&r2=219381&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-view-contracts.html (original)
+++ forrest/site/docs_0_80/howto/howto-view-contracts.html Sun Jul 17 02:26:13 2005
@@ -280,7 +280,7 @@
<a href="#Steps">Steps</a>
<ul class="minitoc">
<li>
-<a href="#enhanceMaintainment">Enhance the maintainment</a>
+<a href="#enhanceMaintenance">Enhance the maintenance</a>
</li>
<li>
<a href="#blankContract">Explaining the blank forrest:contract</a>
@@ -309,7 +309,7 @@
<div class="content">
"Views" are new functionality which is still in development phase. That is why it is in the
"whiteboard" section of the Forrest distribution.
-This HowTo is a good start but still needs proof-reading.
+This HowTo is a good start but still needs more work.
</div>
</div>
<p>
@@ -340,7 +340,7 @@
</li>
<li>
- Reading that how-to is as well a good idea to understand the used dir-structure in this how-to.
+ Reading that how-to is as well a good idea to understand the used directory structure in this how-to.
</li>
</ul>
@@ -351,19 +351,19 @@
<div class="frame note">
<div class="label">Note</div>
<div class="content">The following content is from many mails around the topic, this how-to tries to be the
- consolidation of this thread. It is mainly based on the [RT] Why using views -
+ consolidation of this thread. It is mainly based on the thread "[RT] Why using views" -
in comparison with "old fashion" skins - usecase i18n</div>
</div>
<p>
- By working on the i18n integration for "pelt" we crossed again the whys for using views. ;-)
- The maintainment problem was to change the captions of the skin features (contracts) to enable
+ By working on the i18n integration for "pelt" we again encountered the reasons for using views. ;-)
+ The maintenance problem was to change the captions of the skin features (contracts) to enable
support for i18n. The case is that the <span class="codefrag">site2xhtml.xsl</span> has a lot of repeating code.
</p>
<p>
For example the "last-publish"-contract could be found 2 times in the code.
- This is not the only contract that was (is) double in the code. The problem with that is that
- we needed to search the code for each caption and senseless repeat the following
- maintainment step of adding the <i18n:text/>-tags.
+ This is not the only contract that was (is) doubled in the code. The problem with that is that
+ we needed to search the code for each caption and senselessly repeat the following
+ maintenance step of adding the <i18n:text/>-tags.
</p>
<pre class="code">
@@ -374,9 +374,9 @@
+ Published:</i18n:text>&#160;" + document.lastModified);
</pre>
-<a name="N10051"></a><a name="enhanceMaintainment"></a>
-<h3 class="underlined_5">Enhance the maintainment</h3>
-<p>Now we can enhance the maintainment for the future and we give this code snippets
+<a name="N10051"></a><a name="enhanceMaintenance"></a>
+<h3 class="underlined_5">Enhance the maintenance</h3>
+<p>Now we can enhance the maintenance for the future and we give these code snippets
contracts names (based on their functionality). This naming enables us to keep
the contract separate from the position code itself. In xsl you would
simply do:
@@ -395,7 +395,7 @@
</xsl:template>
</pre>
<p>
- This allows us in a next maintainment just change the code of
+ This allows us in a next maintenance to just change the code of
<xsl:template name="siteinfo-last-published"/> and apply it in any position where
it is placed.
</p>
@@ -422,10 +422,12 @@
name="blank" type="nugget">
<!--NOTE:
- When using the blank template as c'n p master just search and replace 'blank' by the {contract-name}!-->
+ When using the blank template as copy-and-paste master,
+ just search and replace 'blank' by the {contract-name}!-->
<description>
- {contract-name} will output {contract-funtion}. This is just a blank contract, it will output *nothing*.
+ {contract-name} will output {contract-funtion}.
+ This is just a blank contract, it will output *nothing*.
</description>
<usage><![CDATA[<forrest:contract name="blank"/>]]></usage>
<forrest:template xmlns:forrest="http://apache.org/forrest/templates/1.0"
@@ -444,8 +446,8 @@
</p>
<div class="frame note">
<div class="label">Note</div>
-<div class="content">This is a <strong>naming convention</strong> that you have
- to always met. All @name has to be file name of the contract without file extension!
+<div class="content">This is a <strong>naming convention</strong> that you need
+ to always meet. All @name attributes must be the file name of the contract without file extension.
</div>
</div>
<p>
@@ -468,19 +470,19 @@
<span class="codefrag"><forrest:template name="blank" body="false" head="false"> </span>
That leads to the template attribute @body="true" and
@head="false". In xhtml a contract can add content to the <body/> or/and
- <head/> part of <html/>. This values have to be change when adding an actual template.
- Besides this a xsl-template has to indicate this in the naming. A template that add content to the
- html body has to end with "<span class="codefrag">-body</span>"!!!
+ <head/> part of <html/>. These values need to be changed when adding an actual template.
+ Besides this, a xsl-template needs to indicate this in the naming. A template that adds content to the
+ html body needs to end with "<span class="codefrag">-body</span>"!!!
</p>
<div class="frame note">
<div class="label">Note</div>
<div class="content">
- It is possible to use contracts in different in/output-formats.
- We are focusing for now on format="xhtml" as ouput and the inputFormat="xsl".
+ It is possible to use contracts in different in/output formats.
+ We are focussing for now on format="xhtml" as output and the inputFormat="xsl".
</div>
</div>
<p>
- A <forrest:template /> has the son <xsl:stylesheet/> where we can create
+ A <forrest:template /> has the child <xsl:stylesheet/> where we can create
templates for the html-head and html-body. For adding content into the body of the final
document change @body="true" and add:
</p>
@@ -497,15 +499,15 @@
<div class="label">Fixme (thorsten)</div>
<div class="content">
We need to explain basic naming convention for contracts. Like
- "naming do not say about layout position but functionality of the contract.".
+ "naming does not say anything about layout position, but functionality of the contract.".
</div>
</div>
<p>
- Now lets pick up the example we started with and create a "siteinfo-last-published-howto" contract.
+ Now let us pick up the example we started with and create a "siteinfo-last-published-howto" contract.
Save the blank.ft to <span class="codefrag">{project.home}/src/documentation/resources/templates/siteinfo-last-published-howto.ft</span>.
</p>
<p>
- Now the maintainment optimized code (xpath="/html/body/*") was:
+ Now the maintenance-optimized code (xpath="/html/body/*") was:
</p>
<pre class="code">
<xsl:template name="siteinfo-last-published">
@@ -542,7 +544,7 @@
<li>Set @body="true"</li>
-<li>Copy the maintainment optimized code to the contract.</li>
+<li>Copy the maintenance optimized code to the contract.</li>
</ul>
<p>
Modified: forrest/site/docs_0_80/howto/howto-view-contracts.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-view-contracts.pdf?rev=219381&r1=219380&r2=219381&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/docs_0_80/howto/howto-view-dsl.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-view-dsl.html?rev=219381&r1=219380&r2=219381&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-view-dsl.html (original)
+++ forrest/site/docs_0_80/howto/howto-view-dsl.html Sun Jul 17 02:26:13 2005
@@ -261,7 +261,7 @@
<h1>How to use the forrest:view config-DSL</h1>
<div class="abstract">
This How-To describes the usage of the forrest:view config Domain Specific Language
- to create beautiful website in no time.
+ to create beautiful websites in no time.
</div>
<div id="motd-area">
This is documentation for development version v0.8
@@ -321,8 +321,8 @@
<h2 class="underlined_10">Purpose</h2>
<div class="section">
<p>
- This how-to will show you how to write a<strong> forrest:view</strong> from ground on.
- We will focus on html as output format. As well it will show how to add your own css implementation to the view.
+ This how-to will show you how to write a <strong>forrest:view</strong> from the ground up.
+ We will focus on html as the output format. As well it will show how to add your own css implementation to the view.
</p>
</div>
<a name="N10026"></a><a name="Prerequisites"></a>
@@ -331,15 +331,15 @@
<ul>
<li>
- You have a ready-to-go new seed (newSeed) based on views like described in <a href="../../docs_0_80/howto/howto-view-install.html">Install views</a>.
+ You have a ready-to-go new seed (newSeed) based on views as described in <a href="../../docs_0_80/howto/howto-view-install.html">Install views</a>.
</li>
<li>
- This includes as well all additional plugins that are mentioned in <a href="../../docs_0_80/howto/howto-view-install.html">Install views</a>.
+ This includes as well as all additional plugins that are mentioned in <a href="../../docs_0_80/howto/howto-view-install.html">Install views</a>.
</li>
<li>
- Reading that how-to is as well a good idea to understand the used dir-structure in this how-to.
+ Reading that how-to is as well a good idea to understand the used directory structure in this how-to.
</li>
</ul>
@@ -355,44 +355,44 @@
</div>
</div>
<p>
- We developed<strong> forrest:view</strong> to let the user decide where to place elements in e.g. html-pages.
+ We developed<strong> forrest:view</strong> to let the user decide where to place elements in e.g. html pages.
We started this work with the <span class="codefrag">skinconf.xml</span> where you could configure certain elements and
- their positions. This elements was known under certain names. It was up to the skin-designer to support
+ their positions. These elements were known under certain names. It was up to the skin designer to support
this configuration and the elements.
</p>
<p>
The work started with grouping elements (the ones from skinconf). We used css-contracts that
we added as @attributes e.g. <span class="codefrag"><div id="content-main"/> </span>. That made it
possible to use the same elements in different skins. For the full list refer to the
- <a href="http://svn.apache.org/viewcvs.cgi/*checkout*/forrest/trunk/main/webapp/skins/leather-dev/contracts.inicial.txt">
- inicial contract list
+ <a href="http://svn.apache.org/repos/asf/forrest/trunk/main/webapp/skins/leather-dev/contracts.initial.txt">
+ initial contract list
</a>
</p>
<p>
- Around this contracts we developed a configuration Domain Specific Language and called it<strong> forrest:view</strong> .
- <strong> forrest:view</strong> 's allows us to define the order in which <strong>forrest:contract</strong>'s appear, and also to group
- them using <strong>forrest:hook</strong>'s.
+ Around this contracts we developed a configuration Domain Specific Language and called it<strong>forrest:view</strong>.
+ These <strong>forrest:view</strong>s allows us to define the order in which <strong>forrest:contract</strong>s appear, and also to group
+ them using <strong>forrest:hook</strong>s.
</p>
<p>
-<strong>forrest:hook</strong>'s are container that are only used for layout reasons. They <strong>do not</strong> add
- any content nor functionality to the output. They add <strong>only</strong> layout information to
+<strong>forrest:hook</strong>s are containers that are only used for layout reasons. They <strong>do not</strong> add
+ any content or functionality to the output. They add <strong>only</strong> layout information to
the output. Actually a <span class="codefrag"><forrest:hook name="layoutId"/></span> will be transformed
to <span class="codefrag"><div id="layoutId"/> </span>
</p>
<p>
-<strong>forrest:contract</strong>'s are functionality or extra content that a skin can use to display the requested
+<strong>forrest:contract</strong>s are functionality or extra content that a skin can use to display the requested
document (content-main). Sometimes a contract delivers <strong>format-specific markup</strong>, other times it delivers
a <strong>format-independent string</strong>.
</p>
<a name="N10089"></a><a name="emptyView"></a>
<h3 class="underlined_5">Empty view file</h3>
-<pre class="code"><forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" >
- <forrest:view type="xhtml">
- </forrest:view>
+<pre class="code"><forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0">
+ <forrest:view type="xhtml">
+ </forrest:view>
</forrest:views>
</pre>
<p>
@@ -401,7 +401,7 @@
The only format we implemented is xhtml for now. This is as well true for the delivered contracts.
</p>
<p>
- Now lets start to skin our site. :)
+ Now let us start to skin our site.
</p>
<a name="N100A0"></a><a name="firstView"></a>
<h3 class="underlined_5">Creating your first view</h3>
@@ -417,29 +417,29 @@
</p>
<p>
Let use the blank view from the earlier step and add the content-main contract. In
- ls.contracts.html we find the information how to use the contract in our view. Our
+ ls.contracts.html we find the information for how to use the contract in our view. Our
<span class="codefrag">index.fv</span> should look like:
</p>
-<pre class="code"><forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" >
- <forrest:view type="xhtml">
+<pre class="code"><forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0">
+ <forrest:view type="xhtml">
<forrest:contract name="content-main"/>
- </forrest:view>
+ </forrest:view>
</forrest:views>
</pre>
<p>
- Let's try our new view by pointing to <span class="codefrag">http://localhost:8888/index.html</span>.
- We will see only the main content. :) Now let's add the section navigation to our view.
+ Lets try our new view by pointing to <span class="codefrag">http://localhost:8888/index.html</span>.
+ We will see only the main content. Now let us add the section navigation to our view.
The contract usage in the view can be looked up in ls.contracts.html. Our view now looks like:
</p>
-<pre class="code"><forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" >
- <forrest:view type="xhtml">
+<pre class="code"><forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0">
+ <forrest:view type="xhtml">
<forrest:contract name="content-main"/>
<forrest:contract name="nav-section"/>
- </forrest:view>
+ </forrest:view>
</forrest:views>
</pre>
<p>
- We find now the main content and the section navigation after each other and in the order
+ We now find the main content and the section navigation after each other and in the order
we placed them in the view, but we want it next to each other
(left: nav-section; right: content-main).
</p>
@@ -448,7 +448,7 @@
<p>
We will use now the first time a <span class="codefrag"><forrest:hook name="layoutId"/></span>.
Hooks are the styling side of views. We can imitate arbitrary html skeleton
- with their help. Before we explain how to use your own css in views we will use the default css.
+ with their help. Before we explain how to use your own css in views, we will use the default css.
In the default.css we can find
</p>
<pre class="code">/* menu */
@@ -464,7 +464,7 @@
and add contracts into that container.
</p>
<p>
- If we want to put the nav-section contract into the left side position
+ If we want to put the nav-section contract into the left-hand side position
of the site we need to place the contract into that hook. Like:
</p>
<pre class="code"><forrest:hook name="leftbar">
@@ -486,7 +486,7 @@
<a name="N100F6"></a><a name="cssView"></a>
<h3 class="underlined_5">CSS in views</h3>
<p>
- We know now how to place contracts and hooks in our view, till this stage we only used the default.css.
+ We now know how to place contracts and hooks in our view. Until this stage we only used the default.css.
CSS-support of views is as easy as placing contracts/hooks. To override the default.css
stylesheet we use another tag within our view <span class="codefrag"><forrest:css url="default.css"/></span>.
</p>
@@ -512,9 +512,10 @@
<div class="label">Note</div>
<div class="content">
-<span class="codefrag"><forrest:css url="howTo.css"/></span> has to be direct son of
- <span class="codefrag"><forrest:view type="xhtml"></span>!!!
- </div>
+<span class="codefrag"><forrest:css url="howTo.css"/></span> needs to be the direct child of
+ <span class="codefrag"><forrest:view type="xhtml"></span>
+
+</div>
</div>
<pre class="code"><forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" >
<forrest:view type="xhtml">
@@ -527,8 +528,8 @@
</forrest:views>
</pre>
<p>
- Now you see a white page where the menu is sourrounded by a solid border with the defined background.
- As second example let us change as well the content-main by adding another hook
+ Now you see a white page where the menu is surrounded by a solid border with the defined background.
+ As a second example, let us change as well the content-main by adding another hook
<span class="codefrag"><forrest:hook name="content"/></span> We need to add the new layout container
to our howTo.css:
</p>
@@ -541,7 +542,8 @@
}
</pre>
<p>
- Then we have to add the 'content-main' contract to the 'content' hook, the resulting view looks like:
+ Then we have to add the 'content-main' contract to the 'content' hook.
+ The resulting view looks like:
</p>
<pre class="code"><forrest:views xmlns:forrest="http://apache.org/forrest/templates/1.0" >
<forrest:view type="xhtml">
@@ -556,7 +558,7 @@
</forrest:views>
</pre>
<p>
- We are now able to place contracts into layout container and add custom css to the view.
+ We are now able to place contracts into the layout container and add custom css to the view.
</p>
<div class="frame fixme">
<div class="label">Fixme (thorsten)</div>
@@ -571,7 +573,7 @@
<div class="section">
<p>
Congratulations you are now able to work with the view DSL.
- From here we recommend to read the following How-To's:
+ From here we recommend to read the following How-Tos:
</p>
<ul>
Modified: forrest/site/docs_0_80/howto/howto-view-dsl.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-view-dsl.pdf?rev=219381&r1=219380&r2=219381&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/docs_0_80/howto/howto-view-install.html
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-view-install.html?rev=219381&r1=219380&r2=219381&view=diff
==============================================================================
--- forrest/site/docs_0_80/howto/howto-view-install.html (original)
+++ forrest/site/docs_0_80/howto/howto-view-install.html Sun Jul 17 02:26:13 2005
@@ -312,7 +312,7 @@
<div class="content">
"Views" are new functionality which is still in development phase. That is why it is in the
"whiteboard" section of the Forrest distribution.
-This HowTo is a good start but still needs proof-reading.
+This HowTo is a good start but still needs more work.
</div>
</div>
<p>
@@ -333,17 +333,20 @@
<ul>
<li>You have to use the trunk version of forrest for using views because it is in an early stage</li>
+
+<li>Read <a href="../../docs_0_80/howto/howto-buildPlugin.html">How to Build a Plugin</a>
+ especially the section about using Forrest's own Ant.</li>
</ul>
</div>
-<a name="N1002E"></a><a name="Steps"></a>
+<a name="N10035"></a><a name="Steps"></a>
<h2 class="underlined_10">Steps</h2>
<div class="section">
<p>
The process of setting up the plugin is quite heavy. We promise it will be easier in the future.
Some of the instructions has to be modified with your local settings.
</p>
-<a name="N10036"></a><a name="localBuild"></a>
+<a name="N1003D"></a><a name="localBuild"></a>
<h3 class="underlined_5">Build the view and the viewHelper plugins</h3>
<p>
The first step is to build the view and the viewHelper plugins. Change to a console of your choice
@@ -358,57 +361,57 @@
cd ../org.apache.forrest.plugin.output.viewHelper.xhtml/
ant local-deploy
</pre>
-<a name="N10044"></a><a name="newSeed"></a>
+<a name="N1004B"></a><a name="newSeed"></a>
<h3 class="underlined_5">Seed a new project</h3>
<p>
- Go to the dir where you want to seed a new project and seed it.
+ Go to the directory where you want to seed a new project and seed it.
</p>
<pre class="code">
cd ~/src/newSeed
forrest seed
</pre>
-<a name="N10052"></a><a name="forrestProperties"></a>
+<a name="N10059"></a><a name="forrestProperties"></a>
<h3 class="underlined_5">Modifying forrest.properties</h3>
<p>
- Now we have to tell forrest that we are planing to use the view plugins. We will do that
- by editing to the forrest.properties to add the plugins:
+ Now we have to tell forrest that we are planning to use the view plugins. We will do that
+ by editing the forrest.properties to add the plugins:
</p>
<pre class="code">
project.required.plugins=org.apache.forrest.plugin.output.viewHelper.xhtml,org.apache.forrest.plugin.internal.view
</pre>
<p>
Now we have to change the project skin to leather-dev. The reason is that the plugins are still
- not independend form the "old fashion skins".
+ not independent from the "old fashion skins".
</p>
<div class="frame note">
<div class="label">Note</div>
-<div class="content">We exchanging only
- site2xhtml.xsl of leather-dev skin by the plugins and some contracts are based
+<div class="content">We are exchanging only
+ site2xhtml.xsl of leather-dev skin with the plugins, and some contracts are based
on e.g. document2html.xsl output of leather-dev.</div>
</div>
<pre class="code">
project.skin=leather-dev
</pre>
-<a name="N1006A"></a><a name="testing"></a>
+<a name="N10071"></a><a name="testing"></a>
<h3 class="underlined_5">Test your new view based project</h3>
<p>
- Now you have finished the preparation and the setup to finally try
+ Now you have finished the preparation and the setup to finally do
</p>
<pre class="code">
forrest run
</pre>
<p>then point to <a href="http://localhost:8888/">http://localhost:8888/</a> and you should see the default
- view based skin.</p>
+ view-based skin.</p>
<div class="frame note">
<div class="label">Note</div>
-<div class="content">When developing styles with views 'forrest run' is the quickest
-way. You will see you do not have to build your project to see the
+<div class="content">When developing styles with views, 'forrest run' is the quickest
+way. You will see that you do not have to build your project to see the
changes on your pages when working with *.fv. </div>
</div>
-<a name="N10082"></a><a name="availableContracts"></a>
+<a name="N10089"></a><a name="availableContracts"></a>
<h3 class="underlined_5">Available contracts</h3>
<p>
- To start working with views you need to know which contracts you can use.
+ To start working with views, you need to know which contracts you can use.
For this we will install another plugin <span class="codefrag">org.apache.forrest.plugin.input.viewHelper.xhtml.ls</span>.
The setup is:
</p>
@@ -419,10 +422,10 @@
ant local-deploy
</pre>
<p>
- The newly installed plugin will show the available contracts as html page.
- First we have to tell forrest that we are planing to use the new plugin. We will do that
+ The newly installed plugin will show the available contracts as html pages.
+ First we have to tell forrest that we are planning to use the new plugin. We will do that
by editing the forrest.properties of the <a href="../../docs_0_80/howto/howto-view-install.html">newSeed</a>
- to <strong>add</strong> the plugin:
+ to add the plugin:
</p>
<pre class="code">
project.required.plugins=org.apache.forrest.plugin.input.viewHelper.xhtml.ls
@@ -432,7 +435,7 @@
On this page you will find all contracts that you can use in your project.
</p>
</div>
-<a name="N100A7"></a><a name="Further Reading"></a>
+<a name="N100AB"></a><a name="Further Reading"></a>
<h2 class="underlined_10">Further Reading</h2>
<div class="section">
<p>
@@ -451,7 +454,7 @@
</ul>
</div>
-<a name="N100BE"></a><a name="Feedback"></a>
+<a name="N100C2"></a><a name="Feedback"></a>
<h2 class="underlined_10">Feedback</h2>
<div class="section">
<p>
Modified: forrest/site/docs_0_80/howto/howto-view-install.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/docs_0_80/howto/howto-view-install.pdf?rev=219381&r1=219380&r2=219381&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/tools/forrestbot.html
URL: http://svn.apache.org/viewcvs/forrest/site/tools/forrestbot.html?rev=219381&r1=219380&r2=219381&view=diff
==============================================================================
--- forrest/site/tools/forrestbot.html (original)
+++ forrest/site/tools/forrestbot.html Sun Jul 17 02:26:13 2005
@@ -151,6 +151,9 @@
<a href="#deploy.svn">deploy.svn</a>
</li>
<li>
+<a href="#deploy.ftp">deploy.ftp</a>
+</li>
+<li>
<a href="#notify">notify</a>
</li>
<li>
@@ -334,6 +337,10 @@
<li>
<a href="#deploy.svn">deploy.svn</a>
</li>
+
+<li>
+<a href="#deploy.ftp">deploy.ftp</a>
+</li>
</ul>
</td>
@@ -374,7 +381,7 @@
default?</div>
</div>
<p></p>
-<a name="N100D9"></a><a name="Workstage+Properties"></a>
+<a name="N100DE"></a><a name="Workstage+Properties"></a>
<h3 class="underlined_5">Workstage Properties</h3>
<p>Each workstage implementation is configurable with properties. The
following tables describe each property and whether or not you are
@@ -386,7 +393,7 @@
my-settings.xml) that just sets those properties (don't include it in
CVS/SVN). Then in your project buildfile, have <span class="codefrag"><import
file="my-settings.xml"/></span>.</p>
-<a name="N100E8"></a><a name="Misc+Properties"></a>
+<a name="N100ED"></a><a name="Misc+Properties"></a>
<h4>Misc Properties</h4>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -417,13 +424,13 @@
</tr>
</table>
-<a name="N1011F"></a><a name="getsrc.clean-workdir"></a>
+<a name="N10124"></a><a name="getsrc.clean-workdir"></a>
<h4>getsrc.clean-workdir</h4>
<p>This should be executed before a getsrc implementation is executed.
For example, <span class="codefrag"><target name="getsrc"
depends="getsrc.clean-workdir, getsrc.svn"/></span>
</p>
-<a name="N1012B"></a><a name="getsrc.local"></a>
+<a name="N10130"></a><a name="getsrc.local"></a>
<h4>getsrc.local</h4>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -455,7 +462,7 @@
</tr>
</table>
-<a name="N10168"></a><a name="getsrc.cvs"></a>
+<a name="N1016D"></a><a name="getsrc.cvs"></a>
<h4>getsrc.cvs</h4>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -551,7 +558,7 @@
</tr>
</table>
-<a name="N10210"></a><a name="getsrc.svn"></a>
+<a name="N10215"></a><a name="getsrc.svn"></a>
<h4>getsrc.svn</h4>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -595,7 +602,7 @@
</tr>
</table>
-<a name="N1025E"></a><a name="build.forrest"></a>
+<a name="N10263"></a><a name="build.forrest"></a>
<h4>build.forrest</h4>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -638,7 +645,7 @@
</tr>
</table>
-<a name="N102AD"></a><a name="deploy.local"></a>
+<a name="N102B2"></a><a name="deploy.local"></a>
<h4>deploy.local</h4>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -670,7 +677,7 @@
</tr>
</table>
-<a name="N102E5"></a><a name="deploy.scp"></a>
+<a name="N102EA"></a><a name="deploy.scp"></a>
<h4>deploy.scp</h4>
<p>${user.home}/.ssh/known_hosts must properly recognize the host, so
you should manually make an ssh connection to the host if you never
@@ -717,7 +724,7 @@
</tr>
</table>
-<a name="N10335"></a><a name="deploy.cvs"></a>
+<a name="N1033A"></a><a name="deploy.cvs"></a>
<h4>deploy.cvs</h4>
<p>This is only available on *nix operating systems.</p>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -814,7 +821,7 @@
</tr>
</table>
-<a name="N103E1"></a><a name="deploy.svn"></a>
+<a name="N103E6"></a><a name="deploy.svn"></a>
<h4>deploy.svn</h4>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -884,7 +891,77 @@
</tr>
</table>
-<a name="N1045B"></a><a name="notify"></a>
+<a name="N10460"></a><a name="deploy.ftp"></a>
+<h4>deploy.ftp</h4>
+<table class="ForrestTable" cellspacing="1" cellpadding="4">
+
+<tr>
+
+<th colspan="1" rowspan="1">Property</th>
+
+ <th colspan="1" rowspan="1">Description</th>
+
+ <th colspan="1" rowspan="1">Default Value</th>
+
+ <th colspan="1" rowspan="1">Required?</th>
+
+</tr>
+
+
+<tr>
+
+<td colspan="1" rowspan="1">deploy.ftp.server</td>
+
+ <td colspan="1" rowspan="1">FTP server to upload files to</td>
+
+ <td colspan="1" rowspan="1">localhost</td>
+
+ <td colspan="1" rowspan="1">No</td>
+
+</tr>
+
+
+<tr>
+
+<td colspan="1" rowspan="1">deploy.ftp.user</td>
+
+ <td colspan="1" rowspan="1">FTP username to use for authenticating with the server</td>
+
+ <td colspan="1" rowspan="1">anonymous</td>
+
+ <td colspan="1" rowspan="1">No</td>
+
+</tr>
+
+
+<tr>
+
+<td colspan="1" rowspan="1">deploy.ftp.password</td>
+
+ <td colspan="1" rowspan="1">Password for the FTP user</td>
+
+ <td colspan="1" rowspan="1">forrestbot@</td>
+
+ <td colspan="1" rowspan="1">No</td>
+
+</tr>
+
+
+<tr>
+
+<td colspan="1" rowspan="1">deploy.ftp.remotedir</td>
+
+ <td colspan="1" rowspan="1">The directory to upload to (this can be an absolute path or
+ relative to the FTP user's default directory)</td>
+
+ <td colspan="1" rowspan="1">incoming</td>
+
+ <td colspan="1" rowspan="1">No</td>
+
+</tr>
+
+</table>
+<a name="N104DD"></a><a name="notify"></a>
<h4>notify</h4>
<p>These settings are used by all notify implementations.</p>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -982,10 +1059,10 @@
</tr>
</table>
-<a name="N10505"></a><a name="notify.local"></a>
+<a name="N10587"></a><a name="notify.local"></a>
<h4>notify.local</h4>
<p>No properties.</p>
-<a name="N1050F"></a><a name="notify.email"></a>
+<a name="N10591"></a><a name="notify.email"></a>
<h4>notify.email</h4>
<table class="ForrestTable" cellspacing="1" cellpadding="4">
@@ -1044,7 +1121,7 @@
</div>
-<a name="N10577"></a><a name="Forrestbot+design"></a>
+<a name="N105F9"></a><a name="Forrestbot+design"></a>
<h2 class="underlined_10">Forrestbot design</h2>
<div class="section">
<p>Forrest and forrestbot use ant buildfiles extensively. Ant 1.6's import
Modified: forrest/site/tools/forrestbot.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/tools/forrestbot.pdf?rev=219381&r1=219380&r2=219381&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/who.html
URL: http://svn.apache.org/viewcvs/forrest/site/who.html?rev=219381&r1=219380&r2=219381&view=diff
==============================================================================
--- forrest/site/who.html (original)
+++ forrest/site/who.html Sun Jul 17 02:26:13 2005
@@ -195,11 +195,15 @@
<li>
<strong>[FSO] - Ferdinand Soethe (ferdinand.at.apache.org)</strong>
</li>
+
+<li>
+<strong>[DG] - Diwaker Gupta (diwaker.at.apache.org)</strong>
+</li>
</ul>
</div>
-<a name="N10049"></a><a name="inactive"></a>
+<a name="N1004D"></a><a name="inactive"></a>
<h2 class="underlined_10">Inactive Committers</h2>
<div class="section">
<ul>
@@ -225,7 +229,7 @@
</ul>
</div>
-<a name="N1006C"></a><a name="notes"></a>
+<a name="N10070"></a><a name="notes"></a>
<h2 class="underlined_10">Notes</h2>
<div class="section">
<p>Strong type denotes <strong>PMC member</strong>
Modified: forrest/site/who.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/who.pdf?rev=219381&r1=219380&r2=219381&view=diff
==============================================================================
Binary files - no diff available.