[richfaces-svn-commits] JBoss Rich Faces SVN: r3631 - trunk/docs/userguide/en/src/main/docbook/included.

Author: vkorluzhenko Date: 2007-10-31 05:38:30 -0400 (Wed, 31 Oct 2007) New Revision: 3631 Modified: trunk/docs/userguide/en/src/main/docbook/included/tree.xml Log: http://jira.jboss.com/jira/browse/RF-672 - colored meaningfull words Modified: trunk/docs/userguide/en/src/main/docbook/included/tree.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/tree.xml 2007-10-31 02:15:39 UTC (rev 3630) +++ trunk/docs/userguide/en/src/main/docbook/included/tree.xml 2007-10-31 09:38:30 UTC (rev 3631) @@ -90,8 +90,9 @@ </section> <section> <title>Details of Usage</title> - <para>As it has been mentioned <link linkend="tree">above</link> the tree component allows - rendering any tree-like structure of data.</para> + <para>As it has been mentioned <link linkend="tree">above</link> the <emphasis role="bold"> + <property>&lt;rich:tree&gt;</property> + </emphasis> component allows rendering any tree-like structure of data.</para> <para>A bean property is passed into a tree <emphasis> <property>&quot;value&quot;</property> </emphasis> attribute. The property keeps a structure of @@ -104,13 +105,14 @@ </emphasis> attribute of tree component. <ulink url="http://labs.jboss.com/file-access/default/members/jbossrichface... - structures of objects containing &quot;XmlNodeData&quot; instances as data, which - could be represented by the tree component. </para> + structures of objects containing <property>&quot;XmlNodeData&quot;</property> + instances as data, which could be represented by the tree component. </para> <para>For particular visual representation of data <emphasis role="bold"> <property>&lt;rich:tree&gt;</property> - </emphasis> selects one of the children treeNode components by type. The type is defined with - the <emphasis> + </emphasis> selects one of the children <emphasis role="bold"> + <property>&lt;rich:treeNode&gt;</property> + </emphasis> components by type. The type is defined with the <emphasis> <property>&quot;nodeFace&quot;</property> </emphasis> attribute that corresponds to a value of <emphasis> <property>&quot;type&quot;</property> @@ -173,16 +175,21 @@ <programlisting role="JAVA"><![CDATA[<h: outputText value="#{varAttributeName}"> ]]></programlisting> - <para> varAttributeName is a value for <emphasis> + <para> + <property>&quot;varAttributeName&quot;</property> is a value for <emphasis> <property>&quot;var&quot;</property> </emphasis> attribute. </para> - <para> It&apos;s possible to define several treeNode components with the equal values of <emphasis> + <para> It&apos;s possible to define several <emphasis role="bold"> + <property>&lt;rich:treeNode&gt;</property> + </emphasis> components with the equal values of <emphasis> <property>&quot;type&quot;</property> </emphasis> attribute and different values of <emphasis> <property>&quot;rendered&quot;</property> </emphasis> attribute. It provides the possibility to define different markup for the same - treeNode components type. An example is placed below. </para> + <emphasis role="bold"> + <property>&lt;rich:treeNode&gt;</property> + </emphasis> components type. An example is placed below. </para> <para> <emphasis role="bold">Example:</emphasis> @@ -204,9 +211,11 @@ </h:form> ...]]></programlisting> - <para> The example represents definition of two different treeNode components. The first - specifies the album that&apos;s available for sale, the other specifies the album that is - not available. The result is shown on the following screenshot: </para> + <para> The example represents definition of two different <emphasis role="bold"> + <property> &lt;rich:treeNode&gt;</property> + </emphasis> components. The first specifies the album that&apos;s available for sale, the + other specifies the album that is not available. The result is shown on the following + screenshot: </para> <figure> <title> Using the <emphasis> @@ -291,9 +300,11 @@ <property>&quot;value&quot;</property> </emphasis> and <emphasis> <property>&quot;var&quot;</property> - </emphasis>. Besides, visual representation shouldn&apos;t be defined right in the tree. - In this case tree tag is intended mainly for defining common attributes such as - <property>&quot;ajaxSubmitSelection&quot;</property>, for instance. </para> + </emphasis>. Besides, visual representation shouldn&apos;t be defined right in the + <property>tree</property>. In this case tree tag is intended mainly for defining common + attributes such as <emphasis> + <property>&quot;ajaxSubmitSelection&quot;</property> + </emphasis>, for instance. </para> </section> <section>