[richfaces-svn-commits] JBoss Rich Faces SVN: r844 - trunk/docs/userguide/en/included.

Author: smukhina Date: 2007-05-23 11:23:56 -0400 (Wed, 23 May 2007) New Revision: 844 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.desc.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.desc.xml trunk/docs/userguide/en/included/menuItem.xml trunk/docs/userguide/en/included/menuSeparator.desc.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: The right files from Charley version (784) Modified: trunk/docs/userguide/en/included/column.xml =================================================================== --- trunk/docs/userguide/en/included/column.xml 2007-05-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/column.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/columnGroup.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/dataDefinitionList.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -1,6 +1,11 @@ <?xml version='1.0' encoding='UTF-8'?> <section> -<section> +<sectioninfo> +<keywordset> +<keyword>HtmlDataDefinitionList</keyword> +<keyword>rich:dataDefinitionList</keyword> +</keywordset> +</sectioninfo> <table> <title>Component identification parameters </title> <tgroup cols="2"> @@ -45,9 +50,9 @@ </rich:dataDefinitionList> ... ]]></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.HtmlDataDefinitionList; ... HtmlDataDefinitionList myList = new HtmlDataDefinitionList(); @@ -80,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> @@ -135,4 +140,5 @@ <para>To redefine an appearance of all <property>dataDefinitionLists</property> on a page, just redefine one of this classes.</para> <para>To redefine a style of a particular <property>dataDefinitionList</property>, use corresponding class attributes on the component.</para> </section> - </section> \ No newline at end of file + </section> + \ No newline at end of file Modified: trunk/docs/userguide/en/included/dataFilterSlider.xml =================================================================== --- trunk/docs/userguide/en/included/dataFilterSlider.xml 2007-05-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/dataFilterSlider.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -1,6 +1,6 @@ <?xml version='1.0' encoding='UTF-8'?> <section> - <section> + <table> <title>Component identification parameters </title> <tgroup cols="2"> @@ -34,10 +34,10 @@ </tbody> </tgroup> </table> - </section> + <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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/dataGrid.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/dataList.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/dataOrderedList.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/dataTable.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/datascroller.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/dndParam.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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"> ... &lt;rich:dragSupport dragType="file"&gt; Modified: trunk/docs/userguide/en/included/dragIndicator.xml =================================================================== --- trunk/docs/userguide/en/included/dragIndicator.xml 2007-05-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/dragIndicator.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/dragIndicator1.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/dragSupport.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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">... &lt;h:panelGrid id="drag1"&gt; @@ -71,7 +71,7 @@ </section> <section> - <title>Dynamical Creation from Java Code</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&apos;t have its own representation.</para> </section> Modified: trunk/docs/userguide/en/included/draggable.xml =================================================================== --- trunk/docs/userguide/en/included/draggable.xml 2007-05-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/draggable.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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&apos;t has its own representation. Therefore, for customization of a wrapper <emphasis role="bold"><property>&lt;div&gt;</property></emphasis> element of the component it&apos;s Modified: trunk/docs/userguide/en/included/dropDownMenu.desc.xml =================================================================== --- trunk/docs/userguide/en/included/dropDownMenu.desc.xml 2007-05-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/dropDownMenu.desc.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -1,33 +1,55 @@ -<?xml version="1.0" encoding="UTF-8"?> -<section> - <sectioninfo> - <keywordset> - <keyword>dropDownMenu</keyword> - </keywordset> - </sectioninfo> - <section> -<title>Description</title> - <para>The &lt;rich:dropDownMenu&gt; component is used for a multilevel dropdown menu creation.</para> - <figure> - <title>&lt;rich:dropDownMenu&gt; component</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/dropDownMenu1.png" /> - </imageobject> - </mediaobject> - </figure> -</section> -<section> - <title>Key Features</title> - <itemizedlist> - <listitem><para>Highly customizable look and feel</para></listitem> - <listitem><para>Popup appearance event customization</para></listitem> - <listitem><para>Different submission modes</para></listitem> - <listitem><para>Possibility of complex representation elements definition</para></listitem> - <listitem><para>Disablement support</para></listitem> - <listitem><para>Smart and user defined positioning </para></listitem> - </itemizedlist> - -</section> - +<?xml version="1.0" encoding="UTF-8"?> +<section> + <sectioninfo> + <keywordset> + <keyword>dropDownMenu</keyword> + </keywordset> + </sectioninfo> + + <section> + <title>Description</title> + + <para>The &lt;rich:dropDownMenu&gt; component is used for creating + multilevel drop-down menus.</para> + + <figure> + <title>&lt;rich:dropDownMenu&gt; component</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/dropDownMenu1.png" /> + </imageobject> + </mediaobject> + </figure> + </section> + + <section> + <title>Key Features</title> + + <itemizedlist> + <listitem> + <para>Highly customizable look-and-feel</para> + </listitem> + + <listitem> + <para>Pop-up appearance event customization</para> + </listitem> + + <listitem> + <para>Different submission modes</para> + </listitem> + + <listitem> + <para>Ability to define a complex representation for elements</para> + </listitem> + + <listitem> + <para>Support for disabling</para> + </listitem> + + <listitem> + <para>Smart user-defined positioning</para> + </listitem> + </itemizedlist> + </section> </section> \ No newline at end of file Modified: trunk/docs/userguide/en/included/dropDownMenu.xml =================================================================== --- trunk/docs/userguide/en/included/dropDownMenu.xml 2007-05-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/dropDownMenu.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -67,317 +67,432 @@ <section> <title>Creating the Component Dynamically Using Java</title> - <programlisting role="java"><![CDATA[... + <programlisting role="java">... org.richfaces.component.html.HtmlDropDownMenu myMenu = new org.richfaces.component.html.HtmlDropDownMenu(); -...]]</programlisting> - </section> - - <section> - <title>Details of Usage</title> - <para> - All attributes except the &quot;value&quot; are not required. The &quot;value&quot; attribute defines a representation text. - </para> - <para> - Also instead of the &quot;value&quot; attribute you can use the &quot;label&quot; facet. - </para> - <para> - Example. - </para> - <programlisting role="xml"><![CDATA[... - <f:facet name="label"> - <h:graphicImage value="/images/img1.gif"/> - </f:facet> -...]]></programlisting> - <para> - Use the &quot;event&quot; attribute to define an event on the representation element that triggers a menu appearance. An example of a menu appearance on a click could be seen below. - </para> - <programlisting role="xml"><![CDATA[... - <rich:dropDownMenu event="onclick" value="Item1"> - <!--Nested menu components--> - </rich:dropDownMenu> -...]]></programlisting> - <para> - Switching mode could be chosen with the &lt;rich:dropDownMenu&gt; attribute &quot;mode&quot; with three possible parameters. - </para> - <itemizedlist> - <listitem><para>Server (on default)</para></listitem> - </itemizedlist> - <para> - The common submission of a form is performed and a page is completely refreshed. - </para> - <itemizedlist> - <listitem><para>Ajax</para></listitem> - </itemizedlist> - <para> - Ajax form submission is performed, additionally specified elements in the &quot;reRender&quot; attribute are reRendered. - </para> - <itemizedlist> - <listitem><para>None</para></listitem> - </itemizedlist> - <para> - The&quot;action&quot; and &quot;actionListener&quot; item&apos;s attributes are ignored. Menu items don&apos;t fire any submits itself. Behavior is fully defined by the components nested into items. - </para> - <note><title>Note:</title> - As the &lt;rich:dropDownMenu&gt; component doesn&apos;t provide its own form, use it in &lt;form&gt;...&lt;/h:form&gt;. - </note> - <para> - The &quot;direction&quot; and &quot;jointPoint&quot; attributes are used for the definition ways of menu appearance as it&apos;s shown in the example below. - </para> - <para> - Possible values for the &quot;direction&quot; attribute are: - </para> - <itemizedlist> - <listitem><para>top-left - a menu attached to the top-right corner of the label;</para></listitem> - <listitem><para>top-right - a menu attached to the top-left corner of the label;</para></listitem> - <listitem><para>bottom-left - a menu attached to the bottom-right corner of the label;</para></listitem> - <listitem><para>bottom-right - a menu attached to the bottom-left corner of the label;</para></listitem> - <listitem><para>auto - a smart positioning activation.</para></listitem> - </itemizedlist> - <para> - Possible values for the &quot;jointPoint&quot; attribute are: - </para> - <itemizedlist> - <listitem><para>tr - top-right point of the label element;</para></listitem> - <listitem><para>tl - top-left point of the label element;</para></listitem> - <listitem><para>br - bottom-right point of the label element;</para></listitem> - <listitem><para>bl - bottom-left point of the label element;</para></listitem> - <listitem><para>auto - smart positioning activation.</para></listitem> - </itemizedlist> - <para> - On default the &quot;direction&quot; and &quot;jointPoint&quot; attributes define as &quot;auto&quot;. - </para> - <para> - Example. - </para> - <programlisting role="xml"><![CDATA[... - <rich:dropDownMenu value="Item1" direction="bottom-right" jointPoint="tr"> - <!--Nested menu components--> - </rich:dropDownMenu> -...]]></programlisting> - <para> - As a result: - </para> - <figure> - <title>Using the &quot;direction&quot; and &quot;joinPoint&quot; attributes</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/dropDownMenu2.png" /> - </imageobject> - </mediaobject> - </figure> - <para> - You can correct an offset of the popup list relatively to the label using following attributes: &quot;horizontalOffset&quot; and &quot;verticalOffset&quot;. - </para> - <para> - Example. - </para> - <programlisting role="xml"><![CDATA[... - <rich:dropDownMenu value="Item1" direction="bottom-right" jointPoint="tr" horizontalOffset="-15" verticalOffset="0"> - <!--Nested menu components--> - </rich:dropDownMenu> -...]]> +...</programlisting> + </section> + + <section> + <title>Details of Usage</title> + + <para>All attributes except "value" are optional. The "value" attribute + defines text to be represented. If you can use the "label" facet, you can + even not use the "value" attribute.</para> + + <para>Here is an example:</para> + + <programlisting role="xml">... + &lt;f:facet name="label"&gt; + &lt;h:graphicImage value="/images/img1.gif"/&gt; + &lt;/f:facet&gt; +...</programlisting> + + <para>Use the "event" attribute to define an event for the represented + element that triggers a menu appearance. An example of a menu appearance + on a click can be seen below.</para> + + <programlisting role="xml">... + &lt;rich:dropDownMenu event="onclick" value="Item1"&gt; + &lt;!--Nested menu components--&gt; + &lt;/rich:dropDownMenu&gt; +...</programlisting> + + <para>The &lt;rich:dropDownMenu&gt; "mode" attribute can be set to three + possible parameters:</para> + + <itemizedlist> + <listitem> + <para>Server (default)</para> + </listitem> + </itemizedlist> + + <para>The standard form submission is performed and the page is completely + refreshed.</para> + + <itemizedlist> + <listitem> + <para>Ajax</para> + </listitem> + </itemizedlist> + + <para>An AJAX form submission is performed, and specified elements in the + "reRender" attribute are rerendered.</para> + + <itemizedlist> + <listitem> + <para>None</para> + </listitem> + </itemizedlist> + + <para>The "action" and "actionListener" item's attributes are ignored. + Menu items don't fire any submits themselves. The behavior is fully + defined by the components nested inside items.</para> + + <note><title>Note:</title> As the &lt;rich:dropDownMenu&gt; component + doesn't provide its own form, use it between &lt;h:form&gt; and + &lt;/h:form&gt; tags.</note> + + <para>The "direction" and "jointPoint" attributes are used for defining + aspects of menu appearance.</para> + + <para>Possible values for the "direction" attribute are:</para> + + <itemizedlist> + <listitem> + <para>top-left - a menu attached to the top-right corner of the + label</para> + </listitem> + + <listitem> + <para>top-right - a menu attached to the top-left corner of the + label</para> + </listitem> + + <listitem> + <para>bottom-left - a menu attached to the bottom-right corner of the + label</para> + </listitem> + + <listitem> + <para>bottom-right - a menu attached to the bottom-left corner of the + label</para> + </listitem> + + <listitem> + <para>auto - a smart positioning activation</para> + </listitem> + </itemizedlist> + + <para>Possible values for the "jointPoint" attribute are:</para> + + <itemizedlist> + <listitem> + <para>tr - top-right point of the label element</para> + </listitem> + + <listitem> + <para>tl - top-left point of the label element</para> + </listitem> + + <listitem> + <para>br - bottom-right point of the label element</para> + </listitem> + + <listitem> + <para>bl - bottom-left point of the label element</para> + </listitem> + + <listitem> + <para>auto - smart positioning activation</para> + </listitem> + </itemizedlist> + + <para>By default, the "direction" and "jointPoint" attributes are set to + "auto".</para> + + <para>Here is an example:</para> + + <programlisting role="xml">... + &lt;rich:dropDownMenu value="Item1" direction="bottom-right" jointPoint="tr"&gt; + &lt;!--Nested menu components--&gt; + &lt;/rich:dropDownMenu&gt; +...</programlisting> + + <para>This is the result:</para> + + <figure> + <title>Using the "direction" and "joinPoint" attributes</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/dropDownMenu2.png" /> + </imageobject> + </mediaobject> + </figure> + + <para>You can correct an offset of the pop-up list relative to the label + using the following attributes: "horizontalOffset" and + "verticalOffset".</para> + + <para>Here is an example:</para> + + <programlisting role="xml">... + &lt;rich:dropDownMenu value="Item1" direction="bottom-right" jointPoint="tr" horizontalOffset="-15" verticalOffset="0"&gt; + &lt;!--Nested menu components--&gt; + &lt;/rich:dropDownMenu&gt; +... </programlisting> - <para> - As a result: - </para> - <figure> - <title>Using the &quot;horizontalOffset&quot; and &quot;verticalOffset&quot; attributes</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/dropDownMenu3.png" /> - </imageobject> - </mediaobject> - </figure> - </section> - - <section> - <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. - </para> - <para> - There are two ways to redefine appearance of all dropDownMenus at once: - </para> - <itemizedlist> - <listitem><para>Redefine corresponding skin parameters.</para></listitem> - <listitem><para>Add to user&apos;s stylesheets style classes used by a dropDownMenu.</para></listitem> - </itemizedlist> - </section> - <section> - <title>Skin parameters redefinition</title> - <table> - <title>Label Skin parameters redefinition</title> - <tgroup cols="2"> - <thead> - <row> - <entry>Skin parameters for label div element</entry> - <entry>CSS properties</entry> - </row> - </thead> - <tbody> - <row> - <entry>generalFamilyFont</entry> - <entry>font-family</entry> - </row> - <row> - <entry>generalSizeFont</entry> - <entry>font-size</entry> - </row> - </tbody> - </tgroup> - </table> - <table> - <title>Label Skin parameters redefinition</title> - <tgroup cols="2"> - <thead> - <row> - <entry>Skin parameters for selected label element</entry> - <entry>CSS properties</entry> - </row> - </thead> - <tbody> - <row> - <entry>panelBorderColor</entry> - <entry>border-color</entry> - </row> - <row> - <entry>controlBackgroundColor</entry> - <entry>background-color</entry> - </row> - <row> - <entry>generalTextColor</entry> - <entry>background-colorcolor</entry> - </row> - </tbody> - </tgroup> - </table> - <table> - <title>Popup Skin parameters redefinition</title> - <tgroup cols="2"> - <thead> - <row> - <entry>Skin parameters for border element</entry> - <entry>CSS properties</entry> - </row> - </thead> - <tbody> - <row> - <entry>panelBorderColor</entry> - <entry>border-color</entry> - </row> - <row> - <entry>additionalBackgroundColor</entry> - <entry>background-color</entry> - </row> - </tbody> - </tgroup> - </table> - <table> - <title>Popup Skin parameters redefinition</title> - <tgroup cols="2"> - <thead> - <row> - <entry>Skin parameters for background element</entry> - <entry>CSS properties</entry> - </row> - </thead> - <tbody> - <row> - <entry>additionalBackgroundColor</entry> - <entry>border-top-color</entry> - </row> - <row> - <entry>additionalBackgroundColor</entry> - <entry>border-left-color</entry> - </row> - <row> - <entry>additionalBackgroundColor</entry> - <entry>border-right-color</entry> - </row> - </tbody> - </tgroup> - </table> - </section> - <section> - <title> Definition custom style classes </title> - <para> - On the screenshot, there are classes names that define element label. - </para> - <figure> - <title>dropDownMenu class names</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/dropDownMenu4.png" /> - </imageobject> - </mediaobject> - </figure> - <table> - <title>Classes names that define element label</title> - <tgroup cols="2"> - <thead> - <row> - <entry>Class name</entry> - <entry>Description</entry> - </row> - </thead> - <tbody> - <row> - <entry>Rich-label-text-decor</entry> - <entry>Defines the text style of a representation element</entry> - </row> - <row> - <entry>Rich-ddmenu-label</entry> - <entry>Defines the class for wrapping div element of a representation element</entry> - </row> - <row> - <entry>Rich-ddmenu-label-select</entry> - <entry>Defines the class for wrapping div element of the selected representation element</entry> - </row> - <row> - <entry>Rich-ddmenu-label-unselect</entry> - <entry>Defines the class for wrapping div element of a representation element that isn&apos;t selected</entry> - </row> - </tbody> - </tgroup> - </table> - <para> - On the screenshot, there are classes names that define element popup. - </para> - <figure> - <title>Classes names</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/dropDownMenu5.png" /> - </imageobject> - </mediaobject> - </figure> - <table> - <title>Classes names that define element popup</title> - <tgroup cols="2"> - <thead> - <row> - <entry>Class name</entry> - <entry>Description</entry> - </row> - </thead> - <tbody> - <row> - <entry>Rich-menu-list-border</entry> - <entry>Defines a class for borders elements</entry> - </row> - <row> - <entry>Rich-menu-list-border</entry> - <entry>Defines the class for a general background list</entry> - </row> - </tbody> - </tgroup> - </table> - <para> - In order to redefine style for all dropDownMenus on a page using CSS, it&apos;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 dropDownMenus define your own style classes in the corresponding simple dropDownMenu attributes. - </para> - </section> - </section> + <para>This is the result:</para> + + <figure> + <title>Using the "horizontalOffset" and "verticalOffset" + attributes</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/dropDownMenu3.png" /> + </imageobject> + </mediaobject> + </figure> + </section> + + <section> + <title>Look-and-Feel Customization</title> + + <para>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 the appearance of all dropDownMenus + at once:</para> + + <itemizedlist> + <listitem> + <para>Redefine the corresponding skin parameters</para> + </listitem> + + <listitem> + <para>Add to a user's stylesheets style classes used by a + dropDownMenu</para> + </listitem> + </itemizedlist> + </section> + + <section> + <title> Redefinition of Skin Parameters</title> + + <table> + <title>Label Skin parameters redefinition</title> + + <tgroup cols="2"> + <thead> + <row> + <entry>Skin parameters for label div element</entry> + + <entry>CSS properties</entry> + </row> + </thead> + + <tbody> + <row> + <entry>generalFamilyFont</entry> + + <entry>font-family</entry> + </row> + + <row> + <entry>generalSizeFont</entry> + + <entry>font-size</entry> + </row> + </tbody> + </tgroup> + </table> + + <table> + <title>Label Skin parameters redefinition</title> + + <tgroup cols="2"> + <thead> + <row> + <entry>Skin parameters for selected label element</entry> + + <entry>CSS properties</entry> + </row> + </thead> + + <tbody> + <row> + <entry>panelBorderColor</entry> + + <entry>border-color</entry> + </row> + + <row> + <entry>controlBackgroundColor</entry> + + <entry>background-color</entry> + </row> + + <row> + <entry>generalTextColor</entry> + + <entry>background-colorcolor</entry> + </row> + </tbody> + </tgroup> + </table> + + <table> + <title>Popup Skin parameters redefinition</title> + + <tgroup cols="2"> + <thead> + <row> + <entry>Skin parameters for border element</entry> + + <entry>CSS properties</entry> + </row> + </thead> + + <tbody> + <row> + <entry>panelBorderColor</entry> + + <entry>border-color</entry> + </row> + + <row> + <entry>additionalBackgroundColor</entry> + + <entry>background-color</entry> + </row> + </tbody> + </tgroup> + </table> + + <table> + <title>Popup Skin parameters redefinition</title> + + <tgroup cols="2"> + <thead> + <row> + <entry>Skin parameters for background element</entry> + + <entry>CSS properties</entry> + </row> + </thead> + + <tbody> + <row> + <entry>additionalBackgroundColor</entry> + + <entry>border-top-color</entry> + </row> + + <row> + <entry>additionalBackgroundColor</entry> + + <entry>border-left-color</entry> + </row> + + <row> + <entry>additionalBackgroundColor</entry> + + <entry>border-right-color</entry> + </row> + </tbody> + </tgroup> + </table> + </section> + + <section> + <title>Definition of Custom Style Classes</title> + + <para>In the screenshot, there are classes names that define the element + label.</para> + + <figure> + <title>Classes names</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/dropDownMenu4.png" /> + </imageobject> + </mediaobject> + </figure> + + <table> + <title>Classes names that define element label</title> + + <tgroup cols="2"> + <thead> + <row> + <entry>Class name</entry> + + <entry>Description</entry> + </row> + </thead> + + <tbody> + <row> + <entry>Rich-label-text-decor</entry> + + <entry>Defines the text style of a representation element</entry> + </row> + + <row> + <entry>Rich-ddmenu-label</entry> + + <entry>Defines the class for wrapping div element of a + representation element</entry> + </row> + + <row> + <entry>Rich-ddmenu-label-select</entry> + + <entry>Defines the class for wrapping div element of the selected + representation element</entry> + </row> + + <row> + <entry>Rich-ddmenu-label-unselect</entry> + + <entry>Defines the class for wrapping div element of a + representation element that isn't selected</entry> + </row> + </tbody> + </tgroup> + </table> + + <para>In the screenshot, there are classes names that define an element + pop-up.</para> + + <figure> + <title>Classes names</title> + + <mediaobject> + <imageobject> + <imagedata fileref="images/dropDownMenu5.png" /> + </imageobject> + </mediaobject> + </figure> + + <table> + <title>Classes names that define element popup</title> + + <tgroup cols="2"> + <thead> + <row> + <entry>Class name</entry> + + <entry>Description</entry> + </row> + </thead> + + <tbody> + <row> + <entry>Rich-menu-list-border</entry> + + <entry>Defines a class for borders elements</entry> + </row> + + <row> + <entry>Rich-menu-list-border</entry> + + <entry>Defines the class for a general background list</entry> + </row> + </tbody> + </tgroup> + </table> + + <para>In order to redefine the style for all drop-down menus 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 the style peculiarities of the particular drop-down menus + define your own style classes in the corresponding dropDownMenu + attributes.</para> + </section> +</section> \ No newline at end of file Modified: trunk/docs/userguide/en/included/dropSupport.xml =================================================================== --- trunk/docs/userguide/en/included/dropSupport.xml 2007-05-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/dropSupport.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -222,7 +222,7 @@ </section> <section> - <title>Look and Feel Customization</title> + <title>Look-and-Feel Customization</title> <para>The component doesn&apos;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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/dropZone.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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&apos;t have its own representation. Therefore, for a wrapper <emphasis role="bold"><property>&lt;div&gt;</property></emphasis> element customization it&apos;s Modified: trunk/docs/userguide/en/included/gmap.xml =================================================================== --- trunk/docs/userguide/en/included/gmap.xml 2007-05-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/gmap.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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&apos;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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/inputNumberSlider.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/inputNumberSpinner.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/menuGroup.desc.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -7,7 +7,7 @@ </sectioninfo> <section> <title>Description</title> - <para>The &lt;rich:menuGroup&gt; component is used to define an expandable group of items inside of a popup list or another group.</para> + <para>The &lt;rich:menuGroup&gt; component is used to define an expandable group of items inside a pop-up list or another group.</para> <figure> <title>&lt;rich:menuGroup&gt; 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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/menuGroup.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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 &quot;value&quot; attribute defines text representation of a group element on a page. + The &quot;value&quot; attribute defines the text representation of a group element in the page. </para> <para> - The &quot;icon&quot; attribute defines an icon. The &quot;iconDisabled&quot; attribute defines an icon for a disabled group. Also you can use the &quot;icon&quot; and &quot;iconDisabled&quot; facets. If the facets are defined, the corresponding &quot;icon&quot; and &quot;iconDisabled&quot; attributes are ignored and facets content is shown as icon. It could be used for items checkboxes implementation. + The &quot;icon&quot; attribute defines an icon for the component. The &quot;iconDisabled&quot; attribute defines an icon for when the group is disabled. Also you can use the &quot;icon&quot; and &quot;iconDisabled&quot; facets. If the facets are defined, the corresponding &quot;icon&quot; and &quot;iconDisabled&quot; 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 &quot;iconFolder&quot; and &quot;iconFolderDisabled&quot; attributes are defined for using icons as a folder icon. The &quot;iconFolder&quot; and &quot;iconFolderDisabled&quot; facets use content as folder icon representation. + The &quot;iconFolder&quot; and &quot;iconFolderDisabled&quot; attributes are defined for using icons as folder icons. The &quot;iconFolder&quot; and &quot;iconFolderDisabled&quot; facets use their contents as folder icon representations in place of the attribute values. </para> <para> - The &quot;direction&quot; attribute is used to define the ways of menu&apos;s appearance as it&apos;s shown in the example below. + The &quot;direction&quot; 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 &quot;direction&quot; attribute is defined as &quot;auto&quot;. + By default, the &quot;direction&quot; attribute is set to &quot;auto&quot;. </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 &quot;direction&quot; 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&apos;s stylesheets style classes used by a menuGroup.</para></listitem> + <listitem><para>Redefine corresponding skin parameters</para></listitem> + <listitem><para>Add to user&apos;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&apos;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&apos;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.desc.xml =================================================================== --- trunk/docs/userguide/en/included/menuItem.desc.xml 2007-05-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/menuItem.desc.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -7,7 +7,7 @@ </sectioninfo> <section> <title>Description</title> - <para>The <emphasis role="bold">&lt;rich:menuItem&gt;</emphasis> component is used for definition the single item inside of popup list.</para> + <para>The <emphasis role="bold">&lt;rich:menuItem&gt;</emphasis> component is used for the definition of a single item inside a pop-up list.</para> <figure> <title>&lt;rich:menuItem&gt; component</title> <mediaobject> @@ -20,9 +20,9 @@ <section> <title>Key Features</title> <itemizedlist> - <listitem><para>Highly customizable look and feel</para></listitem> + <listitem><para>Highly customizable look-and-feel</para></listitem> <listitem><para>Different submission modes</para></listitem> - <listitem><para>Disablement support</para></listitem> + <listitem><para>Support for disabling</para></listitem> <listitem><para>Custom content support</para></listitem> </itemizedlist> Modified: trunk/docs/userguide/en/included/menuItem.xml =================================================================== --- trunk/docs/userguide/en/included/menuItem.xml 2007-05-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/menuItem.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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> ... @@ -53,7 +53,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.HtmlMenuItem myItem = new org.richfaces.component.html.HtmlMenuItem (); ...]]></programlisting> @@ -62,13 +62,13 @@ <section> <title>Details of Usage</title> <para> - The &quot;value&quot; attribute defines text representation for an item element. + The &quot;value&quot; attribute defines the text representation for an item element. </para> <para> - The &quot;icon&quot; attribute defines an icon. The &quot;iconDisabled&quot; attribute defines an icon for a disabled item. Also you can use the &quot;icon&quot; and &quot;iconDisabled&quot; facets. If the facets are defined, the corresponding &quot;icon&quot; and &quot;iconDisabled&quot; attributes are ignored and the facets content is shown as an icon. It could be used for items checkboxes implementation. + There are two icon-related attributes. The &quot;icon&quot; attribute defines an icon. The &quot;iconDisabled&quot; attribute defines an icon for a disabled item. Also you can use the &quot;icon&quot; and &quot;iconDisabled&quot; facets. If the facets are defined, the corresponding &quot;icon&quot; and &quot;iconDisabled&quot; attributes are ignored and the facets content is shown as an icon. It 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"> @@ -76,32 +76,41 @@ </f:facet> ...]]></programlisting> + <para>The &lt;rich: menuItem&gt; "mode" attribute can be set to three + possible parameters:</para> + + <itemizedlist> + <listitem> + <para>Server (default)</para> + </listitem> + </itemizedlist> + + <para>The standard form submission is performed and the page is completely + refreshed.</para> + + <itemizedlist> + <listitem> + <para>Ajax</para> + </listitem> + </itemizedlist> + + <para>An AJAX form submission is performed, and specified elements in the + "reRender" attribute are rerendered.</para> + + <itemizedlist> + <listitem> + <para>None</para> + </listitem> + </itemizedlist> + + <para>The "action" and "actionListener" item's attributes are ignored. + Menu items don't fire any submits themselves. The behavior is fully + defined by the components nested inside items.</para> <para> - A switching mode could be chosen with the &lt;rich: menuItem&gt; attribute &quot;mode&quot; with three possible parameters. + For example, you can put any content into an item, but, in this case, you should set the &quot;mode&quot; attribute as &quot;none&quot;. </para> - <itemizedlist> - <listitem><para>Server (on default)</para></listitem> - </itemizedlist> <para> - The common submission of the form is performed and a page is completely refreshed. - </para> - <itemizedlist> - <listitem><para>Ajax</para></listitem> - </itemizedlist> - <para> - Ajax form submission is performed, additionally specified elements in the &quot;reRender&quot; attribute are reRendered. - </para> - <itemizedlist> - <listitem><para>None</para></listitem> - </itemizedlist> - <para> - The &quot;action&quot; and &quot;actionListener&quot; items attributes are ignored. Menu items don&apos;t fire any submits itself. Behavior is fully defined by components nested to items. - </para> - <para> - For example, you can put any content into an item but in this case you should set the &quot;mode&quot; attribute as &quot;none&quot;. - </para> - <para> - Example. + Here is an example: </para> <programlisting role="xml"><![CDATA[... <rich:dropDownMenu> @@ -113,10 +122,10 @@ <rich:dropDownMenu> ...]]></programlisting> <para> - You can use the &quot;disabled&quot; attribute to set item state. + You can use the &quot;disabled&quot; attribute to set the item state. </para> <para> - Example. + Here is an example: </para> <programlisting role="xml"><![CDATA[... <rich:dropDownMenu> @@ -126,22 +135,22 @@ </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 menuItems at once: + There are two ways to redefine the appearance of all menuItems at once: </para> <itemizedlist> - <listitem><para>Redefine corresponding skin parameters.</para></listitem> - <listitem><para>Add to user&apos;s stylesheets style classes used by a menuItem.</para></listitem> + <listitem><para>Redefine the corresponding skin parameters</para></listitem> + <listitem><para>Add to user&apos;s stylesheets style classes used by a menuItem</para></listitem> </itemizedlist> </section> <section> <title>Skin parameters redefinition</title> <table> - <title>Label Skin parameters redefinition</title> + <title>Label skin parameters redefinition</title> <tgroup cols="2"> <thead> <row> @@ -163,7 +172,7 @@ </table> <table> - <title>Label Skin parameters redefinition</title> + <title>Label skin parameters redefinition</title> <tgroup cols="2"> <thead> <row> @@ -185,7 +194,7 @@ </table> <table> - <title>Label Skin parameters redefinition</title> + <title>Label skin parameters redefinition</title> <tgroup cols="2"> <thead> <row> @@ -203,7 +212,7 @@ </table> <table> - <title>Label Skin parameters redefinition</title> + <title>Label skin parameters redefinition</title> <tgroup cols="2"> <thead> <row> @@ -222,12 +231,12 @@ </section> <section> - <title> Definition custom style classes </title> + <title> Definition of Custom Style Classes </title> <para> - On the screenshot, there are classes names that define item element appearance. + In the screenshot, the classes names that define item element appearance are shown. </para> <figure> - <title>Classes names</title> + <title>Class names</title> <mediaobject> <imageobject> <imagedata fileref="images/menuItem2.png" /> @@ -235,7 +244,7 @@ </mediaobject> </figure> <table> - <title>Classes names that define item element appearance.</title> + <title>Class names that define item element appearance.</title> <tgroup cols="2"> <thead> <row> @@ -260,10 +269,10 @@ </tgroup> </table> <para> - All listed elements except of general are defined for disabled, enabled and hovered modes. + All listed elements except the general ones are defined for disabled, enabled, and hovered modes. </para> <table> - <title>Classes names for modes</title> + <title>Class names for modes</title> <tgroup cols="2"> <thead> <row> @@ -306,17 +315,17 @@ <entry>Defines properties for the text</entry> </row> <row> - <entry>Rich-menu-item-icon-selectedr</entry> + <entry>Rich-menu-item-icon-selected</entry> <entry>Defines properties for the left icon element</entry> </row> </tbody> </tgroup> </table> <para> - In order to redefine style for all menuItems on a page using CSS, it&apos;s enough to create classes with the same names and define the necessary properties in them. + In order to redefine the style for all menuItems on a page using CSS, it&apos;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 menuItems define your own style classes in the corresponding simple menuItem attributes. + To change the style of particular menuItems define your own style classes in the corresponding menuItem attributes. </para> </section> </section> Modified: trunk/docs/userguide/en/included/menuSeparator.desc.xml =================================================================== --- trunk/docs/userguide/en/included/menuSeparator.desc.xml 2007-05-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/menuSeparator.desc.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -7,7 +7,7 @@ </sectioninfo> <section> <title>Description</title> - <para>The &lt;rich:menuSeparator&gt; component is used for definition of a horizontal separator that can be placed between groups or items.</para> + <para>The &lt;rich:menuSeparator&gt; component is used for the definition of a horizontal separator that can be placed between groups or items.</para> <figure> <title>&lt;rich:menuSeparator&gt;</title> <mediaobject> Modified: trunk/docs/userguide/en/included/menuSeparator.xml =================================================================== --- trunk/docs/userguide/en/included/menuSeparator.xml 2007-05-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/menuSeparator.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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/> ... @@ -53,29 +53,29 @@ </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.HtmlMenuSeparator mySep = new org.richfaces.component.html.HtmlMenuSeparator (); ...]]></programlisting> </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 menuSeparators at once: + There are two ways to redefine the appearance of all menuSeparators at once: </para> <itemizedlist> - <listitem><para>Redefine corresponding skin parameters.</para></listitem> - <listitem><para>Add to user&apos;s stylesheets style classes used by a menuSeparator.</para></listitem> + <listitem><para>Redefine the corresponding skin parameters</para></listitem> + <listitem><para>Add to user&apos;s stylesheets style classes used by a menuSeparator</para></listitem> </itemizedlist> </section> <section> - <title>Skin parameters redefinition</title> + <title>Redefinition of Skin Parameters</title> <table> - <title>Label Skin parameters redefinition</title> + <title>Label skin parameters redefinition</title> <tgroup cols="2"> <thead> <row> @@ -93,9 +93,9 @@ </table> </section> <section> - <title> Definition custom style classes </title> + <title>Definition of Custom Style Classes</title> <para> - On the screenshot, there are classes names that define separator element appearance. + In the screenshot, there are the classes names that define separator element appearance. </para> <figure> <title>Classes names</title> @@ -123,10 +123,10 @@ </tgroup> </table> <para> - In order to redefine style for all menuSeparators on a page using CSS, it&apos;s enough to create classes with the same names and define the necessary properties in them. + In order to redefine a style for all menuSeparators in a page using CSS, it&apos;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 menuSeparators define your own style classes in the corresponding simple menuSeparator attributes. + To change the style peculiarities of the particular menuSeparators, define your own style classes in the corresponding menuSeparator attributes. </para> </section> </section> Modified: trunk/docs/userguide/en/included/modalPanel.xml =================================================================== --- trunk/docs/userguide/en/included/modalPanel.xml 2007-05-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/modalPanel.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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">... &lt;rich:modalPanel id="panel"&gt; @@ -202,7 +202,7 @@ <property>"resizeable"</property> </emphasis> and <emphasis role="italic"> <property>"moveable"</property> - </emphasis> attributes to &quot;true&quot; or &quot;false&quot; values. Window resizing is + </emphasis> attributes to �true� or �false� values. Window resizing is also limited by <emphasis role="italic"> <property>"minWidth"</property> </emphasis> and <emphasis role="italic"> @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/paint2D.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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&apos;s method on the server.</para> Modified: trunk/docs/userguide/en/included/panel.xml =================================================================== --- trunk/docs/userguide/en/included/panel.xml 2007-05-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/panel.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/panelBar.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/panelBarItem.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/separator.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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&apos;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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/simpleTogglePanel.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/spacer.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/subTable.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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&apos;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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/suggestionBox.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/tab.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/tabPanel.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/toggleControl.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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>&quot;switchToState&quot;</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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/togglePanel.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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&apos;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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/toolBar.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/toolBarGroup.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/tree.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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--> @@ -105,32 +105,8 @@ in 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> - - <para> - The <emphasis role="italic"><property>&quot;icon&quot;</property></emphasis>, - <emphasis role="italic"><property>&quot;iconCollapsed&quot;</property></emphasis>, - <emphasis role="italic"><property>&quot;iconExpanded&quot;</property></emphasis> - attributes define icons for the component. Also you can use the facets with the same names. If the facets are defined, - the corresponding attributes are ignored and the facets' contents are used as icons. Maximum width of rendered facet area is 16 px. - <programlisting role="JAVA"><![CDATA[ -<rich:tree ....> - ... - <f:facet name="icon"> - <hutputText value="A"/> - </f:facet> - <f:facet name="iconCollapsed"> - <hutputText value="B"/> - </f:facet> - <f:facet name="iconExpanded"> - <hutputText value="C"/> - </f:facet> - ... -</rich:tree> -]]></programlisting></para> - - </section> - + on recovery or cashing data saving the Id on caching.</para> + </section> <section> <title>Built-In Drag and Drop</title> <para>The tree component functionality provides a built-in support for Drag and Drop operations. @@ -210,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-23 15:00:59 UTC (rev 843) +++ trunk/docs/userguide/en/included/treeNode.xml 2007-05-23 15:23:56 UTC (rev 844) @@ -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=&quot;data&quot; 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>