Added: forrest/site/docs_0_70/howto/howto-pdf-tab.source.xml
URL:
http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/howto-pdf-tab.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/docs_0_70/howto/howto-pdf-tab.source.xml (added)
+++ forrest/site/docs_0_70/howto/howto-pdf-tab.source.xml Wed Feb 8 16:26:20
2006
@@ -0,0 +1,213 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+ Copyright 2002-2005 The Apache Software Foundation or its licensors,
+ as applicable.
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+--><document><header>
+ <title>How to create a PDF document for each tab</title>
+ <abstract>This How-To describes the generation of a PDF document for each
+ group of documents that is defined by a tab.
+ </abstract>
+ <last-modified-content-date date="2005-07-19"/>
+ </header><body><section id="Intended Audience"><title>Intended
Audience</title>
+ <p>
+ Users who need to generate one printable document aggregated from a
+ group of documents.
+ </p>
+ </section><section id="Purpose"><title>Purpose</title>
+ <p>
+ By default Forrest generates a pdf file for each separate document of
+ your project.
+ As well you can create a pdf of the whole site. But sometimes it may
+ be necessary to generate a pdf file out of selected tab, i.e. only for
+ certain parts of the site.
+ </p>
+ </section><section id="Prerequisites"><title>Prerequisites</title>
+ <ul>
+ <li>Understand how to create project-specific sitemaps by following the
+ <link href="site:v0.70//your-project">Using Forrest</link> document.</li>
+ </ul>
+ </section><section id="Steps"><title>Steps</title>
+ <p>The procedure outlined below will define a project
+ <code>sitemap.xmap</code> and create a new
+ <code>pdf-tab.xmap</code>.
+ </p>
+ <section id="sitemap">
+ <title>Create your project's main sitemap.xmap</title>
+ <p>
+ If you do not have already a sitemap then create a new empty one in your
+ <code>src/documentation</code> directory (or wherever
+ ${project.sitemap-dir} points to).
+ </p>
+ </section>
+
+ <section id="aggregator">
+ <title>Create another sitemap: pdf-tab.xmap</title>
+ <p>
+ Like before create an empty sitemap and name it pdf-tab.xmap.
+ </p>
+ </section>
+
+ <section id="mount">
+ <title>Edit project sitemap.xmap to mount pdf-tab.xmap</title>
+ <p>
+ Your sitemap should look something like this.
+ </p>
+ <source xml:space="preserve">
+<map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
+ <map:pipelines>
+ <map:pipeline internal-only="false">
+ <map:match pattern="**.xml">
+ <!-- pdf-tab definitions -->
+ <map:match pattern="pdf-tab.xml">
+ <map:mount uri-prefix="" src="pdf-tab.xmap"
+ check-reload="yes" />
+ </map:match>
+ <!-- end of pdf-tab definitions -->
+ </map:match>
+ </map:pipeline>
+ </map:pipelines>
+</map:sitemap>
+ </source>
+ </section>
+
+ <section id="edit-aggregator">
+ <title>Edit the file <code>pdf-tab.xmap</code></title>
+ <p>
+ The <code><map:match pattern="*.xml"></code> element
+ should look like the following:
+ </p>
+ <source xml:space="preserve">
+<map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
+ <map:pipelines>
+ <map:pipeline internal-only="false">
+ <map:match pattern="*.xml">
+ <map:generate src="cocoon://abs-linkmap"/>
+ <map:transform type="xpath">
+ <map:parameter name="include" value="//[EMAIL
PROTECTED]'true']"/>
+ <map:parameter name="exclude" value="//[EMAIL
PROTECTED]'false']"/>
+ </map:transform>
+ <map:transform src="resources/stylesheets/site2book.xsl" />
+ <map:transform
src="resources/stylesheets/aggregates/book2cinclude.xsl">
+ <map:parameter name="title"
+ value="{conf:project-name}: Still My Foo Site"/>
+ </map:transform>
+ <map:transform type="cinclude"/>
+ <map:transform
src="resources/stylesheets/aggregates/doc2doc-uniqueids.xsl"/>
+ <map:transform
src="resources/stylesheets/aggregates/docs2document.xsl"/>
+ <map:serialize type="xml"/>
+ </map:match>
+ </map:pipeline>
+ </map:pipelines>
+</map:sitemap>
+ </source>
+ </section>
+ <section id="edit-site">
+ <title>Edit your site.xml</title>
+ <note>
+ Do not use directories with "." in it. Replace them by "_"
+ e.g 1.2/ will not work in the aggregation. e.g. 1_2/ just works fine.
+ </note>
+ <p>
+ Add the following entry to your site.xml in the
+ <code><about></code> element
+ </p>
+ <source xml:space="preserve">...
+<whole_foosite href="pdf-tab.html" label="sub site" />
+ </source>
+ <p>
+ Your site.xml should look like this ...
+ </p>
+ <source xml:space="preserve">...
+<about label="About">
+ <index label="Index" href="index.html" description="Welcome to
MyProj"/>
+ <changes label="Changes" href="changes.html"
+ description="History of Changes" />
+ <todo label="Todo" href="todo.html" description="Todo List" />
+ <whole_foosite href="pdf-tab.html" label="pdf-tab" />
+</about>
+...
+ </source>
+ <p>
+ This allows you to link to it via a
+ <code><link href="site:whole_foosite"></code>
+ reference.
+ </p>
+ <p>Add to every element that should be included in the pdf-tab.pdf
+ the attribute <code>wholesite="true"</code></p>
+ <source xml:space="preserve">
+<sample-wiki label="Wiki page" href="wiki-sample.html"
+ description="wiki-sample" wholesite="true"/>
+ </source>
+ <note>This attribute will be inherited by all children of the
element.
+ Do not use it in the parent element that contains the
+ <code><whole_foosite href="pdf-tab.html" label="pdf-tab"
/></code>
+ as the child (will cause a <code>stack overflow</code> if you do)!!!
+ </note>
+ </section>
+ <section id="explain">
+ <title>Explanation of the operation</title>
+ <p>
+ Line 4 of our example
+ <br/>
+ <code><map:parameter name="include" value="//[EMAIL
PROTECTED]'true']"/></code>
+ looks at your site.xml and will match every element containing the
+ <code>wholesite="true"</code> attribute. For example, to use the
"samples"
+ tab ...
+ </p>
+ <source xml:space="preserve">
+...
+<samples label="Samples" href="samples/" tab="samples" wholesite="true">
+...
+</samples>
+...
+ </source>
+ <p>
+ It matches <strong>all</strong> of the elements that contain
+ <code>wholesite="true"</code>
+ (in our example <code><samples></code>
+ and its "children") for the content of the pdf file to be generated.
+ </p>
+ <source xml:space="preserve">
+<samples label="Samples" href="samples/" tab="samples" wholesite="true">
+ <sample2 label="Static content" href="sample2.html"
+ description="More Samples" wholesite='false'/>
+ <sample-wiki label="Wiki page" href="wiki-sample.html"
+ description="wiki-sample" />
+ <sample-ihtml label="ihtml page" href="ihtml-sample.html"
+ description="Test iHTML page" />
+</samples>
+ </source>
+ <p>
+ This example shows that you can as well exclude site(s) from the
aggregation
+ by using the <code>wholesite="false"</code> attribute. This attribute
will be as well inherited
+ by all children of the element.
+ </p>
+ <p>
+ Line 8 defines the title of the pdf file by taking the content
+ of the project-name variable in
+ <code>skinconf.xml</code> and adding some funny text:
+ <br/>
+ <code><map:parameter name="title" value="{conf:project-name}: Still
My Foo Site"/></code>
+ </p>
+ </section>
+ </section><section id="Feedback and further development of this
How-To"><title>Feedback and further development of this How-To</title>
+ <p>
+ Please provide feedback about this document via the
+ <link href="site:mail-lists">mailing lists</link>.
+ </p>
+ <p>
+ In the future, this ability will probably be incorporated into the
+ main Forrest process.
+ </p>
+ </section></body></document>
\ No newline at end of file
Propchange: forrest/site/docs_0_70/howto/howto-pdf-tab.source.xml
------------------------------------------------------------------------------
svn:eol-style = native
Added: forrest/site/docs_0_70/howto/howto-view-contracts.source.xml
URL:
http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/howto-view-contracts.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/docs_0_70/howto/howto-view-contracts.source.xml (added)
+++ forrest/site/docs_0_70/howto/howto-view-contracts.source.xml Wed Feb 8
16:26:20 2006
@@ -0,0 +1,276 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+ Copyright 2002-2005 The Apache Software Foundation or its licensors,
+ as applicable.
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+--><document><header>
+ <title>How to write a forrest:contract?</title>
+ <abstract>
+ This How-To will explain how we wrote the contracts for views and hope
afterwards you will be able to do the same.
+ </abstract>
+ <last-modified-content-date date="2005-06-06"/>
+ </header><body><section id="Intended Audience"><title>Intended
Audience</title>
+
+<warning>
+"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.
+</warning>
+
+ <p>
+ Devs and skin developer that wants to get started with forrest:contract
development.
+ To really understand this how-to you need basic and sometimes advanced
understanding of
+ the "old fashion" skin development process.
+ </p>
+ </section><section id="Purpose"><title>Purpose</title>
+ <p>
+ This setup guide will explain how to create a forrest:contract from
scratch and
+ how this forrest:contract work with the core parts of forrest.
+ </p>
+ </section><section id="Prerequisites"><title>Prerequisites</title>
+ <ul>
+ <li>
+ You have a ready-to-go new seed (newSeed) based on views like
described in <a href="site:howto/view/install">Install views</a>.
+ </li>
+ <li>
+ This includes as well all additional plugins that are mentioned in <a
href="site:howto/view/install">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.
+ </li>
+ </ul>
+ </section><section id="Steps"><title>Steps</title>
+ <note>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 -
+ in comparison with "old fashion" skins - usecase i18n</note>
+ <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
+ support for i18n. The case is that the <code>site2xhtml.xsl</code> 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.
+ </p>
+ <source xml:space="preserve">
+
+- <script language="JavaScript"
+- type="text/javascript">document.write("Published: " +
document.lastModified);</script>
+
++ <script type="text/javascript">document.write("<i18n:text >Last
++ Published:</i18n:text>&#160;" + document.lastModified);
+
+ </source>
+ <section id="enhanceMaintainment">
+ <title>Enhance the maintainment</title>
+ <p>Now we can enhance the maintainment for the future and we give this
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:
+ </p>
+ <ol>
+ <li>replace the script by <xsl:call-template
name="siteinfo-last-published"/></li>
+ <li>and add:</li>
+ </ol>
+
+ <source xml:space="preserve"><xsl:template
name="siteinfo-last-published">
+ <script type="text/javascript">
+ document.write("<i18n:text >Last
Published:</i18n:text>&#160;" + document.lastModified);
+ </script>
+</xsl:template>
+ </source>
+ <p>
+ This allows us in a next maintainment just change the code of
+ <xsl:template name="siteinfo-last-published"/> and apply it in
any position where
+ it is placed.
+ </p>
+ <note>
+ Now this refactoring of the site2xhtml.xsl is exactly what we doing in
creating contracts for views.
+ </note>
+ </section>
+ <section id="blankContract">
+ <title>Explaining the blank forrest:contract</title>
+ <p>
+ To start a new forrest:contract you can copy the 'blank.ft' from
+
<code>org.apache.forrest.plugin.output.viewHelper.xhtml/resources/templates</code>.
+ The exact file system path can be looked up at
<code>http://localhost:8888/ls.contracts.html</code>.
+ </p>
+ <p>
+ The 'blank.ft' is a simple xml file with the following code which you
can use to base new contracts
+ on:
+ </p>
+ <source xml:space="preserve">
+<forrest:contract
+ xmlns:forrest="http://apache.org/forrest/templates/1.0";
+ name="blank" type="nugget">
+
+ <!--NOTE:
+ When using the blank template as c'n p 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*.
+ </description>
+ <usage><![CDATA[<forrest:contract
name="blank"/>]]></usage>
+ <forrest:template xmlns:forrest="http://apache.org/forrest/templates/1.0";
+ format="xhtml" name="blank" inputFormat="xsl" body="false" head="false">
+ <xsl:stylesheet version="1.1"
+ xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
+ <!--Add here the needed templates-->
+ </xsl:stylesheet>
+ </forrest:template>
+</forrest:contract>
+
+ </source>
+ <p>
+ The most important is the name of the contract
<code><forrest:contract name="blank"/></code>.
+ This name is the same as the file name of the contract (without file
extension) <code>blank.ft</code>.
+ </p>
+ <note>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!
+ </note>
+ <p>
+ The <code><description/></code> tag needs to be filled in with
some information
+ that is explaining the contract to the webdesigner. The better
explained the more efficient
+ for the webdesigner to pick the right contract.
+ </p>
+ <source xml:space="preserve"><description>
+ siteinfo-last-published-howto will output the last published date of the
site with the help of jscript.
+</description>
+ </source>
+ <p>
+ In the <code><usage/></code> tag we have to explain how the
designer can use
+ the contract in his view.
+ </p>
+ <source
xml:space="preserve"><usage><![CDATA[<forrest:contract
name="siteinfo-last-published-howto"/>]]></usage>
+ </source>
+ <p>
+ <code><forrest:template name="blank" body="false" head="false">
</code>
+ 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 "<code>-body</code>"!!!
+ </p>
+ <note>
+ 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".
+ </note>
+ <p>
+ A <forrest:template /> has the son <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>
+ <source xml:space="preserve">
+<xsl:stylesheet version="1.1"
+ xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
+ <!--Add here the needed templates-->
+ <xsl:template name="blank-body"/>
+</xsl:stylesheet>
+ </source>
+ </section>
+ <section id="newContract">
+ <title>Create a new contract</title>
+ <fixme author="thorsten">
+ We need to explain basic naming convention for contracts. Like
+ "naming do not say about layout position but functionality of the
contract.".
+ </fixme>
+ <p>
+ Now lets pick up the example we started with
and create a "siteinfo-last-published-howto" contract.
+ Save the blank.ft to
<code>{project.home}/src/documentation/resources/templates/siteinfo-last-published-howto.ft</code>.
+ </p>
+ <p>
+ Now the maintainment optimized code (xpath="/html/body/*") was:
+ </p>
+ <source xml:space="preserve">
+<xsl:template name="siteinfo-last-published">
+ <script type="text/javascript">
+ document.write("<i18n:text >Last
Published:</i18n:text>&#160;" + document.lastModified);
+ </script>
+</xsl:template></source>
+ <p>
+ In this code we have to do the following steps to use it in our
contract:
+ </p>
+ <ul>
+ <li>Search and replace "siteinfo-last-published" with
"siteinfo-last-publish-howto-body"</li>
+ <li>Add a "debug string - " to the template</li>
+ </ul>
+ <p>
+ The contract after this steps should look like:
+ </p>
+ <source xml:space="preserve">
+<xsl:template name="siteinfo-last-publish-howto-body">
+debug string -
+ <script type="text/javascript">
+ document.write("<i18n:text >Last
Published:</i18n:text>&#160;" + document.lastModified);
+ </script>
+</xsl:template></source>
+ <p>Now we have to do some last steps in the
siteinfo-last-publish-howto.ft</p>
+ <ul>
+ <li>Search and replace "blank" with "siteinfo-last-publish-howto"</li>
+ <li>Add description and usage of the contract</li>
+ <li>Set @body="true"</li>
+ <li>Copy the maintainment optimized code to the contract.</li>
+ </ul>
+ <p>
+ As the result your code should look like this:
+ </p>
+ <source xml:space="preserve"><forrest:contract
xmlns:forrest="http://apache.org/forrest/templates/1.0";
+ name="siteinfo-last-published-howto" type="nugget">
+ <description>
+ siteinfo-last-published-howto will output the last published date of the
site with the help of jscript.
+ </description>
+ <usage><![CDATA[<forrest:contract
name="siteinfo-last-published-howto"/>]]></usage>
+ <forrest:template
+ xmlns:i18n="http://apache.org/cocoon/i18n/2.1";
+ xmlns:forrest="http://apache.org/forrest/templates/1.0";
+ format="xhtml" name="siteinfo-last-published-howto" inputFormat="xsl"
body="true" head="false">
+ <xsl:stylesheet version="1.1"
+ xmlns:i18n="http://apache.org/cocoon/i18n/2.1";
+ xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
+ <xsl:template name="siteinfo-last-published-howto-body">
+ debug string -
+ <script type="text/javascript">document.write("<i18n:text
>Last Published:</i18n:text>&#160;" +
document.lastModified);</script>
+ </xsl:template>
+ </xsl:stylesheet>
+ </forrest:template>
+</forrest:contract>
+ </source>
+ </section>
+ <section id="viewContract">
+ <title>Activating the contract</title>
+ <p>
+ To see whether the new contract works we need to add it to our view.
+ The contract usage contains the contract-tag
<code><forrest:contract name="siteinfo-last-published-howto"/></code>
+ Please see <a href="site:howto/view/DSL">Getting started with
forrest:view DSL</a> for more details.
+ </p>
+ <fixme author="thorsten">
+ Let us now look into advanced features of views.
+ I will write a how-to for advanced contracts soon. :)
+ </fixme>
+ </section>
+ </section><section id="Further Reading"><title>Further Reading</title>
+ <p>
+ Congratulations you are now able to work with view contracts.
+ From here we recommend to read the following How-To's:
+ </p>
+ <ul>
+ <li><a href="site:howto/view/DSL">Getting started with forrest:view
DSL</a> </li>
+ </ul>
+ </section><section id="Feedback"><title>Feedback</title>
+ <p>
+ Please provide feedback about this document via the
+ <a href="site:mail-lists">mailing lists</a>.
+ </p>
+ </section></body></document>
\ No newline at end of file
Propchange: forrest/site/docs_0_70/howto/howto-view-contracts.source.xml
------------------------------------------------------------------------------
svn:eol-style = native
Added: forrest/site/docs_0_70/howto/howto-view-dsl.source.xml
URL:
http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/howto-view-dsl.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/docs_0_70/howto/howto-view-dsl.source.xml (added)
+++ forrest/site/docs_0_70/howto/howto-view-dsl.source.xml Wed Feb 8 16:26:20
2006
@@ -0,0 +1,274 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+ Copyright 2002-2005 The Apache Software Foundation or its licensors,
+ as applicable.
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+--><document><header>
+ <title>How to use the forrest:view config-DSL</title>
+ <abstract>
+ This How-To describes the usage of the forrest:view config Domain Specific
Language
+ to create beautiful website in no time.
+ </abstract>
+ <last-modified-content-date date="2005-06-06"/>
+ </header><body><section id="Intended Audience"><title>Intended
Audience</title>
+
+<warning>
+"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 far from being finished.
+</warning>
+
+ <p>
+ This part of the views is dedicated to webdesigner and user with some
knowlegde of css.
+ </p>
+ </section><section id="Purpose"><title>Purpose</title>
+ <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.
+ </p>
+ </section><section id="Prerequisites"><title>Prerequisites</title>
+ <ul>
+ <li>
+ You have a ready-to-go new seed (newSeed) based on views like
described in <a href="site:howto/view/install">Install views</a>.
+ </li>
+ <li>
+ This includes as well all additional plugins that are mentioned in <a
href="site:howto/view/install">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.
+ </li>
+ </ul>
+ </section><section id="Steps"><title>Steps</title>
+ <note>
+ When developing with views we assume you are using 'forrest run' and the
following workflow:<br/>
+ change files -> refresh browser
+ </note>
+ <p>
+ 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 <code>skinconf.xml</code> 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
+ 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. <code><div id="content-main"/>
</code>. 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/repos/asf/forrest/trunk/main/webapp/skins/leather-dev/contracts.initial.txt";>
+ inicial 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.
+ </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
+ the output. Actually a <code><forrest:hook name="layoutId"/></code>
will be transformed
+ to <code><div id="layoutId"/> </code>
+ </p>
+ <p>
+ <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>
+ <section id="emptyView">
+ <title>Empty view file</title>
+ <source xml:space="preserve"><forrest:views
xmlns:forrest="http://apache.org/forrest/templates/1.0"; >
+ <forrest:view type="xhtml">
+ </forrest:view>
+</forrest:views>
+ </source>
+ <p>
+ <strong> forrest:view</strong> is designed to be open for any format
that can use<strong> forrest:view</strong> as configuration file.
+ 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. :)
+ </p>
+ </section>
+
+ <section id="firstView">
+ <title>Creating your first view</title>
+ <p>
+ In this section we will create a new view. We
will override the default view of the view-plugin
+ for the index page of the <a
href="site:howto/view/install">newSeed</a>.
+ For that we will create a file called <code>index.fv</code> and save
it in our xdocs directory.
+ This will make <strong>only</strong> the index.html page look
different from the rest of the project.
+ </p>
+ <p>
+ Remember: pointing your browser to
<code>http://localhost:8888/ls.contracts.html</code> will
+ show a page with all contracts that you can use in your project.
+ </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
+ <code>index.fv</code> should look like:
+ </p>
+ <source xml:space="preserve"><forrest:views
xmlns:forrest="http://apache.org/forrest/templates/1.0"; >
+ <forrest:view type="xhtml">
+ <forrest:contract name="content-main"/>
+ </forrest:view>
+</forrest:views>
+ </source>
+ <p>
+ Let's try our new view by pointing to
<code>http://localhost:8888/index.html</code>.
+ We will see only the main content. :) Now let's 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>
+ <source xml:space="preserve"><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:views>
+ </source>
+ <p>
+ We find now 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>
+ </section>
+ <section id="hookView">
+ <title>Hooks in views</title>
+ <p>
+ We will use now the first time a <code><forrest:hook
name="layoutId"/></code>.
+ 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.
+ In the default.css we can find
+ </p>
+ <source xml:space="preserve">/* menu */
+#leftbar {
+ width: 25%;
+ float: left;
+ background: #eae8e3;
+ border: thin dashed #565248;
+}
+ </source>
+ <p>
+ With this information we know to use <code><forrest:hook
name="leftbar"/></code>
+ and add contracts into that container.
+ </p>
+ <p>
+ If we want to put the nav-section contract into the left side position
+ of the site we need to place the contract into that hook. Like:
+ </p>
+ <source xml:space="preserve"><forrest:hook name="leftbar">
+ <forrest:contract name="nav-section"/>
+</forrest:hook>
+ </source>
+ <p>
+ Our view will then look like:
+ </p>
+ <source xml:space="preserve"><forrest:views
xmlns:forrest="http://apache.org/forrest/templates/1.0"; >
+ <forrest:view type="xhtml">
+ <forrest:hook name="leftbar">
+ <forrest:contract name="nav-section"/>
+ </forrest:hook>
+ <forrest:contract name="content-main"/>
+ </forrest:view>
+</forrest:views>
+ </source>
+ </section>
+ <section id="cssView">
+ <title>CSS in views</title>
+ <p>
+ We know now how to place contracts and hooks in our view, till 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 <code><forrest:css
url="default.css"/></code>.
+ </p>
+ <p>
+ We will now create a file in
<code>{project:skins-dir}{path}/{name}.css</code>. In our case
+ we will save a file called howTo.css in
newSeed/src/documentation/skins/css/howTo.css containing only
+ the following css:
+ </p>
+ <source xml:space="preserve">/* menu */
+#leftbar {
+ width: 25%;
+ float: left;
+ background: #CCCCFF;
+ border: thin solid #000000;
+}
+ </source>
+ <p>
+ We just changed the border-style to 'solid', the background to
'#CCCCFF' and the color to '#000000'.
+ Now we have to add a new tag to tell that we want to override the
default.css. We are doing this
+ by adding the tag <code><forrest:css url="howTo.css"/></code> to
our view.
+ </p>
+ <note>
+ <code><forrest:css url="howTo.css"/></code> has to be direct son
of
+ <code><forrest:view type="xhtml"></code>!!!
+ </note>
+ <source xml:space="preserve"><forrest:views
xmlns:forrest="http://apache.org/forrest/templates/1.0"; >
+ <forrest:view type="xhtml">
+ <forrest:css url="howTo.css"/>
+ <forrest:hook name="leftbar">
+ <forrest:contract name="nav-section"/>
+ </forrest:hook>
+ <forrest:contract name="content-main"/>
+ </forrest:view>
+</forrest:views>
+ </source>
+ <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
+ <code><forrest:hook name="content"/></code> We need to add the
new layout container
+ to our howTo.css:
+ </p>
+ <source xml:space="preserve">
+/* The actual content */
+#content {
+ margin-left: 25%;
+ padding: 0 20px 0 20px;
+ background: #B9D3EE;
+}
+ </source>
+ <p>
+ Then we have to add the 'content-main' contract to the 'content' hook,
the resulting view looks like:
+ </p>
+ <source xml:space="preserve"><forrest:views
xmlns:forrest="http://apache.org/forrest/templates/1.0"; >
+ <forrest:view type="xhtml">
+ <forrest:css url="howTo.css"/>
+ <forrest:hook name="leftbar">
+ <forrest:contract name="nav-section"/>
+ </forrest:hook>
+ <forrest:hook name="content">
+ <forrest:contract name="content-main"/>
+ </forrest:hook>
+ </forrest:view>
+</forrest:views>
+ </source>
+ <p>
+ We are now able to place contracts into layout container and add
custom css to the view.
+ </p>
+ <fixme author="thorsten">
+ Let us now look into advanced features of views.
+ I will write a how-to for advanced contracts soon. :)
+ </fixme>
+ <!--<fixme author="thorsten">This section is next to be
writen/finished</fixme>-->
+ </section>
+ </section><section id="Further Reading"><title>Further Reading</title>
+ <p>
+ Congratulations you are now able to work with the view DSL.
+ From here we recommend to read the following How-To's:
+ </p>
+ <ul>
+ <li><a href="site:howto/view/contracts">Create your own contract
implementation</a> </li>
+ </ul>
+ </section><section id="Feedback"><title>Feedback</title>
+ <p>
+ Please provide feedback about this document via the
+ <a href="site:mail-lists">mailing lists</a>.
+ </p>
+ </section></body></document>
\ No newline at end of file
Propchange: forrest/site/docs_0_70/howto/howto-view-dsl.source.xml
------------------------------------------------------------------------------
svn:eol-style = native
Added: forrest/site/docs_0_70/howto/howto-view-install.source.xml
URL:
http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/howto-view-install.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/docs_0_70/howto/howto-view-install.source.xml (added)
+++ forrest/site/docs_0_70/howto/howto-view-install.source.xml Wed Feb 8
16:26:20 2006
@@ -0,0 +1,153 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+ Copyright 2002-2005 The Apache Software Foundation or its licensors,
+ as applicable.
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+--><document><header>
+ <title>How to install the view package</title>
+ <abstract>
+ This How-To describes the setup of the plugins (needed to work with
forrest:views and forrest:contracts) and a fresh seed.
+ </abstract>
+ <last-modified-content-date date="2005-06-06"/>
+ </header><body><section id="Intended Audience"><title>Intended
Audience</title>
+
+<warning>
+"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.
+</warning>
+
+ <p>
+ Users/devs who wants to get started with view development.
+ This setup guide is valid for both user and devs.
+ </p>
+ </section><section id="Purpose"><title>Purpose</title>
+ <p>
+ To help user installing views. This is the "getting started" setup-guide.
+ </p>
+ </section><section id="Prerequisites"><title>Prerequisites</title>
+ <ul>
+ <li>You have to use the trunk version of forrest for using views because
it is in an early stage</li>
+ </ul>
+ </section><section id="Steps"><title>Steps</title>
+ <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>
+ <section id="localBuild">
+ <title>Build the view and the viewHelper plugins</title>
+ <p>
+ The first step is to build the view and the viewHelper plugins. Change
to a console of your choice
+ and go (cd) to the trunk version of forrest {forrest-trunk}. Then do
an update and after this
+ deploy both plugins locally.
+ </p>
+ <source xml:space="preserve">
+cd {forrest-trunk}
+svn up
+cd whiteboard/plugins/org.apache.forrest.plugin.internal.view/
+ant local-deploy
+cd ../org.apache.forrest.plugin.output.viewHelper.xhtml/
+ant local-deploy
+ </source>
+ </section>
+ <section id="newSeed">
+ <title>Seed a new project</title>
+ <p>
+ Go to the dir where you want to seed a new
project and seed it.
+ Then we have to prepare a default.fv directory in project.conf-dir
(forrest.properties)
+ of the fresh seed. That will be needed as soon you modify the default
view of your project.
+ The "templates"-directory is need for your project specific contract
implementations.
+ </p>
+ <source xml:space="preserve">
+cd ~/src/newSeed
+forrest seed
+mkdir src/documentation/conf
+mkdir src/documentation/resources/templates
+ </source>
+ </section>
+ <section id="forrestProperties">
+ <title>Modifying forrest.properties</title>
+ <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:
+ </p>
+ <source xml:space="preserve">
+project.required.plugins=org.apache.forrest.plugin.output.viewHelper.xhtml,org.apache.forrest.plugin.internal.view
+ </source>
+ <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".
+ </p>
+ <note>We exchanging only
+ site2xhtml.xsl of leather-dev skin by the plugins and some
contracts are based
+ on e.g. document2html.xsl output of leather-dev.</note>
+ <source xml:space="preserve">
+project.skin=leather-dev
+ </source>
+ </section>
+ <section id="testing">
+ <title>Test your new view based project</title>
+ <p>
+ Now you have finished the preparation and the setup to finally try
+ </p>
+ <source xml:space="preserve">
+forrest run
+ </source>
+ <p>then point to <a
href="http://localhost:8888/";>http://localhost:8888/</a> and you should see the
default
+ view based skin.</p>
+ <note>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
+changes on your pages when working with *.fv. </note>
+ </section>
+ <section id="availableContracts">
+ <title>Available contracts</title>
+ <p>
+ To start working with views you need to know which contracts you
can use.
+ For this we will install another plugin
<code>org.apache.forrest.plugin.input.viewHelper.xhtml.ls</code>.
+ The setup is:
+ </p>
+ <source xml:space="preserve">
+cd {forrest-trunk}
+svn up
+cd whiteboard/plugins/org.apache.forrest.plugin.input.viewHelper.xhtml.ls/
+ant local-deploy
+</source>
+ <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
+ by editing the forrest.properties of the <a
href="site:howto/view/install">newSeed</a>
+ to <strong>add</strong> the plugin:
+ </p>
+ <source xml:space="preserve">
+project.required.plugins=org.apache.forrest.plugin.input.viewHelper.xhtml.ls
+ </source>
+ <p>
+ Now point your browser to
<code>http://localhost:8888/ls.contracts.html</code>.
+ On this page you will find all contracts that you can use in your
project.
+ </p>
+ </section>
+ </section><section id="Further Reading"><title>Further Reading</title>
+ <p>
+ Congratulations you are now able to work with views.
+ From here we recommend to read the following How-To's:
+ </p>
+ <ul>
+ <li><a href="site:v0.70//howto/view/DSL">Getting started with
forrest:view DSL</a> </li>
+ <li><a href="site:v0.70//howto/view/contracts">Create your own contract
implementation</a> </li>
+ </ul>
+ </section><section id="Feedback"><title>Feedback</title>
+ <p>
+ Please provide feedback about this document via the
+ <a href="site:mail-lists">mailing lists</a>.
+ </p>
+ </section></body></document>
\ No newline at end of file
Propchange: forrest/site/docs_0_70/howto/howto-view-install.source.xml
------------------------------------------------------------------------------
svn:eol-style = native
Added: forrest/site/docs_0_70/howto/index.source.xml
URL:
http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/index.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/docs_0_70/howto/index.source.xml (added)
+++ forrest/site/docs_0_70/howto/index.source.xml Wed Feb 8 16:26:20 2006
@@ -0,0 +1,78 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+ Copyright 2002-2005 The Apache Software Foundation or its licensors,
+ as applicable.
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+--><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN"
"http://forrest.apache.org/dtd/document-v12.dtd";>
+<document>
+
+ <header>
+ <title>Overview of the How-To documents</title>
+ </header>
+
+ <body>
+ <section>
+ <title>Forrest Site and Documentation</title>
+ <ul>
+ <li><link href="site:v0.70//howto/write-howto">How to write a
How-To</link>
+ - Provides instructions about writing documents. Please copy this
+ file to serve as a template for your own document.
+ </li>
+ <li><link href="site:v0.70//howto/asf-mirror">Generate an ASF mirrors
page using interactive web form</link>
+ - include html form elements
+ into a forrest-generated html page. For example, this enables
building
+ automated download mirror pages for ASF project websites.
+ Also shows how to process "extra" documents, i.e. that have no links
+ from anywhere in the site.
+ </li>
+ </ul>
+ </section>
+
+ <section>
+ <title>Using Forrest</title>
+ <ul>
+ <li><link href="site:v0.70//howto/pdf-tab">How to create a PDF
document for each tab</link>
+ - Describes the generation of a PDF document for each
+ group of documents that is defined by a tab.
+ </li>
+ <li><link href="site:v0.70//howto/editcss">How to edit Forrest's CSS
in a WYSIWYG fashion</link>
+ - Describes the use of Mozilla Firebird and the free EditCSS-Plugin
to
+ customize your Forrest design in a WYSIWYG-way.
+ </li>
+ <li><link href="site:v0.70//howto/corner-css">How to modify the color
of generated corner images</link>
+ - Describes the use of CSS values from the skinconf.xml configuration
+ file to change the color of the corner images to be suitable for
+ your own skin colors. Advanced use explains editing the *.css too.
+ </li>
+ <li><link href="site:v0.70//howto/maven">How to run Forrest from
within Maven</link>
+ - For Maven users who want to generate their project's documentation
and/or website
+ using Forrest in lieu of Maven's site plugin.
+ </li>
+ <li><link href="site:v0.70//custom-html-source">How to customize
processing of html source</link>
+ - When integrating legacy html documents into a Forrest-built site,
additional processing
+ of the html sources might be required.
+ </li>
+ </ul>
+ </section>
+
+ <section>
+ <title>Extending Forrest</title>
+ <ul>
+ <li><link href="site:v0.70//howto/buildPlugin">How to create a Plugin
for Forrest</link>
+ - Describes how to write a plugin to add new input or output document
+ formats, or to modify the default behaviour of Forrest</li>
+ </ul>
+ </section>
+ </body>
+
+</document>
\ No newline at end of file
Propchange: forrest/site/docs_0_70/howto/index.source.xml
------------------------------------------------------------------------------
svn:eol-style = native
Added: forrest/site/docs_0_70/howto/multi/howto-multi.source.xml
URL:
http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/multi/howto-multi.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/docs_0_70/howto/multi/howto-multi.source.xml (added)
+++ forrest/site/docs_0_70/howto/multi/howto-multi.source.xml Wed Feb 8
16:26:20 2006
@@ -0,0 +1,66 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+ Copyright 2002-2005 The Apache Software Foundation or its licensors,
+ as applicable.
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+--><document><header>
+ <title>Example of a multi-page how-to</title>
+ <abstract>This is the shell of a multi-page how-to. Add your own content.
+ </abstract>
+ <last-modified-content-date date="2003-09-10"/>
+ </header><body><section id="Intended audience"><title>Intended
audience</title>
+ <p>Describe the audience here.</p>
+ </section><section id="Purpose"><title>Purpose</title>
+ <p>Explain the purpose of the howto here.</p>
+ </section><section id="Prerequisites"><title>Prerequisites</title>
+ <p>Configuration requirements:</p>
+ <ul>
+ <li>This.</li>
+ <li>That.</li>
+ </ul>
+ <p>Requisite skills:</p>
+ <ul>
+ <li>These.</li>
+ <li>Those.</li>
+ </ul>
+
+ </section><section id="Various Steps"><title>Various Steps</title>
+ <p>After this brief introductory paragraph, the steps are described in
+ separate documents:</p>
+ <ul>
+ <li><link href="step1.html">Step 1: Do foo</link></li>
+ <li><link href="step2.html">Step 2: Do foobar</link></li>
+ <li><link href="step3.html">Step 3: Finish up</link></li>
+ </ul>
+ </section><section id="Real World Extension"><title>Real World
Extension</title>
+ <p>Briefly describe some relevant extensions that go beyond these
basics.</p>
+ </section><section id="Tips"><title>Tips</title>
+ <p>If you have a problem running the example, then you can try the
+ following tips:</p>
+ <ul>
+ <li>Tip #1</li>
+ <li>Tip #2</li>
+ </ul>
+ </section><section id="Related Resources"><title>Related Resources</title>
+ <p>Cocoon resources:</p>
+ <ul>
+ <li>For all Cocoon basics see the
+ <link href="ext:cocoon">Cocoon Web site</link>.
+ </li>
+ </ul>
+ </section><section id="Feedback"><title>Feedback</title>
+ <p>If you find any faults in this How-to or can see any improvements,
+ please contact the
+ <link href="site:mail-lists">project mail lists</link> with them.
+ </p>
+ </section></body></document>
\ No newline at end of file
Propchange: forrest/site/docs_0_70/howto/multi/howto-multi.source.xml
------------------------------------------------------------------------------
svn:eol-style = native
Added: forrest/site/docs_0_70/howto/multi/step1.source.xml
URL:
http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/multi/step1.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/docs_0_70/howto/multi/step1.source.xml (added)
+++ forrest/site/docs_0_70/howto/multi/step1.source.xml Wed Feb 8 16:26:20 2006
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+ Copyright 2002-2005 The Apache Software Foundation or its licensors,
+ as applicable.
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+--><document><header>
+ <title>Multi-page how-to: Step 1</title>
+ <last-modified-content-date date="2003-09-10"/>
+ </header><body><section id="Step 1: Do foo"><title>Step 1: Do foo</title>
+ <section>
+ <title>First section of this step</title>
+ <p>Description here.</p>
+ </section>
+ <section>
+ <title>Second section of this step</title>
+ <p>Description here.</p>
+ <p>Source code follows ...</p>
+ <source xml:space="preserve">
+<pointy-brackets>
+ <are-allowed-in-source-CDATA-sections/>
+</pointy-brackets>
+
+ </source>
+ <p>Now we move on to <link href="step2.html">Step 2: Do foobar</link></p>
+ </section>
+ </section></body></document>
\ No newline at end of file
Propchange: forrest/site/docs_0_70/howto/multi/step1.source.xml
------------------------------------------------------------------------------
svn:eol-style = native
Added: forrest/site/docs_0_70/howto/multi/step2.source.xml
URL:
http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/multi/step2.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/docs_0_70/howto/multi/step2.source.xml (added)
+++ forrest/site/docs_0_70/howto/multi/step2.source.xml Wed Feb 8 16:26:20 2006
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+ Copyright 2002-2005 The Apache Software Foundation or its licensors,
+ as applicable.
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+--><document><header>
+ <title>Multi-page how-to: Step 2</title>
+ <last-modified-content-date date="2003-09-10"/>
+ </header><body><section id="Step 2: Do foobar"><title>Step 2: Do
foobar</title>
+ <section>
+ <title>First section of this step</title>
+ <p>Description here.</p>
+ </section>
+ <section>
+ <title>Second section of this step</title>
+ <p>Description here.</p>
+ <p>Now we move on to <link href="step3.html">Step 3: Finish up</link></p>
+ </section>
+ </section></body></document>
\ No newline at end of file
Propchange: forrest/site/docs_0_70/howto/multi/step2.source.xml
------------------------------------------------------------------------------
svn:eol-style = native
Added: forrest/site/docs_0_70/howto/multi/step3.source.xml
URL:
http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/multi/step3.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/docs_0_70/howto/multi/step3.source.xml (added)
+++ forrest/site/docs_0_70/howto/multi/step3.source.xml Wed Feb 8 16:26:20 2006
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+ Copyright 2002-2005 The Apache Software Foundation or its licensors,
+ as applicable.
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+--><document><header>
+ <title>Multi-page how-to: Step 3</title>
+ <last-modified-content-date date="2002-09-10"/>
+ </header><body><section id="Step 3: Finish up"><title>Step 3: Finish
up</title>
+ <section>
+ <title>First section of this step</title>
+ <p>Description here.</p>
+ </section>
+ <section>
+ <title>Second section of this step</title>
+ <p>Description here.</p>
+ <p>Congratulations, you have finished. Now return to the
+ <link href="howto-multi.html">start</link>.</p>
+ </section>
+ </section></body></document>
\ No newline at end of file
Propchange: forrest/site/docs_0_70/howto/multi/step3.source.xml
------------------------------------------------------------------------------
svn:eol-style = native
Added: forrest/site/docs_0_70/howto/project_sitemap.xmap.source.xml
URL:
http://svn.apache.org/viewcvs/forrest/site/docs_0_70/howto/project_sitemap.xmap.source.xml?rev=376128&view=auto
==============================================================================
--- forrest/site/docs_0_70/howto/project_sitemap.xmap.source.xml (added)
+++ forrest/site/docs_0_70/howto/project_sitemap.xmap.source.xml Wed Feb 8
16:26:20 2006
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><document><header> <!-- <meta
content="HTML Tidy, see www.w3.org" name="generator"/> --> <title>sitemap.xmap
in the Project Documentation
Directory</title></header><body><section><title>sitemap.xmap in the Project
Documentation Directory</title><pre>
+<?xml version="1.0"?>
+<map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
+ <map:pipelines>
+</pre><section><title>Example pipeline for '**custom.xml'</title><pre>
+ <map:pipeline>
+ <map:match pattern="**custom.xml">
+ <map:generate src="{project:content.xdocs}{1}custom.xml" />
+ <map:transform src="{project:resources.stylesheets}/hello2document.xsl"
/>
+ <map:serialize type="xml"/>
+ </map:match>
+ </map:pipeline>
+ </map:pipelines>
+</map:sitemap>
+</pre></section></section></body></document>
\ No newline at end of file
Propchange: forrest/site/docs_0_70/howto/project_sitemap.xmap.source.xml
------------------------------------------------------------------------------
svn:eol-style = native
