You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by gk...@apache.org on 2008/07/16 12:10:44 UTC
svn commit: r677225 [2/3] - in /cocoon/site/site/2.2/blocks/forms/1.0: ./
apidocs/
Modified: cocoon/site/site/2.2/blocks/forms/1.0/487_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/blocks/forms/1.0/487_1_1.html?rev=677225&r1=677224&r2=677225&view=diff
==============================================================================
--- cocoon/site/site/2.2/blocks/forms/1.0/487_1_1.html (original)
+++ cocoon/site/site/2.2/blocks/forms/1.0/487_1_1.html Wed Jul 16 03:10:42 2008
@@ -334,8 +334,6 @@
-
-
<li class='menuCollapse'>
<a href="project-reports.html">Project Reports</a>
@@ -343,13 +341,13 @@
</ul>
</li>
</ul>
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Cocoon Forms: Datatypes</h1><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Context</h1><p>Datatypes are used by certain widgets, more specifically the
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Cocoon Forms: Datatypes</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Context</h1><p>Datatypes are used by certain widgets, more specifically the
<a href="481_1_1.html">field</a> and <a href="490_1_1.html">multivaluefield</a>
widgets, to allow them to edit different types of data (e.g. strings, numbers,
dates). For a general introduction of the relationship between the widget and
the datatype, see the documentation of the <a href="481_1_1.html">field</a>
-widget.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">General information</h1><p>In its most basic form a datatype is declared as follows:</p><pre><fd:datatype base="..."></pre><p>The <strong>base</strong> attribute refers to one of the built-in datatypes
-such as string or long.</p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Convertors</h2><p>A datatype needs a convertor. The purpose of a convertor is to convert
+widget.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">General information</h1><p>In its most basic form a datatype is declared as follows:</p><pre><fd:datatype base="..."></pre><p>The <strong>base</strong> attribute refers to one of the built-in datatypes
+such as string or long.</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Convertors</h2><p>A datatype needs a convertor. The purpose of a convertor is to convert
between string and object representations of values. There is always a default
convertor, but you change or configure that using the fd:convertor element.
Here's an example for dates:</p><pre><fd:datatype base="date">
@@ -361,7 +359,7 @@
</fd:datatype></pre><p>The <strong>type</strong> attribute on the fd:convertor element is optional,
if not specified the default one will be used (configured in the cocoon.xconf).
Any further content of the fd:convertor element is specific to the convertor
-implementation and will be documented in a seperate section.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Available datatypes</h1><table class="bodyTable">
+implementation and will be documented in a seperate section.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Available datatypes</h1><table class="bodyTable">
<tbody>
<tr class="a">
<th>
@@ -466,7 +464,7 @@
</td>
</tr>
</tbody>
-</table><h2 id="enum" xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Enumerated datatype</h2><p>The <strong>enum</strong> datatype is meant to be used with types
+</table><h2 id="enum" xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Enumerated datatype</h2><p>The <strong>enum</strong> datatype is meant to be used with types
implementing Joshua Bloch's
<a href="http://developer.java.sun.com/developer/Books/shiftintojava/page1.html#replaceenums">typesafe
enum pattern</a>. The following is a possible implementation:</p><pre>package com.example;
@@ -493,12 +491,12 @@
</p><p>If you provide a <tt>toString()</tt> method which returns something
different, you should also provide a <tt>fromString(String, Locale)</tt> method
to convert those strings back to instances.</p><p>The enum datatype is typically used together with the
-<a href="753_1_1.html"><strong>enum</strong> selection list type</a>.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Available convertors</h1><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Decimal convertors</h2><p>Numeric or decimal types can be formatted in two ways: plain and formatted.
-The first is very simple, the second provides locale-dependent formatting.</p><h3 id="plain" xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">plain</h3><p>This convertor is not locale-dependent. It shows the full precision of the
+<a href="753_1_1.html"><strong>enum</strong> selection list type</a>.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Available convertors</h1><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Decimal convertors</h2><p>Numeric or decimal types can be formatted in two ways: plain and formatted.
+The first is very simple, the second provides locale-dependent formatting.</p><h3 id="plain" xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">plain</h3><p>This convertor is not locale-dependent. It shows the full precision of the
number and uses dot as the decimal separator.</p><p>Configuration example:</p><pre><fd:datatype base="decimal">
<fd:convertor type="plain"/>
</fd:datatype></pre><p>Output of this field with a value of <em>1234.5678</em> would be</p><pre>1234.5678
-</pre><h3 id="decimalformatting" xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">formatting (decimal)</h3><p>This convertor uses the <tt>java.text.DecimalFormat</tt> class (or
+</pre><h3 id="decimalformatting" xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">formatting (decimal)</h3><p>This convertor uses the <tt>java.text.DecimalFormat</tt> class (or
<tt>com.ibm.icu.text.DecimalFormat</tt> class if it is present in the
classpath). This means it can perform locale-dependent, pattern-based formatting
of numbers.</p><p>Configuration pseudo-schema:</p><pre><fd:convertor type="formatting" variant="integer|number|currency|percent" ? >
@@ -519,8 +517,8 @@
</fd:patterns>
</fd:convertor>
</fd:datatype>
-</pre><p>Output of this field with a value of <em>1234.5612</em> would be</p><p>With locale = en-US: 1,234.56</p><p>With locale = nl-NL: 1234,5612</p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Date convertors</h2><p>The date datatype can be used both for dates as times. The date datatype
-supports the following convertors:</p><h3 id="dateformatting" xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">formatting (date)</h3><p>This convertor uses the <tt>java.text.SimpleDateFormat</tt> class (or
+</pre><p>Output of this field with a value of <em>1234.5612</em> would be</p><p>With locale = en-US: 1,234.56</p><p>With locale = nl-NL: 1234,5612</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Date convertors</h2><p>The date datatype can be used both for dates as times. The date datatype
+supports the following convertors:</p><h3 id="dateformatting" xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">formatting (date)</h3><p>This convertor uses the <tt>java.text.SimpleDateFormat</tt> class (or
<tt>com.ibm.icu.text.SimpleDateFormat</tt> class if it is present in the
classpath). This means it can perform locale-dependent, pattern-based formatting
of dates.</p><p>Configuration pseudo-schema:</p><pre><fd:convertor type="formatting" variant="date|time|datetime" ?
@@ -557,7 +555,7 @@
the "lenient" attribute is false, such a date won't validate.</p><div class="note"><div><strong>Note: </strong>Note that when binding XML documents you can also specify the
final pattern in which the date is stored. More information can be found on the
<a href="488_1_1.html">binding framework</a> page. The same holds true
-for numbers.</div></div><h3 id="millis" xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">millis</h3><p>The millis convertor for dates uses the number of milliseconds since January
+for numbers.</div></div><h3 id="millis" xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">millis</h3><p>The millis convertor for dates uses the number of milliseconds since January
1, 1970, 00:00:00 GMT as string representation. This will likely not be used to
present dates to the user, but may be useful in selection lists retrieved from
external sources.</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
Modified: cocoon/site/site/2.2/blocks/forms/1.0/488_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/blocks/forms/1.0/488_1_1.html?rev=677225&r1=677224&r2=677225&view=diff
==============================================================================
--- cocoon/site/site/2.2/blocks/forms/1.0/488_1_1.html (original)
+++ cocoon/site/site/2.2/blocks/forms/1.0/488_1_1.html Wed Jul 16 03:10:42 2008
@@ -322,8 +322,6 @@
-
-
<li class='menuCollapse'>
<a href="project-reports.html">Project Reports</a>
@@ -331,7 +329,7 @@
</ul>
</li>
</ul>
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Binding Framework</h1><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Intro</h1><p>Likely you will want to use CForms to "edit stuff", such as the properties of
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Binding Framework</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Intro</h1><p>Likely you will want to use CForms to "edit stuff", such as the properties of
a bean or data from an XML document (we'll simply use the term object to refer
to either of these). This supposes that before you show the form, you copy the
data from the object to the form, and after the form has been validated, you
@@ -348,7 +346,7 @@
<a href="http://www.w3.org/TR/xpath">XPath</a> expressions, so this binding
implementation can be used both with beans and XML documents. The rest of this
document will focus on this implementation.</p><p>The binding is configured using an XML file. This XML file contains elements
-in the fb namespace (Forms Binding):</p><pre>http://apache.org/cocoon/forms/1.0#binding</pre><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">What does a binding file look like?</h1><p>To give you an idea of what a binding file looks like, below a very simple
+in the fb namespace (Forms Binding):</p><pre>http://apache.org/cocoon/forms/1.0#binding</pre><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">What does a binding file look like?</h1><p>To give you an idea of what a binding file looks like, below a very simple
example is shown.</p><pre><fb:context xmlns:fb="http://apache.org/cocoon/forms/1.0#binding" path="/" >
<fb:value id="firstname" path="firstName"/>
<fb:value id="lastname" path="lastName"/>
@@ -361,7 +359,7 @@
context</a> to the specified path. The path expressions on the binding elements
occuring inside the context element will then be evaluated in this context, thus
relative to the path specified on the fb:context element.</p><p>The <tt>fb:value</tt> element is used to bind the value of a widget.</p><p>The binding framework can do much more than what is shown in the simple
-example above, so read on for more meat.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Quick reference of supported binding elements</h1><table class="bodyTable">
+example above, so read on for more meat.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Quick reference of supported binding elements</h1><table class="bodyTable">
<tbody>
<tr class="a">
<th>
@@ -560,7 +558,7 @@
</td>
</tr>
</tbody>
-</table><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Detailed reference of binding elements</h1><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">fb:*/@direction</h2><p>All Bindings share the ability to have the two distinct actions they provide
+</table><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Detailed reference of binding elements</h1><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">fb:*/@direction</h2><p>All Bindings share the ability to have the two distinct actions they provide
(i.e. load and save) been enabled or disabled by setting the attribute direction
to one of the following values:</p><table class="bodyTable">
<tbody>
@@ -610,7 +608,7 @@
</tr>
</tbody>
</table><p>The default value 'both' for this attribute makes its use optional.</p><p><strong>NOTE</strong>: this setting replaces the @readonly attribute that was
-available only on selected bindings.</p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">fb:context</h2><p>Attributes:</p><ul>
+available only on selected bindings.</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">fb:context</h2><p>Attributes:</p><ul>
<li>path</li>
<li>direction (optional)</li>
</ul>Child elements: anyThe <tt>fb:context</tt> element changes the JXPath context to the specified
@@ -630,7 +628,7 @@
<fb:value id="firstname" path="firstName"/>
<fb:value id="lastname" path="lastName"/>
</fb:context>
-...</pre><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">fb:value</h2><p>Attributes:</p><ul>
+...</pre><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">fb:value</h2><p>Attributes:</p><ul>
<li>id</li>
<li>path</li>
<li>direction (optional)</li>
@@ -655,7 +653,7 @@
</fd:convertor>
</fb:value></pre>The datatype attribute on the <tt>fd:convertor</tt> element, which you don't
have to specify in the form definition, identifies the datatype to which the
-convertor belongs.<h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">fb:aggregate</h2><p>Attributes:</p><ul>
+convertor belongs.<h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">fb:aggregate</h2><p>Attributes:</p><ul>
<li>id</li>
<li>path</li>
<li>direction</li>
@@ -666,7 +664,7 @@
widgets and lets the user edit their values in one textbox, splitting the values
out to the different widgets on submit based on a regexp.The <tt>fb:aggregate</tt> binding allows to bind the values of the individual
field widgets out of which an aggregatefield widget consists. The bindings for
-these field widgets are specified by the fb:value child elements.<h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">fb:repeater</h2>Attributes:<ul>
+these field widgets are specified by the fb:value child elements.<h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">fb:repeater</h2>Attributes:<ul>
<li>id</li>
<li>parent-path</li>
<li>row-path</li>
@@ -710,7 +708,7 @@
<p>The children of the <tt>fb:on-insert-row</tt> are executed in case a new row
has been added to the repeater. Typically this will contain a
<tt>fb:insert-node</tt> or a <tt>fb:insert-bean</tt> binding (see the
-descriptions of these binding elements for more details).</p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">fb:identity</h2><p>Child elements:</p><ul>
+descriptions of these binding elements for more details).</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">fb:identity</h2><p>Child elements:</p><ul>
<li>fb:value widget bindings constituting the repeater row identity</li>
</ul>The <tt><fb:identity></tt> is just a container for the child elements
specifying the bindings of the row identity widgets.<p>The nested elements just describe regular value bindings (these can declare
@@ -720,18 +718,18 @@
don't need the identity widget(s) at the client, you don't need to add them to
the template at all! This prevents, e.g., database IDs from getting to the
client.</p><p><strong>NOTE:</strong> This 'identity' binding is only active in the 'load'
-operation, so specifying the direction="save" is meaningless.</p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">fb:set-attribute</h2><p>Attributes:</p><ul>
+operation, so specifying the direction="save" is meaningless.</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">fb:set-attribute</h2><p>Attributes:</p><ul>
<li>name</li>
<li>value</li>
<li>direction (optional)</li>
</ul>Child elements: noneSet the value of the attribute specified in the <tt>name</tt> attribute to
the fixed string value specified in the <tt>value</tt> attribute.<strong>NOTE:</strong> This binding is never active in the 'load' operation,
so there is no need to specify the <tt>direction="save"</tt> to protect you
-model from being changed during load.<h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">fb:delete-node</h2><p>Attributes:</p><ul>
+model from being changed during load.<h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">fb:delete-node</h2><p>Attributes:</p><ul>
<li>direction (optional)</li>
</ul>Child elements: none<p>Deletes the current context node.</p><p><strong>NOTE:</strong> This binding is never active in the 'load' operation,
so there is no need to specify the <tt>direction="save"</tt> to protect you
-model from being changed during load.</p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">fb:insert-node</h2><p>Attributes:</p><ul>
+model from being changed during load.</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">fb:insert-node</h2><p>Attributes:</p><ul>
<li>src (optional)</li>
<li>xpath (optional, only in combination with src)</li>
<li>direction (optional)</li>
@@ -742,7 +740,7 @@
element. In this last case, you can also supply an xpath attribute to select a
specific element from the retrieved source.<p><strong>NOTE:</strong> This binding is never active in the 'load' operation,
so there is no need to specify the <tt>direction="save"</tt> to protect you
-model from being changed during load.</p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">fb:insert-bean</h2><p>Attributes:</p><ul>
+model from being changed during load.</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">fb:insert-bean</h2><p>Attributes:</p><ul>
<li>addmethod</li>
<li>classname (optional)</li>
<li>direction (optional)</li>
@@ -753,7 +751,7 @@
argument. If classname is not specified it will just call the addmethod (e.g. if
the addmethod creates the new instance itself).<strong>NOTE:</strong> This binding is never active in the 'load' operation,
so there is no need to specify the <tt>direction="save"</tt> to protect you
-model from being changed during load.<h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">fb:simple-repeater</h2><p>Attributes:</p><ul>
+model from being changed during load.<h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">fb:simple-repeater</h2><p>Attributes:</p><ul>
<li>id</li>
<li>parent-path (same as in fb:repeater)</li>
<li>row-path (same as in fb:repeater)</li>
@@ -762,7 +760,7 @@
<li>direction (optional)</li>
</ul>Child elements: anyA simple repeater binding that will replace (i.e. delete then re-add all) its
content.Works with XML or with JavaBeans if a JXPath factory is set on the binding
-context.<h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">fb:javascript</h2>Attributes:<ul>
+context.<h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">fb:javascript</h2>Attributes:<ul>
<li>id</li>
<li>path</li>
<li>direction (optional)</li>
@@ -804,7 +802,7 @@
<li>The <tt>@readonly</tt> attribute supported in early versions of this binding
has been replaced by the @direction attribute as supported now on all binding
elements.</li>
-</ul><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">fb:custom</h2>Attributes:<ul>
+</ul><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">fb:custom</h2>Attributes:<ul>
<li>id (optional, if not provided the containing widget-context will be passed)
</li>
<li>path (optional, if not provided "." is assumed)</li>
Modified: cocoon/site/site/2.2/blocks/forms/1.0/489_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/blocks/forms/1.0/489_1_1.html?rev=677225&r1=677224&r2=677225&view=diff
==============================================================================
--- cocoon/site/site/2.2/blocks/forms/1.0/489_1_1.html (original)
+++ cocoon/site/site/2.2/blocks/forms/1.0/489_1_1.html Wed Jul 16 03:10:42 2008
@@ -330,8 +330,6 @@
-
-
<li class='menuCollapse'>
<a href="project-reports.html">Project Reports</a>
@@ -339,7 +337,7 @@
</ul>
</li>
</ul>
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Introduction</h1><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Introduction</h1><p>Cocoon has an advanced forms framework. Together with Flow and JXTemplates,
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Introduction</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Introduction</h1><p>Cocoon has an advanced forms framework. Together with Flow and JXTemplates,
Cocoon Forms (or <strong>CForms</strong>) provides a solid basis for building
interactive web applications. Cocoon Forms handles complex use cases while still
being simple enough to be used by non-Java-programmers who want to add forms to
Modified: cocoon/site/site/2.2/blocks/forms/1.0/490_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/blocks/forms/1.0/490_1_1.html?rev=677225&r1=677224&r2=677225&view=diff
==============================================================================
--- cocoon/site/site/2.2/blocks/forms/1.0/490_1_1.html (original)
+++ cocoon/site/site/2.2/blocks/forms/1.0/490_1_1.html Wed Jul 16 03:10:42 2008
@@ -394,8 +394,6 @@
-
-
<li class='menuCollapse'>
<a href="project-reports.html">Project Reports</a>
@@ -403,7 +401,7 @@
</ul>
</li>
</ul>
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">MultiValueField widget</h1><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Concept</h1><p>The fd:multivaluefield is similar to the <a href="481_1_1.html">field widget</a>
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">MultiValueField widget</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Concept</h1><p>The fd:multivaluefield is similar to the <a href="481_1_1.html">field widget</a>
but can take multiple values. Its purpose is to handle those (HTML) form
controls which submit their multiple values as multiple (HTTP) request
parameters with the same name.</p><div class="note"><div><strong>Note: </strong>Before Cocoon 2.1.8, multivaluefields required a selection list,
@@ -412,7 +410,7 @@
multivaluefield styling is available.</div></div><p>The multivaluefield can be rendered in various ways, as described in the
styling section.</p><p>The setValue and getValue methods of the multivaluefield take, respectively
return, arrays of objects (i.e. Object[]). The type of the objects in these
-arrays should match the datatype declared for the widget.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Definition</h1><pre><fd:multivaluefield id="..." state="...">
+arrays should match the datatype declared for the widget.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Definition</h1><pre><fd:multivaluefield id="..." state="...">
<fd:label>...</fd:label>
<fd:help>...</fd:help>
<fd:hint>...</fd:hint>
@@ -437,9 +435,9 @@
</fd:multivaluefield></pre><p>Most of the elements and attributes have the same meaning as for the
<a href="481_1_1.html">field</a> widget.</p><p>Note: A multivaluefield cannot have a required attribute, instead you should
use the value-count <a href="484_1_1.html">validator</a> to check the number of
-values the user has selected.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Template</h1><p>A multivaluefield is inserted into a template using the normal
+values the user has selected.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Template</h1><p>A multivaluefield is inserted into a template using the normal
<tt>ft:widget</tt> tag:</p><pre><ft:widget id="..."/>
-</pre><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Styling (default HTML XSL)</h1><p>If the multivaluefield has a selection list, it will by default be rendered
+</pre><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Styling (default HTML XSL)</h1><p>If the multivaluefield has a selection list, it will by default be rendered
as a list in which multiple items can be selected. Alternative, more
user-friendly styling options are also possible.</p><p>Rendering the multivaluefield as two listboxes between which the items can be
moved:</p><pre><ft:widget id="...">
@@ -456,7 +454,7 @@
when pressing enter they are added to the listbox. Items can be deleted by
selecting them and pressing the delete button. The items can be rearranged by
selecting them and using ctrl+up/down arrow. An existing item can be edited by
-selecting it, editing the value and pressing ctrl+enter.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">API notes</h1><p>As mentioned above, the value of multivaluefield widget is a Java array. So
+selecting it, editing the value and pressing ctrl+enter.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">API notes</h1><p>As mentioned above, the value of multivaluefield widget is a Java array. So
when using the API from javascript, you also need to create a Java array. For
example, if the datatype of the field is "long", you could create an array as
follows:</p><pre>var values = java.lang.reflect.Array.newInstance(java.lang.Long.TYPE, 3);
Modified: cocoon/site/site/2.2/blocks/forms/1.0/491_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/blocks/forms/1.0/491_1_1.html?rev=677225&r1=677224&r2=677225&view=diff
==============================================================================
--- cocoon/site/site/2.2/blocks/forms/1.0/491_1_1.html (original)
+++ cocoon/site/site/2.2/blocks/forms/1.0/491_1_1.html Wed Jul 16 03:10:42 2008
@@ -322,8 +322,6 @@
-
-
<li class='menuCollapse'>
<a href="project-reports.html">Project Reports</a>
@@ -331,7 +329,7 @@
</ul>
</li>
</ul>
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Cocoon Forms: Javascript API</h1><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Javascript API</h1><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Introduction</h2><p>This API lets you manipulate Cocoon Forms using Flowacript</p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Widgets</h2><p>A Form is basically a collection of Widgets, and this API lets you get a
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Cocoon Forms: Javascript API</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Javascript API</h1><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Introduction</h2><p>This API lets you manipulate Cocoon Forms using Flowacript</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Widgets</h2><p>A Form is basically a collection of Widgets, and this API lets you get a
reference to a single widget (using getChild or lookupWidget methods of the Form
objects) and manipulate it using the
<a href="http://cocoon.apache.org/2.2/blocks/forms/1.0/apidocs/org/apache/cocoon/forms/formmodel/Widget.html">Widget
@@ -339,18 +337,18 @@
interface using the getModel method. To set the state of a Widget, the
<a href="http://cocoon.apache.org/2.2/blocks/forms/1.0/apidocs/org/apache/cocoon/forms/formmodel/WidgetState.html">WidgeState
class</a> has to be imported, with this statement:</p><pre>importClass(org.apache.cocoon.forms.formmodel.WidgetState);</pre><p>While the state is set with <tt>setState</tt> method, like in:</p><pre>form1.getChild("msg").setState(WidgetState.OUTPUT);
-</pre><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Form object reference</h2><h3 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Constructors</h3><h4 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Form(formDef)</h4><p>Is the Formo object cxontructor.</p><p><tt>formDef</tt> is the form definition XML, which could be expressed as an
-URI, Source or DOM.</p><h3 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Properties</h3><h4 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">isValid</h4><p>Set to true if theuser input has successfily passed validation, false
-otherwise.</p><h4 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">submitId</h4><p>It is the id of the widget that triggered the form submit (can be null).</p><h4 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">locale</h4><p>The form locale (default locale is used if not set).</p><h4 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">cleanupHook</h4><p>It is a function called after having sent the page displaying the form. This
+</pre><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Form object reference</h2><h3 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Constructors</h3><h4 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Form(formDef)</h4><p>Is the Formo object cxontructor.</p><p><tt>formDef</tt> is the form definition XML, which could be expressed as an
+URI, Source or DOM.</p><h3 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Properties</h3><h4 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">isValid</h4><p>Set to true if theuser input has successfily passed validation, false
+otherwise.</p><h4 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">submitId</h4><p>It is the id of the widget that triggered the form submit (can be null).</p><h4 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">locale</h4><p>The form locale (default locale is used if not set).</p><h4 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">cleanupHook</h4><p>It is a function called after having sent the page displaying the form. This
is equivalent to the "fun" argument of sendPageAndWait(), which allows to
perform some cleanup when the pipeline has been processed. The function <br></br>
-is called with a single parameter which is the form it is attached to.</p><h4 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">cleanupHook</h4><p>It is a function called before processing the form when it has been submitted
+is called with a single parameter which is the form it is attached to.</p><h4 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">cleanupHook</h4><p>It is a function called before processing the form when it has been submitted
by the browser. This allows to restore some environment that is needed by the
form processing. The function is called with a single parameter which is the
-form it is attached to.</p><h3 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Methods</h3><h4 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">getModel()</h4><p>Returns the form as a Widget Java class.</p><h4 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">getChild(id)</h4><p>Returns a widget (as a Widget Java class) given its id</p><p><tt>id</tt> widget id.</p><h4 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">lookupWidget(path)</h4><p>Returns a widget (as a Widget Java class) given its path</p><p><tt>path</tt> widget path.</p><h4 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">showForm(uri, viewData, ttl)</h4><p>Returns a widget (as a Widget Java class) given its path</p><p><tt>uri</tt> the page uri (like in cocoon.sendPageAndWait()).</p><p><tt>viewData</tt> some data for the view
(like in cocoon.sendPageAndWait()).
+form it is attached to.</p><h3 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Methods</h3><h4 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">getModel()</h4><p>Returns the form as a Widget Java class.</p><h4 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">getChild(id)</h4><p>Returns a widget (as a Widget Java class) given its id</p><p><tt>id</tt> widget id.</p><h4 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">lookupWidget(path)</h4><p>Returns a widget (as a Widget Java class) given its path</p><p><tt>path</tt> widget path.</p><h4 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">showForm(uri, viewData, ttl)</h4><p>Returns a widget (as a Widget Java class) given its path</p><p><tt>uri</tt> the page uri (like in cocoon.sendPageAndWait()).</p><p><tt>viewData</tt> some data for the view
(like in cocoon.sendPageAndWait()).
The "{FormsPipelineConfig.CFORMSKEY}" and "locale" properties are added to this
object.</p><p><tt>ttl</tt> the time to live of the continuation used to display the form.
-</p><h4 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">sendForm </h4><p>Show form statelessly, without creating a continuation.<br></br>
+</p><h4 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">sendForm </h4><p>Show form statelessly, without creating a continuation.<br></br>
<tt>uri</tt> the page uri (like in cocoon.sendPageAndWait())<br></br>
<tt>viewdata</tt> some data for the view (like in cocoon.sendPageAndWait()).</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/491?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
Modified: cocoon/site/site/2.2/blocks/forms/1.0/492_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/blocks/forms/1.0/492_1_1.html?rev=677225&r1=677224&r2=677225&view=diff
==============================================================================
--- cocoon/site/site/2.2/blocks/forms/1.0/492_1_1.html (original)
+++ cocoon/site/site/2.2/blocks/forms/1.0/492_1_1.html Wed Jul 16 03:10:42 2008
@@ -394,8 +394,6 @@
-
-
<li class='menuCollapse'>
<a href="project-reports.html">Project Reports</a>
@@ -403,7 +401,7 @@
</ul>
</li>
</ul>
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Output widget</h1><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Concept</h1><p>An fd:output widget is similar to a field widget, but its value is not
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Output widget</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Concept</h1><p>An fd:output widget is similar to a field widget, but its value is not
editable. The value of an output widget must be set programmatically (or through
binding). An output widget does not read its value from the request, so is most
useful in the case where the form is stored accross requests (automatically the
@@ -413,7 +411,7 @@
</div></div><p><strong>Possible alternative:</strong> On each widget you can also store
additional information (i.e. arbitrary Java objects) in attributes. See the Java
API of the Widget interface, methods setAttribute and getAttribute. You can then
-retrieve these attributes using the JXTemplate generator.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Definition</h1><pre><fd:output id="..." state="...">
+retrieve these attributes using the JXTemplate generator.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Definition</h1><pre><fd:output id="..." state="...">
<fd:label>...</fd:label>
<fd:help>...</fd:help>
<fd:hint>...</fd:hint>
@@ -428,7 +426,7 @@
<fd:attribute name="..." value="..."/>
</fd:attributes>
</fd:output></pre><p>See <a href="481_1_1.html">field widget</a> for a description of the
-configuration elements.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Template</h1><p>An output widget is inserted in a template using the ft:widget tag:</p><pre><ft:widget id="..."/>
+configuration elements.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Template</h1><p>An output widget is inserted in a template using the ft:widget tag:</p><pre><ft:widget id="..."/>
</pre></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/492?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
</div></div></div>
Modified: cocoon/site/site/2.2/blocks/forms/1.0/493_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/blocks/forms/1.0/493_1_1.html?rev=677225&r1=677224&r2=677225&view=diff
==============================================================================
--- cocoon/site/site/2.2/blocks/forms/1.0/493_1_1.html (original)
+++ cocoon/site/site/2.2/blocks/forms/1.0/493_1_1.html Wed Jul 16 03:10:42 2008
@@ -394,8 +394,6 @@
-
-
<li class='menuCollapse'>
<a href="project-reports.html">Project Reports</a>
@@ -403,7 +401,7 @@
</ul>
</li>
</ul>
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Submit widget</h1><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Concept</h1><p>The submit widget, usually rendered as a button, is used by the user to
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Submit widget</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Concept</h1><p>The submit widget, usually rendered as a button, is used by the user to
submit the form. The submit widget is a special kind of action widget, thus also
has the same functionality as an action widget, however the submit widget does
trigger validation and its purpose is to end the form.</p><p>You don't need to use a submit widget to submit a form. For example, in your
@@ -418,7 +416,7 @@
<tt><fi:styling submit-on-change="true"/></tt> in the form template (see
<a href="485_1_1.html">XSLT</a> for more information on the <tt>fi:styling</tt>
directive).</p><p>To know which widget caused the form to be submitted, use the method
-<tt>getSubmitWidget</tt> of the <tt>Form</tt> object.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Definition</h1><pre><fd:submit id="..." command="..." validate="true|false" state="...">
+<tt>getSubmitWidget</tt> of the <tt>Form</tt> object.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Definition</h1><pre><fd:submit id="..." command="..." validate="true|false" state="...">
<fd:label>...</fd:label>
<fd:help>...</fd:help>
<fd:hint>...</fd:hint>
@@ -437,7 +435,7 @@
form processing, thus the form will not be redisplayed. Ultimately, it is of
course the controller who decides this, but the forms hint towards the
controller is that it shouldn't be redisplayed, and this is exactly what the
-flowscript integration library does.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Template & styling</h1><p>See the <a href="477_1_1.html">action widget</a>.</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
+flowscript integration library does.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Template & styling</h1><p>See the <a href="477_1_1.html">action widget</a>.</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/493?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
</div></div></div>
</div>
Modified: cocoon/site/site/2.2/blocks/forms/1.0/494_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/blocks/forms/1.0/494_1_1.html?rev=677225&r1=677224&r2=677225&view=diff
==============================================================================
--- cocoon/site/site/2.2/blocks/forms/1.0/494_1_1.html (original)
+++ cocoon/site/site/2.2/blocks/forms/1.0/494_1_1.html Wed Jul 16 03:10:42 2008
@@ -394,8 +394,6 @@
-
-
<li class='menuCollapse'>
<a href="project-reports.html">Project Reports</a>
@@ -403,8 +401,8 @@
</ul>
</li>
</ul>
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">RepeaterAction widget</h1><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Concept</h1><p>This is a specific type of <a href="477_1_1.html">action widget</a> that handles
-the much needed case of adding or removing rows from a repeater.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Definition</h1><pre><fd:repeater-action id="..." command="delete-rows|add-row" number-of-rows="..." repeater="..." select="..." state="...">
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">RepeaterAction widget</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Concept</h1><p>This is a specific type of <a href="477_1_1.html">action widget</a> that handles
+the much needed case of adding or removing rows from a repeater.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Definition</h1><pre><fd:repeater-action id="..." command="delete-rows|add-row" number-of-rows="..." repeater="..." select="..." state="...">
<fd:label>...</fd:label>
<fd:help>...</fd:help>
<fd:hint>...</fd:hint>
@@ -434,7 +432,7 @@
is <tt>org.apache.cocoon.forms.event.ActionEvent</tt>. The event handlers are
called <em>after</em> the action is performed except for the
<tt>delete-rows</tt> action where event handlers are called <em>before</em> the
-selected rows are deleted.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Template & styling</h1><p>See the <a href="477_1_1.html">action widget</a>.</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
+selected rows are deleted.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Template & styling</h1><p>See the <a href="477_1_1.html">action widget</a>.</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/494?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
</div></div></div>
</div>
Modified: cocoon/site/site/2.2/blocks/forms/1.0/495_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/blocks/forms/1.0/495_1_1.html?rev=677225&r1=677224&r2=677225&view=diff
==============================================================================
--- cocoon/site/site/2.2/blocks/forms/1.0/495_1_1.html (original)
+++ cocoon/site/site/2.2/blocks/forms/1.0/495_1_1.html Wed Jul 16 03:10:42 2008
@@ -394,8 +394,6 @@
-
-
<li class='menuCollapse'>
<a href="project-reports.html">Project Reports</a>
@@ -403,10 +401,10 @@
</ul>
</li>
</ul>
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">RowAction widget</h1><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Concept</h1><p>This is a specific type of <a href="477_1_1.html">action widget</a> that handles
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">RowAction widget</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Concept</h1><p>This is a specific type of <a href="477_1_1.html">action widget</a> that handles
frequent actions occuring on a repeater row, such as adding/removing a row and
moving it up and down. These widgets should be placed inside a repeater and act
-on the current row.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Definition</h1><pre><fd:row-action id="..." command="add-after|delete|move-up|move-down" state="...">
+on the current row.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Definition</h1><pre><fd:row-action id="..." command="add-after|delete|move-up|move-down" state="...">
<fd:label>...</fd:label>
<fd:help>...</fd:help>
<fd:hint>...</fd:hint>
@@ -433,7 +431,7 @@
event.getSourceWidget().getParent(), or from the flow using
form.getWidget().getSubmitWidget().getParent(). The row itself has a
lookupWidget(widgetName) method that can be used to access specific widgets for
-the row.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Template & styling</h1><p>See the <a href="477_1_1.html">action widget</a>.</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
+the row.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Template & styling</h1><p>See the <a href="477_1_1.html">action widget</a>.</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/495?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
</div></div></div>
</div>
Modified: cocoon/site/site/2.2/blocks/forms/1.0/496_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/blocks/forms/1.0/496_1_1.html?rev=677225&r1=677224&r2=677225&view=diff
==============================================================================
--- cocoon/site/site/2.2/blocks/forms/1.0/496_1_1.html (original)
+++ cocoon/site/site/2.2/blocks/forms/1.0/496_1_1.html Wed Jul 16 03:10:42 2008
@@ -394,8 +394,6 @@
-
-
<li class='menuCollapse'>
<a href="project-reports.html">Project Reports</a>
@@ -403,8 +401,8 @@
</ul>
</li>
</ul>
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Repeater widget</h1><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Concept</h1><p>An fd:repeater widget is a widget that repeats a number of other widgets. It
-can be used to create e.g. tables, repeating subforms, etc.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Definition</h1><pre><fd:repeater id="..." initial-size="..." min-size="..." max-size="..." state="...">
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Repeater widget</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Concept</h1><p>An fd:repeater widget is a widget that repeats a number of other widgets. It
+can be used to create e.g. tables, repeating subforms, etc.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Definition</h1><pre><fd:repeater id="..." initial-size="..." min-size="..." max-size="..." state="...">
<fd:label>...</fd:label>
<fd:hint>...</fd:hint>
<fd:help>...</fd:help>
@@ -438,7 +436,7 @@
<tt>ROWS_CLEARING</tt> before the action actually takes place, and the
<tt><tt>ROW_DELETED</tt></tt> or <tt>ROWS_CLEARED</tt> after the row has
actually been deleted or the repeater has actually been cleared.</p><p>For a description of the other elements, see the <a href="481_1_1.html">field
-widget</a>.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Template</h1><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Before Cocoon 2.1.8</h2><p>The following elements are available for formatting a repeater in a template:
+widget</a>.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Template</h1><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Before Cocoon 2.1.8</h2><p>The following elements are available for formatting a repeater in a template:
</p><ul>
<li><tt>ft:repeater-widget</tt>: the content of this element is a template that
will be executed for each row in the repeater</li>
@@ -464,7 +462,7 @@
</ft:repeater-widget>
</tbody>
</table>
-</pre><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">From Cocoon 2.1.8</h2>Cocoon 2.1.8 introduced a slightly extended manner to format repeaters, which
+</pre><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">From Cocoon 2.1.8</h2>Cocoon 2.1.8 introduced a slightly extended manner to format repeaters, which
is required when using the new <a href="750_1_1.html">Ajax</a> features. Instead of
one ft:repeater-widget element, it uses two elements:<ul>
<li><tt>ft:repeater</tt>: encloses the entire formatted repeater</li>
@@ -487,7 +485,7 @@
</tbody>
</table>
</ft:repeater>
-</pre><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Tips</h2>When using JXTemplate, it is possible to test if a repeater is empty and show
+</pre><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Tips</h2>When using JXTemplate, it is possible to test if a repeater is empty and show
something else in that case. For example:<pre><jx:choose>
<jx:when test="${widget.getChild('myrepeater').getSize() == 0}">
No items yet.
Modified: cocoon/site/site/2.2/blocks/forms/1.0/497_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/blocks/forms/1.0/497_1_1.html?rev=677225&r1=677224&r2=677225&view=diff
==============================================================================
--- cocoon/site/site/2.2/blocks/forms/1.0/497_1_1.html (original)
+++ cocoon/site/site/2.2/blocks/forms/1.0/497_1_1.html Wed Jul 16 03:10:42 2008
@@ -394,8 +394,6 @@
-
-
<li class='menuCollapse'>
<a href="project-reports.html">Project Reports</a>
@@ -403,13 +401,13 @@
</ul>
</li>
</ul>
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Messages widget</h1><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Concept</h1><p>A widget to output one or messages. This widget doesn't respond to input from
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Messages widget</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Concept</h1><p>A widget to output one or messages. This widget doesn't respond to input from
the user, except that on each form submit the messages are cleared.</p><p>This widget is typically used to communicate extra messages to the user, that
-aren't associated with any other widget in particular.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Definition</h1><pre><fd:messages id="..." state="...">
+aren't associated with any other widget in particular.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Definition</h1><pre><fd:messages id="..." state="...">
</fd:messages>
</pre><p>While the fd:messages widget can have validators etc., this probably does not
-make much sense for this widget so they are not mentioned above.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Template</h1><p>A messages widget is inserted in a template using the ft:widget tag:</p><pre><ft:widget id="..."/>
-</pre><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Styling (default HTML XSL)</h1><p>The messages are rendered as an unordered list.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">API</h1><p>Messages are added using the <tt>addMessage</tt> method on this widget. The
+make much sense for this widget so they are not mentioned above.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Template</h1><p>A messages widget is inserted in a template using the ft:widget tag:</p><pre><ft:widget id="..."/>
+</pre><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Styling (default HTML XSL)</h1><p>The messages are rendered as an unordered list.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">API</h1><p>Messages are added using the <tt>addMessage</tt> method on this widget. The
argument can be a string, but also any object implementing the XMLizable
interface, for example <tt>org.apache.cocoon.forms.util.I18nMessage</tt>.</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/497?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
Modified: cocoon/site/site/2.2/blocks/forms/1.0/498_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/blocks/forms/1.0/498_1_1.html?rev=677225&r1=677224&r2=677225&view=diff
==============================================================================
--- cocoon/site/site/2.2/blocks/forms/1.0/498_1_1.html (original)
+++ cocoon/site/site/2.2/blocks/forms/1.0/498_1_1.html Wed Jul 16 03:10:42 2008
@@ -322,8 +322,6 @@
-
-
<li class='menuCollapse'>
<a href="project-reports.html">Project Reports</a>
@@ -331,21 +329,21 @@
</ul>
</li>
</ul>
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Java API</h1><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Intro</h1><p>CForms is implemented in Java so the natural way to access it is through its
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Java API</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Intro</h1><p>CForms is implemented in Java so the natural way to access it is through its
Java API. In this section we will show you how to get started. The two primary
flow-solutions of Cocoon (Flowscript and Javaflow) each have an additional Forms
integration part. However, here we want to show how the core Forms APIs should
be used independent of specific flow solutions, and therefore we will use the
very basic "Apples" flow.</p><div class="note"><div><strong>Note: </strong>The Apples flow solution (contained in the "apples" block) is
not officially supported by the Cocoon community. We use it here only for
-demonstrative purposes to illustrate the use of the Forms API.</div></div><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Apples flow</h1><p>If you are familiar with Apples, you can skip this section. What follows is a
+demonstrative purposes to illustrate the use of the Forms API.</div></div><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Apples flow</h1><p>If you are familiar with Apples, you can skip this section. What follows is a
super-super short summary of how Apples works.</p><p>An Apple flow-controller is a Java class implementing the following
interface:</p><pre>package org.apache.cocoon.components.flow.apples;
public interface AppleController {
void process(AppleRequest req, AppleResponse res) throws Exception;
}</pre><p>In the sitemap, a flow-interaction is started using map:call with the
-function attribute:</p><pre><map:call function="<em xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">some.fully.qualified.Classname</em>"/></pre><p>This will create an instance of the specified class (which should implement
+function attribute:</p><pre><map:call function="<em xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">some.fully.qualified.Classname</em>"/></pre><p>This will create an instance of the specified class (which should implement
the AppleController interface), associate that class with a continuation ID, and
call the <tt>process</tt> method of the Apple (we refer to a specific Apples
controller object simply as "Apple"). The Apple can then do whathever it wants
@@ -356,7 +354,7 @@
only configures what pipeline to call or where to redirect to in the
AppleResponse object. It is only after the process method has returned that this
information will be used by the Apples flow implementation.</p><p>To continue interacting with the same Apple instance, use map:call with the
-contination attribute:</p><pre><map:call continuation="<em xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">some-continuation-id</em>"/></pre><p>This will look up the previously created Apple and call again its process
+contination attribute:</p><pre><map:call continuation="<em xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">some-continuation-id</em>"/></pre><p>This will look up the previously created Apple and call again its process
method.</p><p>This is basically it. An Apple can maintain state in its instance variables.
You can think of an Apple object as a session specific for a certain
interaction. It encapsulates both the state of the interaction and its
@@ -366,7 +364,7 @@
parameters and the request method).</p><p>To make this overview complete, if you don't need a stateful interaction you
can let your Apple implement the interface <tt>StatelessAppleController</tt>. In
that case, no continuation ID will be associated with the Apple and it will be
-discarded directly after use.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Avalon</h1><p>An Apples controller can implement the Avalon Framework interfaces to get
+discarded directly after use.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Avalon</h1><p>An Apples controller can implement the Avalon Framework interfaces to get
access to its context. If you are familiar with Avalon, you can skip this
section.</p><p>Cocoon internally manages components using the contracts defined by Avalon
Framework. Avalon Framework defines a few interfaces that components can
@@ -379,9 +377,9 @@
this service method will be called during the setup of the component, and via
the supplied ServiceManager object you can get access to other components
running inside Cocoon. We will see below how we use this to get access to the
-FormManager.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Setting up a working environment</h1><p>To have a comfortable work/build environment, we suggest to use the
+FormManager.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Setting up a working environment</h1><p>To have a comfortable work/build environment, we suggest to use the
<a href="http://wiki.apache.org/cocoon/YourCocoonBasedProjectAnt16">Ant script
-found on the wiki</a>.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">A basic Forms usage</h1><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Creating a form instance</h2><p>Creating a form instance based on a form definition is done using the
+found on the wiki</a>.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">A basic Forms usage</h1><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Creating a form instance</h2><p>Creating a form instance based on a form definition is done using the
FormManager. Since the few lines to do this are needed each time we would like
to create a form instance, we define a helper class to do this. While at it, it
includes also a method to create a binding object using the BindingManager.</p><pre>package my;
@@ -417,7 +415,7 @@
}
}
}
-</pre><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">The Apple controller</h2><p>Below is an Apple controller which is used to display a simple form
+</pre><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">The Apple controller</h2><p>Below is an Apple controller which is used to display a simple form
containing just one field, "name". Once the name is entered correctly, it will
redirect to google to perform a search on that name.</p><pre>package my;
@@ -491,8 +489,8 @@
redirect to google.</li>
</ul>It is important to notice that you can make the form definition and template
much more complex (containing many & advanced widgets, with validation
-logic, event handlers, etc.), while the Apple can stay as simple as this.<h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Supporting files</h2>For reference, we list the form definition, form template and sitemap used
-for this example.<h3 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">form definition</h3><pre><fd:form xmlns:fd="http://apache.org/cocoon/forms/1.0#definition">
+logic, event handlers, etc.), while the Apple can stay as simple as this.<h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Supporting files</h2>For reference, we list the form definition, form template and sitemap used
+for this example.<h3 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">form definition</h3><pre><fd:form xmlns:fd="http://apache.org/cocoon/forms/1.0#definition">
<fd:widgets>
<fd:field id="name" required="true">
<fd:label>Name</fd:label>
@@ -500,7 +498,7 @@
</fd:field>
</fd:widgets>
</fd:form>
-</pre><h3 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">form template</h3><pre><html xmlns:ft="http://apache.org/cocoon/forms/1.0#template"
+</pre><h3 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">form template</h3><pre><html xmlns:ft="http://apache.org/cocoon/forms/1.0#template"
xmlns:fi="http://apache.org/cocoon/forms/1.0#instance"
xmlns:jx="http://apache.org/cocoon/templates/jx/1.0">
@@ -518,7 +516,7 @@
</ft:form-template>
</body>
</html>
-</pre><h3 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">sitemap</h3><pre><?xml version="1.0"?>
+</pre><h3 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">sitemap</h3><pre><?xml version="1.0"?>
<map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
<map:components>
@@ -572,7 +570,7 @@
</map:pipelines>
</map:sitemap>
-</pre><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Next</h1>[TODO]<p>See also the javadoc of the forms package for more information on the API.
+</pre><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Next</h1>[TODO]<p>See also the javadoc of the forms package for more information on the API.
</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/498?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
</div></div></div>
Modified: cocoon/site/site/2.2/blocks/forms/1.0/685_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/blocks/forms/1.0/685_1_1.html?rev=677225&r1=677224&r2=677225&view=diff
==============================================================================
--- cocoon/site/site/2.2/blocks/forms/1.0/685_1_1.html (original)
+++ cocoon/site/site/2.2/blocks/forms/1.0/685_1_1.html Wed Jul 16 03:10:42 2008
@@ -318,8 +318,6 @@
-
-
<li class='menuCollapse'>
<a href="project-reports.html">Project Reports</a>
@@ -367,7 +365,7 @@
</fd:selection-list>
</fd:field></pre><div class="note"><div><strong>Note: </strong>Note that "extends" does not have to reference widgets in a
library, widgets in the same context are also usable (e.g. widgets in the same
-group or two top-level widgets can inherit from another).</div></div><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Form Library Inclusion</h2><p>A sample library <tt>sample.xml</tt> might look like this:</p><pre><fd:library>
+group or two top-level widgets can inherit from another).</div></div><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Form Library Inclusion</h2><p>A sample library <tt>sample.xml</tt> might look like this:</p><pre><fd:library>
<fd:widgets>
<fd:group id="account">
Modified: cocoon/site/site/2.2/blocks/forms/1.0/733_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/blocks/forms/1.0/733_1_1.html?rev=677225&r1=677224&r2=677225&view=diff
==============================================================================
--- cocoon/site/site/2.2/blocks/forms/1.0/733_1_1.html (original)
+++ cocoon/site/site/2.2/blocks/forms/1.0/733_1_1.html Wed Jul 16 03:10:42 2008
@@ -334,8 +334,6 @@
-
-
<li class='menuCollapse'>
<a href="project-reports.html">Project Reports</a>
Modified: cocoon/site/site/2.2/blocks/forms/1.0/738_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/blocks/forms/1.0/738_1_1.html?rev=677225&r1=677224&r2=677225&view=diff
==============================================================================
--- cocoon/site/site/2.2/blocks/forms/1.0/738_1_1.html (original)
+++ cocoon/site/site/2.2/blocks/forms/1.0/738_1_1.html Wed Jul 16 03:10:42 2008
@@ -394,8 +394,6 @@
-
-
<li class='menuCollapse'>
<a href="project-reports.html">Project Reports</a>
@@ -403,21 +401,21 @@
</ul>
</li>
</ul>
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">ImageMap widget</h1><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Concept</h1><p>It is used to display a server-side image map and it triggers an ImageMap
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">ImageMap widget</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Concept</h1><p>It is used to display a server-side image map and it triggers an ImageMap
event on the server side when clicked.<br></br>
It behaves much as an Action widget, but you can bind the source URI of the
image using the binding framework "<tt>fb:value</tt>" element, set the image at
runtime using the <tt>setImageURI()</tt> method, and retrieve the mouse
-coordinates with <tt>getX(</tt>) and <tt>getY()</tt> methods.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Definition</h1><pre><fd:imagemap id="map">
+coordinates with <tt>getX(</tt>) and <tt>getY()</tt> methods.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Definition</h1><pre><fd:imagemap id="map">
<fd:imageuri>test.gif</fd:imageuri>
<fd:hint>Click on this map to zoom-in</fd:hint>
<fd:on-action>
<javascript>onClickMap(event);</javascript>
</fd:on-action>
-</fd:imagemap></pre><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Binding</h1><pre><fb:value id="map" path="@src"/></pre><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Template</h1><pre><ft:widget id="map">
+</fd:imagemap></pre><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Binding</h1><pre><fb:value id="map" path="@src"/></pre><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Template</h1><pre><ft:widget id="map">
<fi:styling xmlns:fi="<a href="http://apache.org/cocoon/forms/1.0#instance">http://apache.org/cocoon/forms/1.0#instance</a>"
border="2"/>
-</ft:widget></pre><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Flow</h1><p>This is another way to set the image URI:</p><pre>frm.getWidget().lookupWidget("map").setImageURI("test2.gif");</pre><p>This is the handler of the imagemap event:</p><pre>function onClickMap (event) {
+</ft:widget></pre><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Flow</h1><p>This is another way to set the image URI:</p><pre>frm.getWidget().lookupWidget("map").setImageURI("test2.gif");</pre><p>This is the handler of the imagemap event:</p><pre>function onClickMap (event) {
var x= event.getX();
var y= event.getY();
Modified: cocoon/site/site/2.2/blocks/forms/1.0/739_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/blocks/forms/1.0/739_1_1.html?rev=677225&r1=677224&r2=677225&view=diff
==============================================================================
--- cocoon/site/site/2.2/blocks/forms/1.0/739_1_1.html (original)
+++ cocoon/site/site/2.2/blocks/forms/1.0/739_1_1.html Wed Jul 16 03:10:42 2008
@@ -394,8 +394,6 @@
-
-
<li class='menuCollapse'>
<a href="project-reports.html">Project Reports</a>
@@ -403,9 +401,9 @@
</ul>
</li>
</ul>
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Tree widget</h1><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Concept</h1><p>The tree widget is for displaying trees of "things". The tree widget supports
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Tree widget</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Concept</h1><p>The tree widget is for displaying trees of "things". The tree widget supports
expanding and collapsing of nodes, single or multiple selections, and a flexible
-TreeModel interface to provide its data.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Definition</h1><pre><fd:tree id="..." state="..." root-visible="true" selection="multiple|single">
+TreeModel interface to provide its data.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Definition</h1><pre><fd:tree id="..." state="..." root-visible="true" selection="multiple|single">
<fd:tree-model type="..."/>
<fd:on-selection-changed>
...
@@ -421,14 +419,14 @@
</fd:attributes>
</fd:tree>
</pre><p>All elements and attributes, except for id, are optional.</p><p>See the <a href="481_1_1.html">field widget</a> for information on common
-attributes and elements.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">The tree model</h1><p>See the interface
+attributes and elements.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">The tree model</h1><p>See the interface
<a href="http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/forms/formmodel/tree/TreeModel.html">TreeModel</a>.
Essentially, can be a tree of any sort of objects (there is no interface for the
nodes in the tree). Each parent node should be able to identify its children
uniquely by means of a key (some string).</p><p>CForms ships with two implementations of TreeModel: one generic
implementation (DefaultTreeModel), and one for browsing over Cocoon/Avalon
sources (= filesystem-like structures).</p><p>You can set the form model in the form definition, or set it at runtime using
-the setModel method on the tree widget.</p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Source tree model</h2><p>Syntax:</p><pre><fd:tree-model type="source" src="...">
+the setModel method on the tree widget.</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Source tree model</h2><p>Syntax:</p><pre><fd:tree-model type="source" src="...">
<fd:fileset>
<fd:include pattern="..."/>
<fd:exclude pattern="..."/>
@@ -449,11 +447,11 @@
exclude patterns have higher precendence.</p><p>The patterns are wildcard patterns. They are the same as for the wildcard
matcher in the sitemap, thus simply use a * as wildcard (the ** syntax makes no
sense here, as the pattern is evaluated on individual names, not on full paths).
-</p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Custom models</h2><p>Syntax:</p><pre><fd:tree-model type="java" class="..."/>
+</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Custom models</h2><p>Syntax:</p><pre><fd:tree-model type="java" class="..."/>
</pre><p>whereby the class attribute specifies a class implementing
<a href="http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/forms/formmodel/tree/TreeModel.html">TreeModel</a>.
The class can implement Avalon interfaces to get the Logger, ServiceManager and
-Context.</p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Programmatically assigning a model</h2><p>Here's an example of how to build a tree model programatically using the
+Context.</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Programmatically assigning a model</h2><p>Here's an example of how to build a tree model programatically using the
provided DefaultTreeModel in flowscript:</p><pre>importClass(Packages.org.apache.cocoon.forms.formmodel.tree.DefaultTreeModel);
[...]
@@ -467,7 +465,7 @@
var treeWidget = form.getChild("mytree");
treeWidget.setModel(treeModel);
-</pre><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Template</h1><p>For the display of a tree widget, three special template elements are
+</pre><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Template</h1><p>For the display of a tree widget, three special template elements are
available:</p><ul>
<li><tt>ft:tree</tt>: global element to insert a tree widget in the template.
This also inserts two hidden fields, ":path" and ":action" to communicate a node
@@ -494,11 +492,11 @@
More specifically it is a
<a href="http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/forms/formmodel/tree/TreeWalker.html">TreeWalker</a>
instance. Its <tt>node</tt> property gives access to the actual tree node.</li>
-</ul><div class="note"><div><strong>Note: </strong>The <tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">${treeNode.node.data}</tt> expression in the template
+</ul><div class="note"><div><strong>Note: </strong>The <tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">${treeNode.node.data}</tt> expression in the template
example above is specific to the form model you are using, since the node can be
any object. The data property exists in the DefaultTreeModel nodes, however in
the source tree model the nodes are Source objects, so you would use name
-instead of data.</div></div><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Tree node actions</h1>An action can be executed on a certain node in the tree. The available
+instead of data.</div></div><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Tree node actions</h1>An action can be executed on a certain node in the tree. The available
actions are:<ul>
<li>expand</li>
<li>collapse</li>
@@ -510,9 +508,9 @@
":action" to one of the actions listed above. The node on which the action is
applied is specified in the hidden field named tree-widget-full-name + ":path".
The node is specified as a slash-separated path of node keys. In the template
-you can access this easily with <tt>treeNode.path</tt>.<h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">A more functional template</h1>For a complete example of a tree template, see e.g. the
+you can access this easily with <tt>treeNode.path</tt>.<h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">A more functional template</h1>For a complete example of a tree template, see e.g. the
file_explorer_template.xml file in the CForms samples. From there, you can
-"steal" the styling and the javascript to perform tree node actions.<h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">API notes</h1>See the
+"steal" the styling and the javascript to perform tree node actions.<h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">API notes</h1>See the
<a href="http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/forms/formmodel/tree/Tree.html">API
docs of the tree widgets</a> for more information on how to access e.g. the
selected nodes.</div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
Modified: cocoon/site/site/2.2/blocks/forms/1.0/740_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/blocks/forms/1.0/740_1_1.html?rev=677225&r1=677224&r2=677225&view=diff
==============================================================================
--- cocoon/site/site/2.2/blocks/forms/1.0/740_1_1.html (original)
+++ cocoon/site/site/2.2/blocks/forms/1.0/740_1_1.html Wed Jul 16 03:10:42 2008
@@ -394,8 +394,6 @@
-
-
<li class='menuCollapse'>
<a href="project-reports.html">Project Reports</a>
@@ -403,13 +401,13 @@
</ul>
</li>
</ul>
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Group/Struct widget</h1><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Concept</h1><p>A group widget is simply a container for a number of other widgets. This can
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Group/Struct widget</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Concept</h1><p>A group widget is simply a container for a number of other widgets. This can
be useful to:</p><ul>
<li>change the <a href="733_1_1.html">state</a> of the grouped widgets as a whole
</li>
<li>to use in a <a href="741_1_1.html">union widget</a></li>
<li>....</li>
-</ul>The group widget was previously called struct.<h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Definition</h1><pre><fd:group id="..." state="...">
+</ul>The group widget was previously called struct.<h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Definition</h1><pre><fd:group id="..." state="...">
<fd:widgets>
[...]
</fd:widgets>
@@ -423,12 +421,12 @@
<fd:attribute name="..." value="..."/>
</fd:attributes>
</fd:group>
-</pre><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Template</h1>A group widget is inserted in a template using the ft:group tag. The content
+</pre><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Template</h1>A group widget is inserted in a template using the ft:group tag. The content
of the ft:group widget is the template for the children of the group widget,
thus should contain the template tags for these child widgets.<pre><ft:group id="...">
[...]
</ft:group>
-</pre><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Example</h2>For a definition like this:<pre><fd:group id="mygroup">
+</pre><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Example</h2>For a definition like this:<pre><fd:group id="mygroup">
<fd:widgets>
<fd:field id="field1"/>
<fd:field id="field2"/>
@@ -438,7 +436,7 @@
<br/>
<ft:widget id="field2"/>
</ft:group>
-</pre><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Styling (default HTML XSL)</h1><p>N/A</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
+</pre><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Styling (default HTML XSL)</h1><p>N/A</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/740?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
</div></div></div>
</div>