[richfaces-svn-commits] JBoss Rich Faces SVN: r784 - trunk/docs/userguide/en/included.
richfaces-svn-commits at lists.jboss.org
richfaces-svn-commits at lists.jboss.org
Wed May 16 16:59:58 EDT 2007
Author: ccowens
Date: 2007-05-16 16:59:58 -0400 (Wed, 16 May 2007)
New Revision: 784
Modified:
trunk/docs/userguide/en/included/column.xml
trunk/docs/userguide/en/included/columnGroup.xml
trunk/docs/userguide/en/included/dataDefinitionList.xml
trunk/docs/userguide/en/included/dataFilterSlider.xml
trunk/docs/userguide/en/included/dataGrid.xml
trunk/docs/userguide/en/included/dataList.xml
trunk/docs/userguide/en/included/dataOrderedList.xml
trunk/docs/userguide/en/included/dataTable.xml
trunk/docs/userguide/en/included/datascroller.xml
trunk/docs/userguide/en/included/dndParam.xml
trunk/docs/userguide/en/included/dragIndicator.xml
trunk/docs/userguide/en/included/dragIndicator1.xml
trunk/docs/userguide/en/included/dragSupport.xml
trunk/docs/userguide/en/included/draggable.xml
trunk/docs/userguide/en/included/dropDownMenu.xml
trunk/docs/userguide/en/included/dropSupport.xml
trunk/docs/userguide/en/included/dropZone.xml
trunk/docs/userguide/en/included/gmap.xml
trunk/docs/userguide/en/included/inputNumberSlider.xml
trunk/docs/userguide/en/included/inputNumberSpinner.xml
trunk/docs/userguide/en/included/menuGroup.desc.xml
trunk/docs/userguide/en/included/menuGroup.xml
trunk/docs/userguide/en/included/menuItem.xml
trunk/docs/userguide/en/included/menuSeparator.xml
trunk/docs/userguide/en/included/modalPanel.xml
trunk/docs/userguide/en/included/paint2D.xml
trunk/docs/userguide/en/included/panel.xml
trunk/docs/userguide/en/included/panelBar.xml
trunk/docs/userguide/en/included/panelBarItem.xml
trunk/docs/userguide/en/included/separator.xml
trunk/docs/userguide/en/included/simpleTogglePanel.xml
trunk/docs/userguide/en/included/spacer.xml
trunk/docs/userguide/en/included/subTable.xml
trunk/docs/userguide/en/included/suggestionBox.xml
trunk/docs/userguide/en/included/tab.xml
trunk/docs/userguide/en/included/tabPanel.xml
trunk/docs/userguide/en/included/toggleControl.xml
trunk/docs/userguide/en/included/togglePanel.xml
trunk/docs/userguide/en/included/toolBar.xml
trunk/docs/userguide/en/included/toolBarGroup.xml
trunk/docs/userguide/en/included/tree.xml
trunk/docs/userguide/en/included/treeNode.xml
Log:
designated files and more consistent section heads
Modified: trunk/docs/userguide/en/included/column.xml
===================================================================
--- trunk/docs/userguide/en/included/column.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/column.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -55,7 +55,7 @@
]]></programlisting>
</section>
<section>
- <title>Dynamical Creation from Java Code</title>
+ <title>Creating the Component Dynamically Using Java</title>
<programlisting role="JAVA"><![CDATA[import org.richfaces.component.html.HtmlColumn;
...
HtmlColumn myColumn = new HtmlColumn();
@@ -160,8 +160,8 @@
component that is described in <ulink url="columnGroup.html">the following chapter</ulink>.</para>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/columnGroup.xml
===================================================================
--- trunk/docs/userguide/en/included/columnGroup.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/columnGroup.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -58,7 +58,7 @@
]]></programlisting>
</section>
<section>
- <title>Dynamical Creation from Java Code</title>
+ <title>Creating the Component Dynamically Using Java</title>
<programlisting role="JAVA"><![CDATA[import org.richfaces.component.html.HtmlColumnGroup;
...
HtmlColumnGroup myRow = new HtmlColumnGroup();
@@ -145,8 +145,8 @@
</figure>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/dataDefinitionList.xml
===================================================================
--- trunk/docs/userguide/en/included/dataDefinitionList.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/dataDefinitionList.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -52,7 +52,7 @@
]]></programlisting>
<section>
- <title>Dynamical Creation from Java Code</title>
+ <title>Creating the Component Dynamically Using Java</title>
<programlisting role="JAVA"><![CDATA[import org.richfaces.component.html.HtmlDataDefinitionList;
...
HtmlDataDefinitionList myList = new HtmlDataDefinitionList();
@@ -85,8 +85,8 @@
specified for the whole table actually happens only for the chosen set of rows.</para>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/dataFilterSlider.xml
===================================================================
--- trunk/docs/userguide/en/included/dataFilterSlider.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/dataFilterSlider.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -37,7 +37,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para> To create the simplest variant on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page:</para>
<programlisting role="XML"><![CDATA[...
<rich:dataFilterSlider sliderListener="#{mybean.doSlide}"
startRange="0"
Modified: trunk/docs/userguide/en/included/dataGrid.xml
===================================================================
--- trunk/docs/userguide/en/included/dataGrid.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/dataGrid.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -53,7 +53,7 @@
]]></programlisting>
</section>
<section>
- <title>Dynamical Creation from Java Code</title>
+ <title>Creating the Component Dynamically Using Java</title>
<programlisting role="JAVA"><![CDATA[import org.richfaces.component.html.HtmlDataGrid;
...
HtmlDataGrid myList = new HtmlDataGrid();
@@ -91,8 +91,8 @@
actually happens only for the chosen set of elements.</para>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/dataList.xml
===================================================================
--- trunk/docs/userguide/en/included/dataList.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/dataList.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -54,7 +54,7 @@
]]></programlisting>
</section>
<section>
- <title>Dynamical Creation from Java Code</title>
+ <title>Creating the Component Dynamically Using Java</title>
<programlisting role="JAVA"><![CDATA[import org.richfaces.component.html.HtmlDataList;
...
HtmlDataList myList = new HtmlDataList();
@@ -87,8 +87,8 @@
specified for the whole table actually happens only for the chosen set of rows.</para>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/dataOrderedList.xml
===================================================================
--- trunk/docs/userguide/en/included/dataOrderedList.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/dataOrderedList.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -53,7 +53,7 @@
]]></programlisting>
</section>
<section>
- <title>Dynamical Creation from Java Code</title>
+ <title>Creating the Component Dynamically Using Java</title>
<programlisting role="JAVA"><![CDATA[import org.richfaces.component.html.HtmlDataOrderedList;
...
HtmlDataOrderedList myList = new HtmlDataOrderedList();
@@ -86,8 +86,8 @@
specified for the whole table actually happens only for the chosen set of rows.</para>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/dataTable.xml
===================================================================
--- trunk/docs/userguide/en/included/dataTable.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/dataTable.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -45,8 +45,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create the simplest variant of <property>dataTable</property> on a page, use the
- following syntax:</para>
+ <para>Here is a simple example as it might be used in a page:</para>
<programlisting role="XML"><![CDATA[...
<rich:dataTable value="#{capitalsBean.capitals}" var="capitals">
<!--...//Set of columns and header/footer facets-->
@@ -67,7 +66,7 @@
<para>The <property>table</property> component is very similar to the custom JSF dataTable one, except for the common
peculiarities of any rich component:</para>
<itemizedlist>
- <listitem>Skin support. The <property>table</property> completely meets a three-class principle of Rich Faces skinnability</listitem>
+ <listitem>Skin support. The <property>table</property> completely meets a three-class principle of Rich Faces skinability</listitem>
<listitem>Support of AJAX updates for a limited set of strings</listitem>
</itemizedlist>
<para>Skins support is described in the <ulink url="Skinnability.html">corresponding section</ulink>.
@@ -90,8 +89,8 @@
the whole table.</para>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/datascroller.xml
===================================================================
--- trunk/docs/userguide/en/included/datascroller.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/datascroller.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -45,8 +45,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create the simplest variant of <property>dataScroller</property> on a page, use the
- following syntax:</para>
+ <para>Here is a simple example as it might be used in a page:</para>
<programlisting role="XML"><![CDATA[...
<h:dataTable id="table">
...
@@ -105,8 +104,8 @@
The attribute indicates pages quantity to switch onto when fast scrolling is used. </para>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/dndParam.xml
===================================================================
--- trunk/docs/userguide/en/included/dndParam.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/dndParam.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -51,8 +51,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, place the component as nested to one of Drag
- and Drop components.</para>
+ <para>Here is a simple example as it might be used in a page, nested in one of the drag-and-drop components:</para>
<programlisting role="XML"> ...
<rich:dragSupport dragType="file">
Modified: trunk/docs/userguide/en/included/dragIndicator.xml
===================================================================
--- trunk/docs/userguide/en/included/dragIndicator.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/dragIndicator.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -45,7 +45,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax:</para>
+ <para>Here is a simple example as it might be used in a page:</para>
<programlisting role="XML"><![CDATA[ ...
<dnd:dragIndicator id="indicator">
<f:facet name="single">
Modified: trunk/docs/userguide/en/included/dragIndicator1.xml
===================================================================
--- trunk/docs/userguide/en/included/dragIndicator1.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/dragIndicator1.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -45,7 +45,7 @@
</section>
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax:</para>
+ <para>Here is a simple example as it might be used in a page:</para>
<programlisting role="XML"><![CDATA[...
<dnd:dragIndicator id="indicator">
<f:facet name="single">
Modified: trunk/docs/userguide/en/included/dragSupport.xml
===================================================================
--- trunk/docs/userguide/en/included/dragSupport.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/dragSupport.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -59,7 +59,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax:</para>
+ <para>Here is a simple example as it might be used in a page:</para>
<programlisting role="XML">...
<h:panelGrid id="drag1">
@@ -71,7 +71,7 @@
</section>
<section>
- <title>Creating the Component Dynamically from Java</title>
+ <title>Creating the Component Dynamically Using Java</title>
<programlisting role="JAVA">import org.richfaces.component.html.HtmlDragSupport;
...
@@ -183,7 +183,7 @@
</section>
<section>
- <title>Look and Feel Customization</title>
+ <title>Look-and-Feel Customization</title>
<para>The component doesn't have its own representation.</para>
</section>
Modified: trunk/docs/userguide/en/included/draggable.xml
===================================================================
--- trunk/docs/userguide/en/included/draggable.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/draggable.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -45,7 +45,7 @@
</section>
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[...
<rich:draggable dragType="file">
<!--Some Content to be Dragged-->
@@ -98,7 +98,7 @@
your own additional JavaScript functions that are called on the corresponding events.</para>
</section>
<section>
- <title>Look and Feel Customization</title>
+ <title>Look-and-Feel Customization</title>
<para>As it has been mention above, the component defines components wrapper for drag areas, i.e.
it doesn't has its own representation. Therefore, for customization of a wrapper
<emphasis role="bold"><property><div></property></emphasis> element of the component it's
Modified: trunk/docs/userguide/en/included/dropDownMenu.xml
===================================================================
--- trunk/docs/userguide/en/included/dropDownMenu.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/dropDownMenu.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -55,7 +55,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>Here is a simple example in a page:</para>
+ <para>Here is a simple example as it might be used in a page:</para>
<programlisting role="xml">...
<rich:dropDownMenu value="Item1">
@@ -65,7 +65,7 @@
</section>
<section>
- <title>Creating the Component Dynamically from Java</title>
+ <title>Creating the Component Dynamically Using Java</title>
<programlisting role="java">...
org.richfaces.component.html.HtmlDropDownMenu myMenu = new org.richfaces.component.html.HtmlDropDownMenu();
Modified: trunk/docs/userguide/en/included/dropSupport.xml
===================================================================
--- trunk/docs/userguide/en/included/dropSupport.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/dropSupport.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -222,7 +222,7 @@
</section>
<section>
- <title>Look and Feel Customization</title>
+ <title>Look-and-Feel Customization</title>
<para>The component doesn't have its own visual presentation.</para>
</section>
Modified: trunk/docs/userguide/en/included/dropZone.xml
===================================================================
--- trunk/docs/userguide/en/included/dropZone.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/dropZone.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -44,7 +44,7 @@
</section>
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[...
<rich:draggable dragType="DropIcons">
<!-- Draggable content that can be dropped to next drop zone-->
@@ -115,7 +115,7 @@
</itemizedlist>
</section>
<section>
- <title>Look and Feel Customization</title>
+ <title>Look-and-Feel Customization</title>
<para>As it has been mention above, the component defines a components wrapper for drag areas,
i.e. it doesn't have its own representation. Therefore, for a wrapper
<emphasis role="bold"><property><div></property></emphasis> element customization it's
Modified: trunk/docs/userguide/en/included/gmap.xml
===================================================================
--- trunk/docs/userguide/en/included/gmap.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/gmap.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -44,7 +44,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[...
<rich:gmap gmapKey="..."/>
...
@@ -145,7 +145,7 @@
</itemizedlist>
</section>
<section>
- <title>Look and Feel Customization</title>
+ <title>Look-and-Feel Customization</title>
<para><property>Gmap</property> component isn't tied to skin parameters, as there is no
additional elements on it, except the ones provided with
<emphasis role="italic"><property>Google Map</property>.</emphasis></para>
Modified: trunk/docs/userguide/en/included/inputNumberSlider.xml
===================================================================
--- trunk/docs/userguide/en/included/inputNumberSlider.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/inputNumberSlider.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -43,7 +43,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[...
<rich:inputNumberSlider minValue="0" maxValue="100" step="1"/>
...
@@ -127,8 +127,8 @@
</itemizedlist>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/inputNumberSpinner.xml
===================================================================
--- trunk/docs/userguide/en/included/inputNumberSpinner.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/inputNumberSpinner.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -44,7 +44,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[...
<rich:inputNumberSpinner minValue="0" maxValue="100" step="1"/>
...
@@ -118,8 +118,8 @@
</itemizedlist>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/menuGroup.desc.xml
===================================================================
--- trunk/docs/userguide/en/included/menuGroup.desc.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/menuGroup.desc.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -7,7 +7,7 @@
</sectioninfo>
<section>
<title>Description</title>
- <para>The <rich:menuGroup> component is used to define an expandable group of items inside of a popup list or another group.</para>
+ <para>The <rich:menuGroup> component is used to define an expandable group of items inside a pop-up list or another group.</para>
<figure>
<title><rich:menuGroup> component</title>
<mediaobject>
@@ -20,11 +20,11 @@
<section>
<title>Key Features</title>
<itemizedlist>
- <listitem><para>Highly customizable look and feel</para></listitem>
- <listitem><para>Grouping any menu's items set</para></listitem>
- <listitem><para>Popup appearance event customization</para></listitem>
- <listitem><para>Disablement support</para></listitem>
- <listitem><para>Smart and user defined positioning</para></listitem>
+ <listitem><para>Highly customizable look-and-feel</para></listitem>
+ <listitem><para>Grouping of any menu's items</para></listitem>
+ <listitem><para>Pop-up appearance event customization</para></listitem>
+ <listitem><para>Support for disabling</para></listitem>
+ <listitem><para>Smart user-defined positioning</para></listitem>
</itemizedlist>
</section>
Modified: trunk/docs/userguide/en/included/menuGroup.xml
===================================================================
--- trunk/docs/userguide/en/included/menuGroup.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/menuGroup.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -41,8 +41,8 @@
</table>
<section>
- <title>Creation on a page</title>
- <para>To create the simplest variant on a page use the following syntax:</para>
+ <title>Creating the Component with a Page Tag</title>
+ <para>Here is a simple example as it might be used in a page:</para>
<programlisting role="xml"><![CDATA[...
<rich:dropDownMenu value="Active">
...
@@ -55,7 +55,7 @@
</section>
<section>
- <title>Dynamical Creation from Java Code</title>
+ <title>Creating the Component Dynamically Using Java</title>
<programlisting role="java"><![CDATA[...
org.richfaces.component.html.HtmlMenuGroup myGroup = new org.richfaces.component.html.HtmlMenuGroup ();
...]]></programlisting>
@@ -64,13 +64,13 @@
<section>
<title>Details of Usage</title>
<para>
- The "value" attribute defines text representation of a group element on a page.
+ The "value" attribute defines the text representation of a group element in the page.
</para>
<para>
- The "icon" attribute defines an icon. The "iconDisabled" attribute defines an icon for a disabled group. Also you can use the "icon" and "iconDisabled" facets. If the facets are defined, the corresponding "icon" and "iconDisabled" attributes are ignored and facets content is shown as icon. It could be used for items checkboxes implementation.
+ The "icon" attribute defines an icon for the component. The "iconDisabled" attribute defines an icon for when the group is disabled. Also you can use the "icon" and "iconDisabled" facets. If the facets are defined, the corresponding "icon" and "iconDisabled" attributes are ignored and the facets' contents are used as icons. This could be used for an item check box implementation.
</para>
<para>
- Example.
+ Here is an example:
</para>
<programlisting role="xml"><![CDATA[...
<f:facet name="icon">
@@ -79,10 +79,10 @@
...]]>
</programlisting>
<para>
- The "iconFolder" and "iconFolderDisabled" attributes are defined for using icons as a folder icon. The "iconFolder" and "iconFolderDisabled" facets use content as folder icon representation.
+ The "iconFolder" and "iconFolderDisabled" attributes are defined for using icons as folder icons. The "iconFolder" and "iconFolderDisabled" facets use their contents as folder icon representations in place of the attribute values.
</para>
<para>
- The "direction" attribute is used to define the ways of menu's appearance as it's shown in the example below.
+ The "direction" attribute is used to define which way to display the menu as shown in the example below:
</para>
<para>Possible values are:</para>
<itemizedlist>
@@ -91,10 +91,10 @@
<listitem><para>auto – smart positioning activated.</para></listitem>
</itemizedlist>
<para>
- On default the "direction" attribute is defined as "auto".
+ By default, the "direction" attribute is set to "auto".
</para>
<para>
-
+ Here is an example:
</para>
<programlisting role="xml"><![CDATA[...
<rich:menuGroup value="Active" direction="left"
@@ -103,7 +103,7 @@
...]]>
</programlisting>
<para>
- As a result:
+ This would be the result:
</para>
<figure>
<title>Using the "direction" attribute</title>
@@ -116,16 +116,16 @@
</section>
<section>
- <title> Look and Feel Customization</title>
+ <title>Look-and-Feel Customization</title>
<para>
- For skinnability implementation, the components use a style class redefinition method. Default style classes are mapped on skin parameters.
+ For skinability implementation, the components use a style class redefinition method. Default style classes are mapped on skin parameters.
</para>
<para>
- There are two ways to redefine appearance of all menuGroups at once:
+ There are two ways to redefine the appearance of all menuGroups at once:
</para>
<itemizedlist>
- <listitem><para>Redefine corresponding skin parameters.</para></listitem>
- <listitem><para>Add to user's stylesheets style classes used by a menuGroup.</para></listitem>
+ <listitem><para>Redefine corresponding skin parameters</para></listitem>
+ <listitem><para>Add to user's stylesheet style classes used by a menuGroup</para></listitem>
</itemizedlist>
</section>
<section>
@@ -191,7 +191,7 @@
<section>
<title> Definition custom style classes </title>
<para>
- On the screenshot, there are classes names that define group element appearance.
+ The classes names that define group element appearance are in the screenshot.
</para>
<figure>
<title>Classes names</title>
@@ -231,7 +231,7 @@
</tgroup>
</table>
<para>
- All listed elements except of general are defined for disabled mode.
+ All listed elements except for the general one are defined for disabled mode.
</para>
<table>
<title>Classes names for disabled mode</title>
@@ -259,10 +259,10 @@
</tgroup>
</table>
<para>
- In order to redefine style for all menuGroups on a page using CSS, it's enough to create classes with the same names and define the necessary properties in them.
+ In order to redefine the style for all menuGroups on a page using CSS, it's enough to create classes with the same names and define the necessary properties in them.
</para>
<para>
- To change style peculiarities of the particular menuGroups define your own style classes in the corresponding simple menuGroup attributes.
+ To change style aspects of particular menuGroups define your own style classes in the corresponding menuGroup attributes.
</para>
</section>
</section>
Modified: trunk/docs/userguide/en/included/menuItem.xml
===================================================================
--- trunk/docs/userguide/en/included/menuItem.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/menuItem.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -42,7 +42,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>Here is a simple example in a page:</para>
+ <para>Here is a simple example as it might be used in a page:</para>
<programlisting role="xml"><![CDATA[...
<rich:dropDownMenu>
...
@@ -53,7 +53,7 @@
</section>
<section>
- <title>Creating the Component Dynamically from Java</title>
+ <title>Creating the Component Dynamically Using Java</title>
<programlisting role="java"><![CDATA[...
org.richfaces.component.html.HtmlMenuItem myItem = new org.richfaces.component.html.HtmlMenuItem ();
...]]></programlisting>
Modified: trunk/docs/userguide/en/included/menuSeparator.xml
===================================================================
--- trunk/docs/userguide/en/included/menuSeparator.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/menuSeparator.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -42,7 +42,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>Here is a simple example in a page:</para>
+ <para>Here is a simple example as it might be used in a page:</para>
<programlisting role="xml"><![CDATA[...
<rich:dropDownMenu/>
...
@@ -53,7 +53,7 @@
</section>
<section>
- <title>Creating the Component Dynamically from Java</title>
+ <title>Creating the Component Dynamically Using Java</title>
<programlisting role="java"><![CDATA[...
org.richfaces.component.html.HtmlMenuSeparator mySep = new org.richfaces.component.html.HtmlMenuSeparator ();
...]]></programlisting>
Modified: trunk/docs/userguide/en/included/modalPanel.xml
===================================================================
--- trunk/docs/userguide/en/included/modalPanel.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/modalPanel.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -59,7 +59,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To add it to a page, use the following syntax:</para>
+ <para>Here is a simple example as it might be used in a page:</para>
<programlisting role="XML">...
<rich:modalPanel id="panel">
@@ -211,9 +211,9 @@
</section>
<section>
- <title>Look and Feel Customization</title>
+ <title>Look-and-Feel Customization</title>
- <para>For implementing skinnability the components use a <emphasis
+ <para>For implementing skinability the components use a <emphasis
role="italic">
<property>style class redefinition method</property>
</emphasis>. Default style classes are mapped on <emphasis
Modified: trunk/docs/userguide/en/included/paint2D.xml
===================================================================
--- trunk/docs/userguide/en/included/paint2D.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/paint2D.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -44,7 +44,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[...
<rich:paint2D paint="#{paint2D.paint}" data="#{paint2DModel}"/>
...
@@ -118,7 +118,7 @@
</section>
<section>
- <title>Look and Feel Customization</title>
+ <title>Look-and-Feel Customization</title>
<para><property>Paint2D</property> has no skin parameters and special
<emphasis role="italic"><property>style classes</property>, </emphasis> as it consists
of one element generated with a user's method on the server.</para>
Modified: trunk/docs/userguide/en/included/panel.xml
===================================================================
--- trunk/docs/userguide/en/included/panel.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/panel.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -44,7 +44,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[...
<rich:panel>
<f:facet name="header">
@@ -139,8 +139,8 @@
</itemizedlist>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/panelBar.xml
===================================================================
--- trunk/docs/userguide/en/included/panelBar.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/panelBar.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -44,7 +44,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[...
<rich:panelBar>
<!--//... -->
@@ -79,8 +79,8 @@
<para><property>panelBar</property> could contain any number of child <property>panelBarItem</property> components inside, which content is uploaded onto the client and headers are controls to open the corresponding child element.</para>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/panelBarItem.xml
===================================================================
--- trunk/docs/userguide/en/included/panelBarItem.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/panelBarItem.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -44,7 +44,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[...
<rich:panelBar>
<rich:panelBarItem label="Canon">
@@ -77,8 +77,8 @@
corresponding child element.</para>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/separator.xml
===================================================================
--- trunk/docs/userguide/en/included/separator.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/separator.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -44,7 +44,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create <property>separator</property> on a page, use the following syntax:</para>
+ <para>Here is a simple example as it might be used in a page:</para>
<programlisting role="XML"><![CDATA[...
<rich:separator/>
...
@@ -97,7 +97,7 @@
</itemizedlist>
</section>
<section>
- <title>Look and Feel Customization</title>
+ <title>Look-and-Feel Customization</title>
<para>On the component generation, the framework presents a default rich-separator class in
styleClass of a generated component, i.e. in order to redefine appearance of all <property>separators</property> at
once, it's necessary to redefine this class in your own CSS (replacing in the result properties
Modified: trunk/docs/userguide/en/included/simpleTogglePanel.xml
===================================================================
--- trunk/docs/userguide/en/included/simpleTogglePanel.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/simpleTogglePanel.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -45,7 +45,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[...
<rich:simpleTogglePanel>
...
@@ -112,8 +112,8 @@
</figure>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/spacer.xml
===================================================================
--- trunk/docs/userguide/en/included/spacer.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/spacer.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -44,7 +44,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>Here is an example of the component decoding on a page. </para>
+ <para>Here is a simple example as it might be used in a page:</para>
<programlisting role="XML"><![CDATA[...
<rich:spacer/>
...]]></programlisting>
@@ -81,7 +81,7 @@
</itemizedlist>
</section>
<section>
- <title>Look and Feel Customization</title>
+ <title>Look-and-Feel Customization</title>
<para>On the component generation, the framework presents a default rich-spacer class in
<emphasis role="italic"><property>styleClass</property></emphasis> of a generated
component, i.e. in order to redefine appearance of all <property>spacers</property>
Modified: trunk/docs/userguide/en/included/subTable.xml
===================================================================
--- trunk/docs/userguide/en/included/subTable.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/subTable.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -43,7 +43,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create simplest variant of <property>subTable</property> on a page, use the following syntax:</para>
+ <para>Here is a simple example as it might be used in a page:</para>
<programlisting role="XML"><![CDATA[...
<rich:dataTable value="#{capitalsBean.capitals}" var="capitals">
<!--...//Set of columns and header/footer facets-->
@@ -69,7 +69,7 @@
Hence, it's possible to add a subtable structure different from the main one to organize tables
of the master - details type. The component is also has common peculiarities of any rich component:</para>
<itemizedlist>
- <listitem>Skin support. The table completely meets a three-class principle of Rich Faces skinnability</listitem>
+ <listitem>Skin support. The table completely meets a three-class principle of Rich Faces skinability</listitem>
<listitem>Support of AJAX updates for a limited set of rows</listitem>
</itemizedlist>
<para>Skins support is described in the <ulink url="Skinnability.html">corresponding section</ulink>. AJAX support is
@@ -96,8 +96,8 @@
when update is specified for the whole table.</para>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/suggestionBox.xml
===================================================================
--- trunk/docs/userguide/en/included/suggestionBox.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/suggestionBox.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -44,7 +44,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[...
<h:inputText value="#{bean.property}" id="suggest"/>
<rich:suggestionbox for="suggest" suggestionAction="#{bean.autocomplete}"
Modified: trunk/docs/userguide/en/included/tab.xml
===================================================================
--- trunk/docs/userguide/en/included/tab.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/tab.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -43,7 +43,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[...
<rich:tabPanel>
<!--Set of Tabs inside-->
@@ -108,8 +108,8 @@
</itemizedlist>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use <emphasis
role="italic"><property>style class redefinition method</property>.</emphasis>
Default style classes are mapped on <emphasis
Modified: trunk/docs/userguide/en/included/tabPanel.xml
===================================================================
--- trunk/docs/userguide/en/included/tabPanel.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/tabPanel.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -44,7 +44,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[...
<rich:tabPanel>
<!--//Set of Tabs inside-->
@@ -139,8 +139,8 @@
</itemizedlist>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/toggleControl.xml
===================================================================
--- trunk/docs/userguide/en/included/toggleControl.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/toggleControl.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -45,7 +45,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[<rich:toggleControl for="panel"/>
...
<rich:togglePanel id="panel" stateOrder="[facets order to be switched]">
@@ -109,7 +109,7 @@
role="italic"><property>"switchToState"</property></emphasis> attribute.</para>
</section>
<section>
- <title>Look and Feel Customization</title>
+ <title>Look-and-Feel Customization</title>
<para>On component generation the framework substitutes the default
class <emphasis role="italic"><property>rich-toggle-control</property></emphasis> into
styleClass of a generated component, i.e. to redefine at once all <property>toggle controls</property> appearance on a
Modified: trunk/docs/userguide/en/included/togglePanel.xml
===================================================================
--- trunk/docs/userguide/en/included/togglePanel.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/togglePanel.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -44,7 +44,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[...
<rich:togglePanel>
<f:facet name="first">
@@ -122,7 +122,7 @@
<para>The example shows a <property>togglePanel</property> initial state when the second facet (panelB) is rendered and successive switching from the first to the second happens.</para>
</section>
<section>
- <title>Look and Feel Customization</title>
+ <title>Look-and-Feel Customization</title>
<para>The component doesn't have its own representation rendering only content of its facets, thus all look and feel is set only for content.</para>
</section>
</section>
\ No newline at end of file
Modified: trunk/docs/userguide/en/included/toolBar.xml
===================================================================
--- trunk/docs/userguide/en/included/toolBar.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/toolBar.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -44,7 +44,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[<rich:toolBar>
<!--//...Set of action or other JSF components-->
</rich:toolBar>
@@ -98,8 +98,8 @@
are placed above all.</para>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/toolBarGroup.xml
===================================================================
--- trunk/docs/userguide/en/included/toolBarGroup.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/toolBarGroup.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -44,7 +44,7 @@
</section>
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[<rich:toolBar>
...
<rich:toolBarGroup>
@@ -113,8 +113,8 @@
</figure>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/tree.xml
===================================================================
--- trunk/docs/userguide/en/included/tree.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/tree.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -44,7 +44,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[...
<rich:tree>
<!--Set of the Tree nodes-->
@@ -186,8 +186,8 @@
</itemizedlist>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
Modified: trunk/docs/userguide/en/included/treeNode.xml
===================================================================
--- trunk/docs/userguide/en/included/treeNode.xml 2007-05-16 16:02:53 UTC (rev 783)
+++ trunk/docs/userguide/en/included/treeNode.xml 2007-05-16 20:59:58 UTC (rev 784)
@@ -44,7 +44,7 @@
<section>
<title>Creating the Component with a Page Tag</title>
- <para>To create it on a page, use the following syntax: </para>
+ <para>Here is a simple example as it might be used in a page: </para>
<programlisting role="XML"><![CDATA[...
<rich:tree ... faceNode="simpleNode">
<rich:treeNode type="simpleNode">
@@ -55,7 +55,7 @@
]]></programlisting>
</section>
<section>
- <title>Dynamical Creation from Java Code</title>
+ <title>Creating the Component Dynamically Using Java</title>
<programlisting role="JAVA"><![CDATA[import org.richfaces.component.html.HtmlTreeNode;
...
HtmlTreeNode myPanel = new HtmlTreeNode();
@@ -66,7 +66,7 @@
<title>Details of Usage</title>
</section>
<section>
- <title>Look and Feel Customization</title>
+ <title>Look-and-Feel Customization</title>
<para>As it has been mentioned above, <property>treeNode</property> defines a template for nodes
rendering in a tree. Thus, during XML document rendering (a web.xml application) as a tree, the
following nodes output (passed via var="data" on a tree) happens:</para>
@@ -113,8 +113,8 @@
<ulink url="tree.html">the tree component level</ulink> for a default Node.</para>
</section>
<section>
- <title>Look and Feel Customization</title>
- <para>For skinnability implementation the components use a <emphasis
+ <title>Look-and-Feel Customization</title>
+ <para>For skinability implementation the components use a <emphasis
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>
More information about the richfaces-svn-commits
mailing list