Author: smukhina Date: 2007-07-04 08:41:56 -0400 (Wed, 04 Jul 2007) New Revision: 1461 Modified: trunk/docs/userguide/en/src/main/docbook/included/tree.xml Log: http://jira.jboss.com/jira/browse/RF-398 small grammar mistakes are fixed Modified: trunk/docs/userguide/en/src/main/docbook/included/tree.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/tree.xml 2007-07-04 12:24:26 UTC (rev 1460) +++ trunk/docs/userguide/en/src/main/docbook/included/tree.xml 2007-07-04 12:41:56 UTC (rev 1461) @@ -65,7 +65,7 @@ <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 may look at this interface description in the API document) The default classes for lists building of a TreeNodeImpl type (it + 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&apos;s necessary only to implement this interface, i.e. the <emphasis role="italic"><property>&quot;var&quot;</property></emphasis> attribute contains @@ -102,7 +102,7 @@ <para>To set a model saving during requests, use the <emphasis role="italic"><property>&quot;preserveModel&quot;</property></emphasis>attribute with state, request (default) and none values. The attribute is used for cashing data between requests - in state or request. The + in a state or request. The <emphasis role="italic"><property>&quot;treeDataLocator&quot;</property></emphasis> attribute defines a class providing an access to cashed data according to the ids saved in state/request on recovery or cashing data saving the Id on caching.</para> @@ -200,19 +200,19 @@ <title>Events handling</title> <para>Listeners classes that process events on server side are defined with the help:</para> <itemizedlist> - <listitem>nodeSelectListener is called during request sending on a node selecting event (if request sending on this + <listitem>nodeSelectListener is called during request sending on a node selecting event (if request sending on this event is defined)</listitem> <listitem>dropListener processes Drop event</listitem> <listitem>changeExpandListener processes expand/collapse event of a tree node</listitem> </itemizedlist> <para>Moreover, to add e.g. some JavaScript effects, client events defined on it are used:</para> <itemizedlist> - <listitem>onexpand - expand node event</listitem> - <listitem>oncollapse - collapse node event</listitem> - <listitem>ondragexit - element passing out from tree zone event</listitem> - <listitem>ondragstart - drag start event</listitem> - <listitem>ondragend - drag end event (drop event)</listitem> - <listitem>ondragenter - dragged element appearing on tree event</listitem> + <listitem>onexpand - expands a node event</listitem> + <listitem>oncollapse - collapses a node event</listitem> + <listitem>ondragexit - element passing out from a tree zone event</listitem> + <listitem>ondragstart - drags a start event</listitem> + <listitem>ondragend - drags an end event (a drop event)</listitem> + <listitem>ondragenter - drags an element appearing on a tree event</listitem> </itemizedlist> @@ -223,7 +223,7 @@ role="italic"><property>style class redefinition method</property></emphasis>.</para> <para>Default style classes are mapped on <emphasis role="italic"><property>skin parameters</property>.</emphasis></para> - <para>To redefine appearance of all trees at once, there are two ways:</para> + <para>To redefine an appearance of all trees at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis