Author: vkorluzhenko
Date: 2007-08-15 12:08:19 -0400 (Wed, 15 Aug 2007)
New Revision: 2274
Modified:
trunk/docs/userguide/en/src/main/docbook/included/tree.xml
Log:
http://jira.jboss.com/jira/browse/RF-396
Modified: trunk/docs/userguide/en/src/main/docbook/included/tree.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/tree.xml 2007-08-15 16:07:50 UTC
(rev 2273)
+++ trunk/docs/userguide/en/src/main/docbook/included/tree.xml 2007-08-15 16:08:19 UTC
(rev 2274)
@@ -73,11 +73,13 @@
<para>As it has been mentioned above the tree component allows to render any
tree-like structure
of data.</para>
<para>A bean property is passed into a tree
<property>value</property> attribute. The property
- keeps the structure of a org.richfaces.component.TreeNode type. (You could have a
look at this
- interface description in the API document) The default classes for lists building
of a
- TreeNodeImpl type (it implements a TreeNode interface) for an XML structure
XmlNodeData and
- XmlTreeDataBuilder are implemented in the tree component. Hence, in order to
provide your own
- class for TreeNode, it's necessary only to implement this interface, i.e.
the <emphasis>
+ keeps the structure of a org.richfaces.component.TreeNode type (you could have a
look at this
+ interface description in the <ulink
+
url="http://labs.jboss.com/file-access/default/members/jbossrichface...
+ >API document</ulink>). The default classes for lists building of a
TreeNodeImpl type (it
+ implements a TreeNode interface) for an XML structure XmlNodeData and
XmlTreeDataBuilder are
+ implemented in the tree component. Hence, in order to provide your own class for
TreeNode,
+ it's necessary only to implement this interface, i.e. the
<emphasis>
<property>"var"</property>
</emphasis> attribute contains a name providing an access to data defined
with a value. </para>
<para>For data output, named <property>tree</property> nodes
elements are used. Each element,
@@ -160,10 +162,10 @@
</section>
<section>
<title>Built-In Drag and Drop</title>
- <para>The tree component functionalityity provides a built-in support for Drag
and Drop operations.
- The main usage principles are the same as for Rich Faces Drag and Drop wrapper
components.
- Hence, to get additional information on the topic, read the corresponding
chapters:<link
- linkend="dndParam">"rich:dndParam"</link>
+ <para>The tree component functionalityity provides a built-in support for Drag
and Drop
+ operations. The main usage principles are the same as for Rich Faces Drag and Drop
wrapper
+ components. Hence, to get additional information on the topic, read the
corresponding
+ chapters:<link
linkend="dndParam">"rich:dndParam"</link>
<link
linkend="dragSupport">"rich:dragSupport"</link>
<link
linkend="dragIndicator">"rich:dragIndicator"</link>
<link
linkend="dropSupport">"rich:dropSupport"</link>
@@ -238,8 +240,8 @@
<para> Also standart HTML event attributes like "onclick",
"onmousedown", "onmouseover" and etc.
could be used. Event handlers of a tree component capture events occured on any
tree part. But
- event handlers of treeNode capture events occured on treeNode only, except for
children events.
- </para>
+ event handlers of treeNode capture events occured on treeNode only, except for
children
+ events. </para>
</section>
<section>
<title>Look-and-Feel Customization</title>
@@ -261,8 +263,8 @@
<para>There is only one skin parameter for the
<property>tree</property> since <emphasis
role="bold">
<property><rich:tree></property>
- </emphasis> is a wrapper component for <property>tree</property>
nodes. Look and feel
- is described in details in the <link
linkend="treeNode">"treeNode"
+ </emphasis> is a wrapper component for <property>tree</property>
nodes. Look and feel is
+ described in details in the <link
linkend="treeNode">"treeNode"
chapter</link>.</para>
<table>
<title>Skin parameters for wrapper element</title>