Author: smukhina Date: 2007-07-04 09:13:57 -0400 (Wed, 04 Jul 2007) New Revision: 1463 Modified: trunk/docs/userguide/en/src/main/docbook/included/column.desc.xml trunk/docs/userguide/en/src/main/docbook/included/column.xml trunk/docs/userguide/en/src/main/docbook/included/columnGroup.xml trunk/docs/userguide/en/src/main/docbook/included/dataDefinitionList.xml trunk/docs/userguide/en/src/main/docbook/included/dataFilterSlider.xml trunk/docs/userguide/en/src/main/docbook/included/dataGrid.xml trunk/docs/userguide/en/src/main/docbook/included/dataList.xml trunk/docs/userguide/en/src/main/docbook/included/dataOrderedList.xml trunk/docs/userguide/en/src/main/docbook/included/dataTable.xml trunk/docs/userguide/en/src/main/docbook/included/datascroller.xml trunk/docs/userguide/en/src/main/docbook/included/dragIndicator.xml trunk/docs/userguide/en/src/main/docbook/included/dragIndicator1.xml trunk/docs/userguide/en/src/main/docbook/included/dragSupport.xml trunk/docs/userguide/en/src/main/docbook/included/draggable.xml trunk/docs/userguide/en/src/main/docbook/included/dropSupport.xml trunk/docs/userguide/en/src/main/docbook/included/dropZone.xml trunk/docs/userguide/en/src/main/docbook/included/gmap.xml trunk/docs/userguide/en/src/main/docbook/included/inputNumberSlider.xml trunk/docs/userguide/en/src/main/docbook/included/inputNumberSpinner.desc.xml trunk/docs/userguide/en/src/main/docbook/included/inputNumberSpinner.xml trunk/docs/userguide/en/src/main/docbook/included/modalPanel.xml trunk/docs/userguide/en/src/main/docbook/included/paint2D.xml trunk/docs/userguide/en/src/main/docbook/included/panel.xml trunk/docs/userguide/en/src/main/docbook/included/panelBar.xml trunk/docs/userguide/en/src/main/docbook/included/panelBarItem.xml trunk/docs/userguide/en/src/main/docbook/included/panelMenu.desc.xml trunk/docs/userguide/en/src/main/docbook/included/separator.desc.xml trunk/docs/userguide/en/src/main/docbook/included/separator.xml trunk/docs/userguide/en/src/main/docbook/included/simpleTogglePanel.xml trunk/docs/userguide/en/src/main/docbook/included/spacer.xml trunk/docs/userguide/en/src/main/docbook/included/subTable.xml trunk/docs/userguide/en/src/main/docbook/included/suggestionBox.desc.xml trunk/docs/userguide/en/src/main/docbook/included/suggestionBox.xml trunk/docs/userguide/en/src/main/docbook/included/tab.xml trunk/docs/userguide/en/src/main/docbook/included/tabPanel.xml trunk/docs/userguide/en/src/main/docbook/included/toggleControl.desc.xml trunk/docs/userguide/en/src/main/docbook/included/toggleControl.xml trunk/docs/userguide/en/src/main/docbook/included/togglePanel.xml trunk/docs/userguide/en/src/main/docbook/included/toolBar.xml trunk/docs/userguide/en/src/main/docbook/included/toolBarGroup.xml trunk/docs/userguide/en/src/main/docbook/included/tree.xml trunk/docs/userguide/en/src/main/docbook/included/treeNode.xml Log: http://jira.jboss.org/jira/browse/EXIN-373 italic font style is added Modified: trunk/docs/userguide/en/src/main/docbook/included/column.desc.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/column.desc.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/column.desc.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -21,8 +21,8 @@ <title>Key Features</title> <itemizedlist> <listitem>Completely skinned table rows and child elements</listitem> - <listitem>Possibility to combine columns with the help of <emphasis role="italic"><property>&quot;colspan&quot;</property></emphasis></listitem> - <listitem>Possibility to combine rows with the help of <emphasis role="italic"><property>&quot;rowspan&quot;</property></emphasis> and <emphasis role="italic"><property>&quot;breakBefore&quot;</property></emphasis></listitem> + <listitem>Possibility to combine columns with the help of <emphasis ><property>&quot;colspan&quot;</property></emphasis></listitem> + <listitem>Possibility to combine rows with the help of <emphasis ><property>&quot;rowspan&quot;</property></emphasis> and <emphasis ><property>&quot;breakBefore&quot;</property></emphasis></listitem> </itemizedlist> </section> </section> \ No newline at end of file Modified: trunk/docs/userguide/en/src/main/docbook/included/column.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/column.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/column.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -97,9 +97,9 @@ </mediaobject> </figure> <para>Now, in order to group columns with text information into one row in one column with a flag, use - the <emphasis role="italic"><property>&quot;colspan&quot;</property></emphasis> attribute, which is similar to an HTML one, specifying that the first column contains 3 columns. + the <emphasis ><property>&quot;colspan&quot;</property></emphasis> attribute, which is similar to an HTML one, specifying that the first column contains 3 columns. In addition, it&apos;s necessary to specify that the next column begins from the first row with the help of the - <emphasis role="italic"><property>&quot;breakBefore&quot;</property></emphasis> attribute = true.</para> + <emphasis ><property>&quot;breakBefore&quot;</property></emphasis> attribute = true.</para> <programlisting role="XML"><![CDATA[... <rich:dataTable value="#{capitalsBean.capitals}" var="cap" rows="5"> <rich:column colspan="3"> @@ -126,7 +126,7 @@ </imageobject> </mediaobject> </figure> - <para>The same way is used for <property>columns</property> grouping with the <emphasis role="italic"><property>&quot;rowspan&quot;</property></emphasis> + <para>The same way is used for <property>columns</property> grouping with the <emphasis ><property>&quot;rowspan&quot;</property></emphasis> attribute that is similar to an HTML one responsible for rows quantity definition occupied with the current one. The only thing to add in the example is an instruction to move onto the next row for each next after the second column.</para> <programlisting role="XML"><![CDATA[... @@ -165,14 +165,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property></emphasis>.</para> +><property>style class redefinition method</property></emphasis>.</para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all columns at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis - role="italic"><property>style classes</property></emphasis> used by the column to your page style sheets</listitem> + ><property>style classes</property></emphasis> used by the column to your page style sheets</listitem> </itemizedlist> </section> <section> Modified: trunk/docs/userguide/en/src/main/docbook/included/columnGroup.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/columnGroup.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/columnGroup.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -68,7 +68,7 @@ <section> <title>Details of Usage</title> <para>The <emphasis role="bold"><property>&lt;rich:columnGroup&gt;</property></emphasis> component combines columns set wrapping them into the <emphasis role="bold"><property>&lt;tr&gt;</property></emphasis> element and outputting them - into one row. Columns are combined in a group the same way as when the <emphasis role="italic"><property>&quot;breakBefore&quot;</property></emphasis> attribute is used for + into one row. Columns are combined in a group the same way as when the <emphasis ><property>&quot;breakBefore&quot;</property></emphasis> attribute is used for columns to add a moving to the next rows, but the first variant is clearer from a source code. Hence, the following simple examples are very same.</para> <programlisting role="XML"><![CDATA[... @@ -150,14 +150,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property></emphasis>.</para> +><property>style class redefinition method</property></emphasis>.</para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all columnGroups at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis - role="italic"><property>style classes</property></emphasis> used by the columnGroup to your page style sheets</listitem> + ><property>style classes</property></emphasis> used by the columnGroup to your page style sheets</listitem> </itemizedlist> </section> <section> Modified: trunk/docs/userguide/en/src/main/docbook/included/dataDefinitionList.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/dataDefinitionList.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/dataDefinitionList.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -67,7 +67,7 @@ similar to ordinary UIData components output ways:</para> <itemizedlist> <listitem>A header and footer output</listitem> -<listitem>Limitation of the output elements (the <emphasis role="italic"><property>&quot;elements&quot;</property></emphasis> attribute) and definition of the first +<listitem>Limitation of the output elements (the <emphasis ><property>&quot;elements&quot;</property></emphasis> attribute) and definition of the first element</listitem> <listitem>Binding to scrolling components of list pages</listitem> </itemizedlist> @@ -89,14 +89,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property></emphasis>.</para> +><property>style class redefinition method</property></emphasis>.</para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all dataDefinitionList at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis - role="italic"><property>style classes</property></emphasis> used by the dataDefinitionList to your page style sheets</listitem> + ><property>style classes</property></emphasis> used by the dataDefinitionList to your page style sheets</listitem> </itemizedlist> </section> Modified: trunk/docs/userguide/en/src/main/docbook/included/dataFilterSlider.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/dataFilterSlider.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/dataFilterSlider.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -59,7 +59,7 @@ <section> <title>Details of Usage</title> <para>The <property>dataFilterSlider</property> component is bound to some UIData component using a - <emphasis role="italic"><property>&quot;for&quot;</property></emphasis> attribute and + <emphasis ><property>&quot;for&quot;</property></emphasis> attribute and filters data in this table. </para> <para><emphasis role="bold">Example:</emphasis></para> <programlisting role="XML"><![CDATA[... @@ -81,27 +81,27 @@ <para>In this example other two attributes are used for filtering:</para> <itemizedlist> <listitem> - <emphasis role="italic"><property>&quot;forValRef&quot;</property></emphasis> is a string + <emphasis ><property>&quot;forValRef&quot;</property></emphasis> is a string which is used in a value attribute of the target UIData component. It&apos;s designed for resetting the UIData component back to the original list provided by a backing bean. </listitem> <listitem> - <emphasis role="italic"><property>&quot;filterBy&quot;</property></emphasis> is a getter of + <emphasis ><property>&quot;filterBy&quot;</property></emphasis> is a getter of an object member that is to be compared to a slider value. It&apos;s a value that is used in results filtering. </listitem> </itemizedlist> -<para><emphasis role="italic"><property>&quot;handleValue&quot;</property></emphasis> is an attribute +<para><emphasis ><property>&quot;handleValue&quot;</property></emphasis> is an attribute for keeping the current handler position on the <property>dataFilterSlider</property> component. Based on the current value, appropriate values obtained from a getter method defined in - <emphasis role="italic"><property>&quot;filterBy&quot;</property></emphasis> are + <emphasis ><property>&quot;filterBy&quot;</property></emphasis> are filtered.</para> <para>One more important attribute is a -<emphasis role="italic"><property>&quot;storeResults&quot;</property></emphasis> one that allows the +<emphasis ><property>&quot;storeResults&quot;</property></emphasis> one that allows the <property>dataFilterSlider</property> component to keep UIData target object in session.</para> <para>If it&apos;s necessary the component submits a form on event of a handler state changing, use -the <emphasis role="italic"><property>&quot;onSlide&quot;</property></emphasis> attribute -(<emphasis role="italic"><property>&quot;onChange&quot;</property></emphasis> is its alias). When +the <emphasis ><property>&quot;onSlide&quot;</property></emphasis> attribute +(<emphasis ><property>&quot;onChange&quot;</property></emphasis> is its alias). When the attribute definition = true, submission on this event is defined.</para> <para> <ulink url="http://livedemo.exadel.com/richfaces-demo/richfaces/dataFilterS... you can see the example of <emphasis role="bold">&lt;rich:dataFilterSlider&gt;</emphasis> usage and sources for the given example. Modified: trunk/docs/userguide/en/src/main/docbook/included/dataGrid.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/dataGrid.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/dataGrid.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -67,7 +67,7 @@ The component also has similar to ordinary UIData components output ways.</para> <itemizedlist> <listitem>A header and footer output</listitem> -<listitem>Limitation of the output elements (the <emphasis role="italic"><property>&quot;elements&quot;</property></emphasis> attribute) and definition of the first +<listitem>Limitation of the output elements (the <emphasis ><property>&quot;elements&quot;</property></emphasis> attribute) and definition of the first element</listitem> <listitem>Binding to scrolling components of list pages</listitem> </itemizedlist> @@ -93,14 +93,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property></emphasis>.</para> +><property>style class redefinition method</property></emphasis>.</para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all dataGrids at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis - role="italic"><property>style classes</property></emphasis> used by the dataGrid to your page style sheets</listitem> + ><property>style classes</property></emphasis> used by the dataGrid to your page style sheets</listitem> </itemizedlist> </section> @@ -111,7 +111,7 @@ <para>To redefine an appearance of all <property>dataGrids</property> on a page, redefine the corresponding class in the CSS file used with the page.</para> - <para>To redefine a style of a particular table, use <emphasis role="italic"><property>&quot;component class&quot;</property></emphasis> attributes which list is the same + <para>To redefine a style of a particular table, use <emphasis ><property>&quot;component class&quot;</property></emphasis> attributes which list is the same as the <property>dataTable</property> one and is known to you.</para> </section> </section> Modified: trunk/docs/userguide/en/src/main/docbook/included/dataList.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/dataList.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/dataList.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -67,11 +67,11 @@ similar to ordinary UIData components output ways:</para> <itemizedlist> <listitem>A header and footer output</listitem> -<listitem>Limitation of the output elements (the <emphasis role="italic"><property>&quot;elements&quot;</property></emphasis> attribute) and definition of the first +<listitem>Limitation of the output elements (the <emphasis ><property>&quot;elements&quot;</property></emphasis> attribute) and definition of the first element</listitem> <listitem>Binding to scrolling components of list pages</listitem> </itemizedlist> - <para>The component has the <emphasis role="italic"><property>&quot;type&quot;</property></emphasis> attribute corresponding to the &quot;ul&quot; HTML element.</para> + <para>The component has the <emphasis ><property>&quot;type&quot;</property></emphasis> attribute corresponding to the &quot;ul&quot; HTML element.</para> <para>The component is created basing on the <emphasis role="bold"><property>&lt;a4j:repeat&gt;</property></emphasis> component and as a result the component could be partially updated with AJAX.</para> <programlisting role="XML"><![CDATA[... @@ -89,14 +89,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property></emphasis>.</para> +><property>style class redefinition method</property></emphasis>.</para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all dataLists at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis - role="italic"><property>style classes</property></emphasis> used by the dataList to your page style sheets</listitem> + ><property>style classes</property></emphasis> used by the dataList to your page style sheets</listitem> </itemizedlist> </section> Modified: trunk/docs/userguide/en/src/main/docbook/included/dataOrderedList.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/dataOrderedList.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/dataOrderedList.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -66,11 +66,11 @@ similar to ordinary UIData components output ways:</para> <itemizedlist> <listitem>Header and footer output</listitem> -<listitem>Limitation of the output elements (the <emphasis role="italic"><property>&quot;elements&quot;</property></emphasis> attribute) and definition of the first +<listitem>Limitation of the output elements (the <emphasis ><property>&quot;elements&quot;</property></emphasis> attribute) and definition of the first element</listitem> <listitem>Binding to scrolling components of list pages</listitem> </itemizedlist> - <para>The component has the <emphasis role="italic"><property>&quot;type&quot;</property></emphasis> attribute corresponding to the &quot;ul&quot; HTML element.</para> + <para>The component has the <emphasis ><property>&quot;type&quot;</property></emphasis> attribute corresponding to the &quot;ul&quot; HTML element.</para> <para>The component is created basing on the <emphasis role="bold"><property>&lt;a4j:repeat&gt;</property></emphasis> component and as a result the component could be partially updated with AJAX.</para> <programlisting role="XML"><![CDATA[... @@ -88,14 +88,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property></emphasis>.</para> +><property>style class redefinition method</property></emphasis>.</para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all dataOrderedLists at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis - role="italic"><property>style classes</property></emphasis> used by the dataOrderedList to your page style sheets</listitem> + ><property>style classes</property></emphasis> used by the dataOrderedList to your page style sheets</listitem> </itemizedlist> </section> Modified: trunk/docs/userguide/en/src/main/docbook/included/dataTable.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/dataTable.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/dataTable.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -72,7 +72,7 @@ <para>Skins support is described in the <link linkend="ArchitectureOverview">corresponding section</link>. AJAX support is possible because the component is created basing on the <emphasis role="bold"><property>&lt;a4j:repeat&gt;</property></emphasis> component and as a result the component has its possibilities of AJAX updates for a limited set of strings. - The component is implemented with the <emphasis role="italic"><property>&quot;ajaxKeys&quot;</property></emphasis> attribute for a <property>table</property> and in contrast to + The component is implemented with the <emphasis ><property>&quot;ajaxKeys&quot;</property></emphasis> attribute for a <property>table</property> and in contrast to the <emphasis role="bold"><property>&lt;a4j:repeat&gt;</property></emphasis> outputs the standard HTML structure for table rendering.</para> <programlisting role="XML"><![CDATA[... <rich:dataTable value="#{capitalsBean.capitals}" var="capitals" @@ -94,14 +94,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property></emphasis>.</para> +><property>style class redefinition method</property></emphasis>.</para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all dataTables at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis -role="italic"><property>style classes</property></emphasis> used by the dataTable to your page style sheets</listitem> +><property>style classes</property></emphasis> used by the dataTable to your page style sheets</listitem> </itemizedlist> </section> <section> @@ -179,7 +179,7 @@ </table> <para>To redefine an appearance of all <property>tables</property> on a page, redefine the corresponding class in the CSS file used with the page.</para> - <para>To redefine a style of a particular page, use <emphasis role="italic"><property>&quot;component class&quot;</property></emphasis> attributes which list is the same + <para>To redefine a style of a particular page, use <emphasis ><property>&quot;component class&quot;</property></emphasis> attributes which list is the same as the <property>dataTable</property> one and is known to you.</para> </section> </section> Modified: trunk/docs/userguide/en/src/main/docbook/included/datascroller.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/datascroller.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/datascroller.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -68,11 +68,11 @@ <para>The <emphasis role="bold"><property>&lt;rich:Datascroller&gt;</property></emphasis> component provides table scrolling functionality the same as tomahawk scroller but with AJAX requests usage.</para> <para>The component should be placed into footer of the parent table or be bound to it with the - <emphasis role="italic"><property>&quot;for&quot;</property></emphasis> attribute.</para> - <para>The table should also have the defined <emphasis role="italic"><property>&quot;rows&quot;</property></emphasis> attribute limiting the quantity of inputted + <emphasis ><property>&quot;for&quot;</property></emphasis> attribute.</para> + <para>The table should also have the defined <emphasis ><property>&quot;rows&quot;</property></emphasis> attribute limiting the quantity of inputted table rows.</para> <para>The scroller could limit the maximum quantity of rendered links on the table pages with the - help of the <emphasis role="italic"><property>&quot;maxPages&quot;</property></emphasis> attribute.</para> + help of the <emphasis ><property>&quot;maxPages&quot;</property></emphasis> attribute.</para> <para>Component provides two controllers groups for switching:</para> <itemizedlist> <listitem>Page numbers for switching onto a particular page</listitem> @@ -104,7 +104,7 @@ </mediaobject> </figure> <para>The screenshot shows one controller from each group.</para> - <para>For the <property>&quot;fastforward&quot;</property>/<property>&quot;rewind&quot;</property> controls customization the additional <emphasis role="italic"><property>&quot;fastStep&quot;</property></emphasis> attribute is used. + <para>For the <property>&quot;fastforward&quot;</property>/<property>&quot;rewind&quot;</property> controls customization the additional <emphasis ><property>&quot;fastStep&quot;</property></emphasis> attribute is used. The attribute indicates pages quantity to switch onto when fast scrolling is used. </para> <para> <ulink url="http://livedemo.exadel.com/richfaces-demo/richfaces/dataTableSc... you can see the example of <emphasis role="bold">&lt;rich:dataScroller&gt;</emphasis> usage and sources for the given example. @@ -113,14 +113,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property>.</emphasis></para> +><property>style class redefinition method</property>.</emphasis></para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all dataScrollers at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis -role="italic"><property>style classes</property></emphasis> used by the dataScroller to your page style sheets</listitem> +><property>style classes</property></emphasis> used by the dataScroller to your page style sheets</listitem> </itemizedlist> </section> <section> Modified: trunk/docs/userguide/en/src/main/docbook/included/dragIndicator.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/dragIndicator.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/dragIndicator.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -92,14 +92,14 @@ <section> <title>Indicator icon element</title> <para>Inside the component there also could be definitions for three faces with - <emphasis role="italic"><property>&quot;accept&quot;</property>,</emphasis> - <emphasis role="italic"><property>&quot;reject&quot;</property></emphasis> and - <emphasis role="italic"><property>&quot;default&quot;</property></emphasis> names that specify icons on the left side according to states when an + <emphasis ><property>&quot;accept&quot;</property>,</emphasis> + <emphasis ><property>&quot;reject&quot;</property></emphasis> and + <emphasis ><property>&quot;default&quot;</property></emphasis> names that specify icons on the left side according to states when an <property>indicator</property> is above:</para> <itemizedlist> <listitem> a drop zone that processes the facets written in the - <emphasis role="italic"><property>&quot;acceptedTypes&quot;</property></emphasis> attribute + <emphasis ><property>&quot;acceptedTypes&quot;</property></emphasis> attribute of this drop zone </listitem> <listitem> @@ -119,7 +119,7 @@ <para>Each of these three facets have a default structure for icons rendering on the left side.</para> <para>When it&apos;s necessary to define individual icons for dragged above elements of a <property>drop zone</property> from each particular drag area, use a <property>drop zone</property> - <emphasis role="italic"><property>&quot;typeMapping&quot;</property></emphasis> attribute for the + <emphasis ><property>&quot;typeMapping&quot;</property></emphasis> attribute for the corresponding icons.</para> <programlisting role="XML"><![CDATA[... <rich:dropSupport acceptedTypes="[iconsDragged, textDragged]" typeMapping="{iconsDragged: DropIcon}"> @@ -131,7 +131,7 @@ ]]></programlisting> <para>Here, drag areas that are to be processed with this drop zone are of iconsDragged and textDragged type. An icon is redefined for iconsDragged with the help of the drop zone - <emphasis role="italic"><property>&quot;typeMapping&quot;</property></emphasis> attribute + <emphasis ><property>&quot;typeMapping&quot;</property></emphasis> attribute defined with the <emphasis role="bold"><property>&lt;rich:dndParam&gt;</property></emphasis>component.</para> <para> <ulink url="http://livedemo.exadel.com/richfaces-demo/richfaces/dragSupport... you can see the example of <emphasis role="bold">&lt;rich:dragIndicator&gt;</emphasis> usage and sources for the given example. Modified: trunk/docs/userguide/en/src/main/docbook/included/dragIndicator1.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/dragIndicator1.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/dragIndicator1.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -90,14 +90,14 @@ <section> <title>Indicator icon element</title> <para>Inside the component there also could be definitions for three faces with - <emphasis role="italic"><property>&quot;accept&quot;</property>,</emphasis> - <emphasis role="italic"><property>&quot;reject&quot;</property></emphasis> and - <emphasis role="italic"><property>&quot;default&quot;</property></emphasis> names that specify icons on the left side according to states when an + <emphasis ><property>&quot;accept&quot;</property>,</emphasis> + <emphasis ><property>&quot;reject&quot;</property></emphasis> and + <emphasis ><property>&quot;default&quot;</property></emphasis> names that specify icons on the left side according to states when an <property>indicator</property> is above:</para> <itemizedlist> <listitem> a drop zone that processes the facets written in the - <emphasis role="italic"><property>&quot;acceptedTypes&quot;</property></emphasis> attribute + <emphasis ><property>&quot;acceptedTypes&quot;</property></emphasis> attribute of this drop zone </listitem> <listitem> @@ -116,7 +116,7 @@ <para>Each of these three facets have a default structure for icons rendering on the left side.</para> <para>When it&apos;s necessary to define individual icons for dragged above elements of a <property>drop zone</property> from each particular drag area, use the <property>drop zone</property> - <emphasis role="italic"><property>&quot;typeMapping&quot;</property></emphasis> attribute for the + <emphasis ><property>&quot;typeMapping&quot;</property></emphasis> attribute for the corresponding icons.</para> <programlisting role="XML"><![CDATA[<rich:dropSupport acceptedTypes="[iconsDragged, textDragged]" typeMapping="{iconsDragged: DropIcon}"> @@ -128,7 +128,7 @@ ]]></programlisting> <para>Here, drag areas that are to be processed with this drop zone are of iconsDragged and textDragged type. An icon is redefined for iconsDragged with the help of the drop zone - <emphasis role="italic"><property>&quot;typeMapping&quot;</property></emphasis> attribute + <emphasis ><property>&quot;typeMapping&quot;</property></emphasis> attribute defined with the <emphasis role="bold"><property>&lt;rich:dndParam&gt;</property></emphasis>component.</para> </section> </section> Modified: trunk/docs/userguide/en/src/main/docbook/included/dragSupport.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/dragSupport.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/dragSupport.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -121,7 +121,7 @@ <para>This code makes all rows of this column draggable.</para> <para>One of the main attributes for <property>dragSupport</property> is - <emphasis role="italic"><property>"dragType"</property>,</emphasis> which + <emphasis ><property>"dragType"</property>,</emphasis> which associates a name with the drag zone. Only drop zones with this name as an acceptable type can be used in drag-and-drop operations. Here is an example:</para> @@ -153,14 +153,14 @@ drop.</para> <para>The <property>dragSupport</property> component also has a <emphasis - role="italic"> + > <property>"value"</property> </emphasis> attribute for passing data into the processing after a drop event.</para> <para>One more important attribute for <emphasis role="bold"> <property>&lt;rich:dragSupport&gt;</property> - </emphasis> is the <emphasis role="italic"> + </emphasis> is the <emphasis > <property>"dragIndicator"</property> </emphasis> attribute that point to the component id of the <emphasis role="bold"> Modified: trunk/docs/userguide/en/src/main/docbook/included/draggable.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/draggable.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/draggable.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -64,7 +64,7 @@ </section> <section> <title>Details of Usage</title> - <para>As it shown in the example, a key attribute is <emphasis role="italic"><property>&quot;dragType&quot;</property></emphasis>, where a name for an obtaining Drag-area is defined. Basing on this name, Drop-zones on a page decide whether to accept Drag-area content or not (with the help of Drag-areas lists accepted for processing that are defined in Drop-zones).</para> + <para>As it shown in the example, a key attribute is <emphasis ><property>&quot;dragType&quot;</property></emphasis>, where a name for an obtaining Drag-area is defined. Basing on this name, Drop-zones on a page decide whether to accept Drag-area content or not (with the help of Drag-areas lists accepted for processing that are defined in Drop-zones).</para> <para><emphasis role="bold">Example:</emphasis></para> <programlisting role="XML"><![CDATA[... <rich:draggable dragType="dragTextBlocks"> @@ -82,7 +82,7 @@ <para>The example shows that Drop zone calls the corresponding drop event processing in it, only if a drop is generated from the second drop zone. </para> <para>Another important attribute for - <emphasis role="bold"><property>&lt;rich:draggable&gt;</property></emphasis> is <emphasis role="italic"><property>&quot;dragIndicator&quot;</property></emphasis> where the + <emphasis role="bold"><property>&lt;rich:draggable&gt;</property></emphasis> is <emphasis ><property>&quot;dragIndicator&quot;</property></emphasis> where the <emphasis role="bold"><property>&lt;rich:dragIndicator&gt;</property></emphasis> component id is defined for this drag area. If it isn&apos;t defined drag area creates a default indicator for drag operation. Additional information on <emphasis role="bold"> <property>&lt;rich:dragIndicator&gt;</property> @@ -106,7 +106,7 @@ <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 - possible to use a component attribute <emphasis role="italic"><property>&quot;styleClass&quot;</property></emphasis> or + possible to use a component attribute <emphasis ><property>&quot;styleClass&quot;</property></emphasis> or redefine rich-draggable class in your own CSS files that is added to all <property>draggable</property> components style on default.</para> </section> Modified: trunk/docs/userguide/en/src/main/docbook/included/dropSupport.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/dropSupport.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/dropSupport.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -86,14 +86,14 @@ <para>As shown in the example, the key attribute for <emphasis role="bold"> <property>&lt;rich:dropSupport&gt;</property> - </emphasis> is <emphasis role="italic"> + </emphasis> is <emphasis > <property>"acceptedTypes"</property> </emphasis>. This attribute defines the types of draggable items that can be dropped onto the designated drop zone.</para> <para>The second most important attribute for <emphasis role="bold"> <property>&lt;rich:dropSupport&gt;</property> - </emphasis> is <emphasis role="italic"> + </emphasis> is <emphasis > <property>"typeMapping"</property> </emphasis>. This attribute maps a specific type among the acceptable types for draggable items to a specific <emphasis role="bold"> @@ -195,9 +195,9 @@ <para>As with every AJAX action component, <emphasis role="bold"> <property>&lt;rich:dropSupport&gt;</property> </emphasis> has all the common attributes (<emphasis - role="italic"><property>"timeout"</property>,</emphasis> <emphasis - role="italic"><property>"limitToList"</property>,</emphasis> <emphasis - role="italic"><property>"reRender"</property>,</emphasis> etc.) for AJAX + ><property>"timeout"</property>,</emphasis> <emphasis + ><property>"limitToList"</property>,</emphasis> <emphasis + ><property>"reRender"</property>,</emphasis> etc.) for AJAX request customization. To get detailed information on these attributes, read the <ulink url="http://labs.jboss.com/file-access/default/members/jbossajax4jsf... Modified: trunk/docs/userguide/en/src/main/docbook/included/dropZone.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/dropZone.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/dropZone.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -69,14 +69,14 @@ <section> <title>Details of Usage</title> <para>As it&apos;s shown in the example, a key attribute is - <emphasis role="italic"><property>&quot;acceptedTypes&quot;</property></emphasis>, where some + <emphasis ><property>&quot;acceptedTypes&quot;</property></emphasis>, where some Drag-zones names of drop elements responsible for drop-zone processing are defined, i.e. in the example of component creation on a page, drop zone calls the corresponding drop event processing, only if a drop comes from the above mentioned drag zone of the corresponding type. All zones of another type are ignored.</para> <para>Another important attribute for <emphasis role="bold"><property>&lt;rich:dropZone&gt;</property></emphasis> is - <emphasis role="italic"><property>&quot;typeMapping&quot;</property></emphasis>, where + <emphasis ><property>&quot;typeMapping&quot;</property></emphasis>, where corresponding order of <emphasis role="bold"><property>&lt;rich:dndParam&gt;</property></emphasis> wrapping is defined for a drop from each drag-zone type</para> <para><emphasis role="bold">Example:</emphasis></para> @@ -93,19 +93,19 @@ <para>Thus, here is a drag zone indicator of iconsDragged type that obtains DropIcon parameter the same one as richParam gets. </para> <para>As any AJAX action, <property>dropZone</property> has all custom attributes of AJAX requests - customization (<emphasis role="italic"><property>&quot;timeout&quot;</property></emphasis>, - <emphasis role="italic"><property>&quot;limitToList&quot;</property></emphasis>, - <emphasis role="italic"><property>&quot;reRender&quot;</property></emphasis>, etc). To read more + customization (<emphasis ><property>&quot;timeout&quot;</property></emphasis>, + <emphasis ><property>&quot;limitToList&quot;</property></emphasis>, + <emphasis ><property>&quot;reRender&quot;</property></emphasis>, etc). To read more about the attributes, follow <ulink url="https://ajax4jsf.dev.java.net/nonav/documentation/ajax-document... Developer Guide </ulink>link.</para> <para>For <property>dropZone</property> layout could be defined with a - <emphasis role="italic"><property>&quot;layout&quot;</property></emphasis> attribute with inline + <emphasis ><property>&quot;layout&quot;</property></emphasis> attribute with inline (default) and block values.</para> <para>As any action component <emphasis role="bold"><property>&lt;rich:dropZone&gt;</property></emphasis> has server-side action Listener defined with - <emphasis role="italic"><property>&quot;dropListener&quot;</property></emphasis> attribute as + <emphasis ><property>&quot;dropListener&quot;</property></emphasis> attribute as well as a definition of attributes for all required events processing on the client:</para> <itemizedlist> <listitem> @@ -124,7 +124,7 @@ <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 - possible to use a component attribute <emphasis role="italic"><property>&quot;styleClass&quot;</property></emphasis> or + possible to use a component attribute <emphasis ><property>&quot;styleClass&quot;</property></emphasis> or redefine a rich-dropzone class in your own CSS files that is added to all <property>dropZone</property> components style on default.</para> </section> Modified: trunk/docs/userguide/en/src/main/docbook/included/gmap.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/gmap.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/gmap.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -60,33 +60,33 @@ </section> <section> <title>Details of Usage</title> - <para>To use <emphasis role="italic"><property>Google Map</property></emphasis> in your + <para>To use <emphasis ><property>Google Map</property></emphasis> in your application, generate a key on <ulink url="http://google.com/apis/maps">Google Map official resource</ulink>. One key could be used for one directory on the server.</para> <para>Here are the main settings of initial rendering performed with a component <property>map</property> that are accessible with the following attributes:</para> <itemizedlist> <listitem> - <emphasis role="italic"><property>&quot;zoom&quot;</property></emphasis> defines an + <emphasis ><property>&quot;zoom&quot;</property></emphasis> defines an approximation size (boundary values 1-18) </listitem> <listitem> - <emphasis role="italic"><property>&quot;lat&quot;</property></emphasis> specifies an initial + <emphasis ><property>&quot;lat&quot;</property></emphasis> specifies an initial latitude coordinate in degrees, as a number between -90 and +90 </listitem> <listitem> - <emphasis role="italic"><property>&quot;lng&quot;</property></emphasis> specifies an initial + <emphasis ><property>&quot;lng&quot;</property></emphasis> specifies an initial longitude coordinate in degrees, as a number between -180 and +180 </listitem> <listitem> - <emphasis role="italic"><property>&quot;mapType&quot;</property></emphasis> specifies a type + <emphasis ><property>&quot;mapType&quot;</property></emphasis> specifies a type of a rendered map (G_NORMAL_MAP, G_SATELLITE_MAP (DEFAULT), G_HYBRID_MAP) </listitem> </itemizedlist> <para>For example, the city of Paris is shown after rendering with the following - initial settings: <emphasis role="italic"><property>&quot;lat&quot;</property></emphasis>= 48.44, - <emphasis role="italic"><property>&quot;lng&quot;</property></emphasis>= 2.24 and - <emphasis role="italic"><property>&quot;zoom&quot;</property></emphasis>= 5.</para> + initial settings: <emphasis ><property>&quot;lat&quot;</property></emphasis>= 48.44, + <emphasis ><property>&quot;lng&quot;</property></emphasis>= 2.24 and + <emphasis ><property>&quot;zoom&quot;</property></emphasis>= 5.</para> <figure> <title>Gmap initial rendering</title> <mediaobject> @@ -100,15 +100,15 @@ of the attributes:</para> <itemizedlist> <listitem> - <emphasis role="italic"><property>&quot;showGMapTypeControl&quot;</property></emphasis> + <emphasis ><property>&quot;showGMapTypeControl&quot;</property></emphasis> determines whether the controls for a map type definition are switched on </listitem> <listitem> - <emphasis role="italic"><property>&quot;showGScaleControl&quot;</property></emphasis> + <emphasis ><property>&quot;showGScaleControl&quot;</property></emphasis> determines whether the controls for scaling are switched on </listitem> <listitem> - <emphasis role="italic"><property>&quot;showGLargeMapControl&quot;</property></emphasis> + <emphasis ><property>&quot;showGLargeMapControl&quot;</property></emphasis> determines whether the control for <property>map</property> scale rendering is rendered </listitem> </itemizedlist> @@ -122,11 +122,11 @@ </figure> <para>To set all these parameters and perform some activity (Zoom In/Out etc.) is possible with your JavaScript, i.e. declare a name of an object on a <property>map</property> in the -<emphasis role="italic"><property>&quot;gmapVar&quot;</property></emphasis> attribute +<emphasis ><property>&quot;gmapVar&quot;</property></emphasis> attribute and then call the object directly with API -<emphasis role="italic"><property>Google Map</property>.</emphasis></para> +<emphasis ><property>Google Map</property>.</emphasis></para> <para>For example, to approximate a map for - <emphasis role="italic"><property>&quot;gmapVar&quot;</property></emphasis>= <property>&quot;map&quot;</property> + <emphasis ><property>&quot;gmapVar&quot;</property></emphasis>= <property>&quot;map&quot;</property> declared inside the component, call map.zoomIn() on an event.</para> <para>Moreover, to add e.g. some JavaScript effects, events defined on it are used.</para> <itemizedlist> @@ -151,7 +151,7 @@ <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> + <emphasis ><property>Google Map</property>.</emphasis></para> </section> <section> <title>Definition custom style classes:</title> Modified: trunk/docs/userguide/en/src/main/docbook/included/inputNumberSlider.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/inputNumberSlider.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/inputNumberSlider.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -63,11 +63,11 @@ used to facilitate user data input with rich UI Controls.</para> <para>Here is the simplest variant of a slider definition with <emphasis -role="italic"><property>&quot;minValue&quot;</property>,</emphasis> <emphasis +><property>&quot;minValue&quot;</property>,</emphasis> <emphasis -role="italic"><property>&quot;maxValue&quot;</property></emphasis> and <emphasis +><property>&quot;maxValue&quot;</property></emphasis> and <emphasis -role="italic"><property>&quot;step&quot;</property></emphasis> (on default = &quot;1&quot;) attributes, +><property>&quot;step&quot;</property></emphasis> (on default = &quot;1&quot;) attributes, which define the beginning and the end of a numerical area and a <property>slider</property> property step.</para> @@ -83,11 +83,11 @@ </mediaobject> </figure> <para> - Using <emphasis role="italic"><property>&quot;showInput&quot;</property></emphasis> (default is true) and - <emphasis role="italic"><property>&quot;enableManualInput&quot;</property></emphasis> (default value is + Using <emphasis ><property>&quot;showInput&quot;</property></emphasis> (default is true) and + <emphasis ><property>&quot;enableManualInput&quot;</property></emphasis> (default value is true) attributes, it&apos;s possible to output the input area near the slider, and make it read-only or editable.</para> - <para>To remove input area use <emphasis role="italic"><property>&quot;showInput=&quot;false&quot;</property></emphasis>:</para> + <para>To remove input area use <emphasis ><property>&quot;showInput=&quot;false&quot;</property></emphasis>:</para> <programlisting role="XML"><![CDATA[<rich:inputNumberSlider minValue="1" maxValue="100" showInput="false"/>]]></programlisting> <para>It looks at page like:</para> <figure> @@ -100,8 +100,8 @@ </figure> <para>It&apos;s also possible to switch off displaying of &quot;boundary values&quot; and a tooltip showing on a handle drawing. This could be performed with the help of the component defined - attributes: <emphasis role="italic"><property>&quot;showBoundaryValues&quot;</property></emphasis> which is responsible for -&quot;boundary values&quot; displaying (default is true) and <emphasis role="italic"><property>&quot;showToolTip&quot;</property></emphasis> which is responsible for + attributes: <emphasis ><property>&quot;showBoundaryValues&quot;</property></emphasis> which is responsible for +&quot;boundary values&quot; displaying (default is true) and <emphasis ><property>&quot;showToolTip&quot;</property></emphasis> which is responsible for tooltip displaying (default is true).</para> <para>Moreover, to add e.g. some JavaScript effects, events defined on it are used.</para> @@ -132,14 +132,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property></emphasis>.</para> +><property>style class redefinition method</property></emphasis>.</para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all inputNumberSliders at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis -role="italic"><property>style classes</property></emphasis> used by the inputNumberSlider to your page style sheets</listitem> +><property>style classes</property></emphasis> used by the inputNumberSlider to your page style sheets</listitem> </itemizedlist> <table> <title>Skin parameters redefinition:</title> Modified: trunk/docs/userguide/en/src/main/docbook/included/inputNumberSpinner.desc.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/inputNumberSpinner.desc.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/inputNumberSpinner.desc.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -10,7 +10,7 @@ <para>A single line input field that lets selecting a number using controls near a text field. It&apos;s possible to change a value using &quot;Up/Down&quot; keyboard keys. The keyboard input in a field is possible if it isn&apos;t locked by the - <emphasis role="italic"><property>&quot;manualInput&quot;</property></emphasis> + <emphasis ><property>&quot;manualInput&quot;</property></emphasis> attribute. When arrow controls are pressed, the cursor can be moved in any way without losing a dragged state.</para> <figure> Modified: trunk/docs/userguide/en/src/main/docbook/included/inputNumberSpinner.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/inputNumberSpinner.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/inputNumberSpinner.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -63,12 +63,12 @@ <para><emphasis role="bold"><property>&lt;rich:inputNumberSpinner&gt;</property></emphasis> is used to facilitate user data input with rich UI Controls.</para> <para>Here is the simplest variant of <property>spinner</property> definition with <emphasis -role="italic"><property>&quot;minValue&quot;</property>,</emphasis> <emphasis +><property>&quot;minValue&quot;</property>,</emphasis> <emphasis -role="italic"><property>&quot;maxValue&quot;</property></emphasis> +><property>&quot;maxValue&quot;</property></emphasis> and <emphasis -role="italic"><property>&quot;step&quot;</property></emphasis> (on default = &quot;1&quot;) attributes, which define the beginning and the end of numerical area +><property>&quot;step&quot;</property></emphasis> (on default = &quot;1&quot;) attributes, which define the beginning and the end of numerical area and a <property>spinner</property> step.</para> <para><emphasis role="bold">Example:</emphasis></para> <programlisting role="XML"><![CDATA[... @@ -87,13 +87,13 @@ <para>There are also several attributes to define functional peculiarities:</para> <itemizedlist> <listitem> - <emphasis role="italic"><property>&quot;cycled&quot;</property></emphasis> if the attribute is &quot;true&quot; after the current value reaches the border value it's be reversed to another border value after next increasing/decreasing. In other case possibilities of next increasing/decreasing are locked + <emphasis ><property>&quot;cycled&quot;</property></emphasis> if the attribute is &quot;true&quot; after the current value reaches the border value it's be reversed to another border value after next increasing/decreasing. In other case possibilities of next increasing/decreasing are locked </listitem> <listitem> - <emphasis role="italic"><property>&quot;disabled&quot;</property></emphasis> is an attribute that defines whether a component is active on a page + <emphasis ><property>&quot;disabled&quot;</property></emphasis> is an attribute that defines whether a component is active on a page </listitem> <listitem> - <emphasis role="italic"><property>&quot;manualInput&quot;</property></emphasis> is an attribute that defines whether a keyboard input is possible or only UI controls could be used</listitem> + <emphasis ><property>&quot;manualInput&quot;</property></emphasis> is an attribute that defines whether a keyboard input is possible or only UI controls could be used</listitem> </itemizedlist> <para>Moreover, to add e.g. some JavaScript effects, events defined on it are used</para> <itemizedlist> @@ -123,14 +123,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property></emphasis>.</para> +><property>style class redefinition method</property></emphasis>.</para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all inputNumberSpinners at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis -role="italic"><property>style classes</property></emphasis> used by the inputNumberSpinner to your page style sheets</listitem> +><property>style classes</property></emphasis> used by the inputNumberSpinner to your page style sheets</listitem> </itemizedlist> <table> <title>Skin parameters redefinition:</title> @@ -233,7 +233,7 @@ <para>To redefine appearance of the particular <property>spinner</property>, it&apos;s possible to define your own CSS class. Then it&apos;s necessary just to define it in one of the <emphasis -role="italic"><property>&quot;components class&quot;</property></emphasis> +><property>&quot;components class&quot;</property></emphasis> attributes modifying component style properties.</para> <para><emphasis role="bold">Example:</emphasis></para> <para>CSS code piece used on the page:</para> Modified: trunk/docs/userguide/en/src/main/docbook/included/modalPanel.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/modalPanel.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/modalPanel.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -183,27 +183,27 @@ </mediaobject> </figure> - <para>To manage the placement of inserted windows, use the <emphasis role="italic"> + <para>To manage the placement of inserted windows, use the <emphasis > <property>"zindex"</property> </emphasis> attribute that is similar to the standard HTML attribute and can specify window placement relative to the content.</para> - <para>To manage window placement relative to the component, there are <emphasis role="italic"> + <para>To manage window placement relative to the component, there are <emphasis > <property>"left"</property> - </emphasis> and <emphasis role="italic"> + </emphasis> and <emphasis > <property>"top"</property> </emphasis> attributes defining a window shifting relative to the top-left corner of the window.</para> <para>Modal windows can also support resize and move operations on the client side. To allow or - disallow these operations, set the <emphasis role="italic"> + disallow these operations, set the <emphasis > <property>"resizeable"</property> - </emphasis> and <emphasis role="italic"> + </emphasis> and <emphasis > <property>"moveable"</property> </emphasis> attributes to &quot;true&quot; or &quot;false&quot; values. Window - resizing is also limited by <emphasis role="italic"> + resizing is also limited by <emphasis > <property>"minWidth"</property> - </emphasis> and <emphasis role="italic"> + </emphasis> and <emphasis > <property>"minHeight"</property> </emphasis> attributes specifying the minimal window sizes.</para> <para> You can pass your parameters during modalPanel opening or closing. This passing could be @@ -225,9 +225,9 @@ <section> <title>Look-and-Feel Customization</title> - <para>For implementing skinnability the components use a <emphasis role="italic"> + <para>For implementing skinnability the components use a <emphasis > <property>style class redefinition method</property> -</emphasis>. Default style classes are mapped on <emphasis role="italic"><property>skin +</emphasis>. Default style classes are mapped on <emphasis ><property>skin parameters</property>.</emphasis></para> <para>There are two ways to redefine the appearance of all modal panels at once:</para> @@ -235,7 +235,7 @@ <itemizedlist> <listitem>Redefine the corresponding skin parameters</listitem> - <listitem>Add <emphasis role="italic"> + <listitem>Add <emphasis > <property>style classes</property> </emphasis> used by modalPanel to your page style sheets</listitem> </itemizedlist> Modified: trunk/docs/userguide/en/src/main/docbook/included/paint2D.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/paint2D.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/paint2D.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -51,10 +51,10 @@ ]]></programlisting> <para>Here <emphasis -role="italic"><property>&quot;paint&quot;</property></emphasis> specifies the method performing +><property>&quot;paint&quot;</property></emphasis> specifies the method performing drawing and <emphasis -role="italic"><property>&quot;data&quot;</property></emphasis> specifies Managed Bean property keeping the data used by the method.</para> +><property>&quot;data&quot;</property></emphasis> specifies Managed Bean property keeping the data used by the method.</para> </section> <section> <title>Creating the Component Dynamically Using Java</title> @@ -69,11 +69,11 @@ <para>The example shows two main attributes of the component:</para> <itemizedlist> <listitem> - <para><emphasis role="italic"><property>&quot;paint&quot;</property></emphasis></para> + <para><emphasis ><property>&quot;paint&quot;</property></emphasis></para> <para>Specify a method receiving an object specified in data as a parameter and sending graphical information into the stream</para> </listitem> <listitem> - <para><emphasis role="italic"><property>&quot;data&quot;</property></emphasis></para> + <para><emphasis ><property>&quot;data&quot;</property></emphasis></para> <para>Specifies a bean class keeping user&apos;s data for rendering</para> </listitem> </itemizedlist> @@ -82,18 +82,18 @@ <title>Note:</title>data object should implement serializable interface </note> </para> - <para>The <emphasis role="italic"><property>&quot;format&quot;</property></emphasis> attribute of + <para>The <emphasis ><property>&quot;format&quot;</property></emphasis> attribute of the component defines a format of visual data passing to the server.</para> <para>Generated data can be used as a cacheable or non-cacheable resource. It&apos;s defined with <emphasis -role="italic"><property>&quot;cacheable&quot;</property></emphasis> attribute. +><property>&quot;cacheable&quot;</property></emphasis> attribute. If cache support is turned on, a key is created in URI with a mix of size (width/height), <emphasis -role="italic"><property>&quot;paint&quot;</property></emphasis> method, <emphasis +><property>&quot;paint&quot;</property></emphasis> method, <emphasis -role="italic"><property>&quot;format&quot;</property></emphasis> and <emphasis +><property>&quot;format&quot;</property></emphasis> and <emphasis -role="italic"><property>&quot;data&quot;</property></emphasis> attributes.</para> +><property>&quot;data&quot;</property></emphasis> attributes.</para> <para>Example:</para> <programlisting role="JAVA"><![CDATA[paintBean.java: @@ -129,13 +129,13 @@ <section> <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 + <emphasis ><property>style classes</property>, </emphasis> as it consists of one element generated with a user&apos;s method on the server.</para> <para>To define some style properties such as an indent or a border, it&apos;s possible to use <emphasis -role="italic"><property>&quot;style&quot;</property></emphasis> - and <emphasis role="italic"><property>&quot;styleClass&quot;</property></emphasis> attributes +><property>&quot;style&quot;</property></emphasis> + and <emphasis ><property>&quot;styleClass&quot;</property></emphasis> attributes on the component.</para> </section> </section> \ No newline at end of file Modified: trunk/docs/userguide/en/src/main/docbook/included/panel.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/panel.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/panel.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -147,14 +147,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property>.</emphasis></para> +><property>style class redefinition method</property>.</emphasis></para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all panels at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis -role="italic"><property>style classes</property></emphasis> used by the panel to your page style sheets</listitem> +><property>style classes</property></emphasis> used by the panel to your page style sheets</listitem> </itemizedlist> </section> <section> Modified: trunk/docs/userguide/en/src/main/docbook/included/panelBar.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/panelBar.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/panelBar.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -72,9 +72,9 @@ thus its customization deals only with specification of sizes and styles for rendering.</para> <para><emphasis -role="italic"><property>&quot;width&quot;</property></emphasis> and <emphasis +><property>&quot;width&quot;</property></emphasis> and <emphasis -role="italic"><property>&quot;height&quot;</property></emphasis> (both are 100% on default) attributes stand apart.</para> +><property>&quot;height&quot;</property></emphasis> (both are 100% on default) attributes stand apart.</para> <para>Style attributes are described further.</para> <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> <para> @@ -84,14 +84,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property>.</emphasis></para> +><property>style class redefinition method</property>.</emphasis></para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all panelBars at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis -role="italic"><property>style classes</property></emphasis> used by the panelBar to your page style sheets (<property>PanelBar</property> +><property>style classes</property></emphasis> used by the panelBar to your page style sheets (<property>PanelBar</property> itself has no properties mapped on a skin, it&apos;s described for its children).</listitem> </itemizedlist> </section> Modified: trunk/docs/userguide/en/src/main/docbook/included/panelBarItem.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/panelBarItem.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/panelBarItem.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -72,21 +72,21 @@ <para>The only attribute to describe here is <emphasis -role="italic"><property>&quot;label&quot;</property></emphasis> that specifies a text string in a component header.</para> +><property>&quot;label&quot;</property></emphasis> that specifies a text string in a component header.</para> <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 -role="italic"><property>style class redefinition method</property></emphasis>.</para> +><property>style class redefinition method</property></emphasis>.</para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all panelBarItem at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis -role="italic"><property>style classes</property></emphasis> used by the panelBarItem to your page style sheets</listitem> +><property>style classes</property></emphasis> used by the panelBarItem to your page style sheets</listitem> </itemizedlist> </section> <section> Modified: trunk/docs/userguide/en/src/main/docbook/included/panelMenu.desc.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/panelMenu.desc.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/panelMenu.desc.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -7,8 +7,8 @@ </sectioninfo> <section> <para>A collapsible vertical menu. The color scheme is based on skin parameters, but might differ - from a skin basing on the values of the <emphasis role="italic"><property>&quot;backgpoundType&quot;</property></emphasis> and - <emphasis role="italic"><property>&quot;backgroundTypeTopLevel&quot;</property></emphasis> attributes. + from a skin basing on the values of the <emphasis ><property>&quot;backgpoundType&quot;</property></emphasis> and + <emphasis ><property>&quot;backgroundTypeTopLevel&quot;</property></emphasis> attributes. The component can include two types of child components: panelMenuNode and PanelMenuItem.</para> <mediaobject> <imageobject> Modified: trunk/docs/userguide/en/src/main/docbook/included/separator.desc.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/separator.desc.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/separator.desc.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -8,7 +8,7 @@ <section> <title>Description</title> <para>A horizontal line to use as a <property>separator</property> in a layout. The line type - can be customized with the <emphasis role="italic"><property>&quot;lineType&quot;</property></emphasis> parameter.</para> + can be customized with the <emphasis ><property>&quot;lineType&quot;</property></emphasis> parameter.</para> <figure> <title>Separator component</title> <mediaobject> Modified: trunk/docs/userguide/en/src/main/docbook/included/separator.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/separator.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/separator.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -65,11 +65,11 @@ </emphasis> is a simple layout component which represents a <property>separator</property> stylized as a skin. Thus, the main attributes that define its style are <emphasis -role="italic"><property>&quot;style&quot;</property></emphasis> and <emphasis +><property>&quot;style&quot;</property></emphasis> and <emphasis - role="italic"><property>&quot;styleClass&quot;.</property></emphasis> In addition there are <emphasis role="italic"><property>width</property></emphasis> and <emphasis role="italic"><property>height</property></emphasis> attributes that should be specified in pixels.</para> -<para>The line type can be customized with the <emphasis role="italic"><property>&quot;lineType&quot;</property></emphasis> parameter. - For example, different line types are shown after rendering with the following initial settings <emphasis role="italic"><property>lineType=&quot;double&quot;</property></emphasis>and <emphasis role="italic"><property>&quot;lineType=&quot;solid&quot;.</property></emphasis> + ><property>&quot;styleClass&quot;.</property></emphasis> In addition there are <emphasis ><property>width</property></emphasis> and <emphasis ><property>height</property></emphasis> attributes that should be specified in pixels.</para> +<para>The line type can be customized with the <emphasis ><property>&quot;lineType&quot;</property></emphasis> parameter. + For example, different line types are shown after rendering with the following initial settings <emphasis ><property>lineType=&quot;double&quot;</property></emphasis>and <emphasis ><property>&quot;lineType=&quot;solid&quot;.</property></emphasis> </para> <figure> <title>Different line types of separator</title> @@ -108,6 +108,6 @@ <para>To define appearance of a particular <property>separators</property>, it&apos;s possible to write your own CSS classes and properties in the component style attributes - (<emphasis role="italic"><property>&quot;style&quot;</property>,</emphasis> <emphasis role="italic"><property>&quot;styleClass&quot;</property></emphasis>) modifying component property.</para> + (<emphasis ><property>&quot;style&quot;</property>,</emphasis> <emphasis ><property>&quot;styleClass&quot;</property></emphasis>) modifying component property.</para> </section> </chapter> \ No newline at end of file Modified: trunk/docs/userguide/en/src/main/docbook/included/simpleTogglePanel.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/simpleTogglePanel.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/simpleTogglePanel.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -69,7 +69,7 @@ <para>Switching mode could be defined with the <emphasis -role="italic"><property>&quot;switchType&quot;</property></emphasis> attribute with three possible parameters.</para> +><property>&quot;switchType&quot;</property></emphasis> attribute with three possible parameters.</para> <itemizedlist> <listitem> Server (DEFAULT)<para>The common submission is performed around <property>simpleTogglePanel</property> and a page is completely rendered on a called panel. Only one at a time panel is uploaded onto the client side.</para> @@ -77,7 +77,7 @@ <listitem> Ajax<para>AJAX form submission is performed around the panel, content of the called panel is uploaded on AJAX request and additionally specified elements in the <emphasis -role="italic"><property>&quot;reRender&quot;</property></emphasis> attribute are rendered. Only one at a time panel is uploaded on the client side.</para> +><property>&quot;reRender&quot;</property></emphasis> attribute are rendered. Only one at a time panel is uploaded on the client side.</para> </listitem> <listitem> Client<para> @@ -87,7 +87,7 @@ </itemizedlist> <para>The component could also have an <emphasis -role="italic"><property>&quot;expanded&quot;</property></emphasis> (true/false) attribute responsible for keeping a panel state. It gives an opportunity to manage a <property>simpleTogglePanel</property> state from a model.</para> +><property>&quot;expanded&quot;</property></emphasis> (true/false) attribute responsible for keeping a panel state. It gives an opportunity to manage a <property>simpleTogglePanel</property> state from a model.</para> <itemizedlist> <listitem> onmouseover @@ -117,14 +117,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property></emphasis>.</para> +><property>style class redefinition method</property></emphasis>.</para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all simpleTogglePanels at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis -role="italic"><property>style classes</property></emphasis> used by the simpleTogglePanel to your page style sheets</listitem> +><property>style classes</property></emphasis> used by the simpleTogglePanel to your page style sheets</listitem> </itemizedlist> </section> <section> Modified: trunk/docs/userguide/en/src/main/docbook/included/spacer.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/spacer.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/spacer.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -62,8 +62,8 @@ <para><emphasis role="bold"> <property>&lt;rich:spacer&gt;</property> </emphasis> is a simple layout component which represents a transparent <property>spacer</property>. Thus, the main -attributes that define its style are <emphasis role="italic"><property>style</property></emphasis> and <emphasis role="italic"><property>styleClass</property>.</emphasis></para> -<para>In addition, the attributes are responsible for the component size: <emphasis role="italic"><property>&quot;width&quot;</property></emphasis> and <emphasis role="italic"><property>&quot;height&quot;</property>.</emphasis></para> +attributes that define its style are <emphasis ><property>style</property></emphasis> and <emphasis ><property>styleClass</property>.</emphasis></para> +<para>In addition, the attributes are responsible for the component size: <emphasis ><property>&quot;width&quot;</property></emphasis> and <emphasis ><property>&quot;height&quot;</property>.</emphasis></para> <para>Moreover, to add e.g. some JavaScript effects, events defined on it are used.</para> <itemizedlist> <listitem> @@ -86,11 +86,11 @@ <section> <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 + <emphasis ><property>styleClass</property></emphasis> of a generated component, i.e. in order to redefine appearance of all <property>spacers</property> at once, it&apos;s necessary to redefine this class in your own CSS (replacing in the result properties defined in a skin with your own).</para> <para>To define appearance of the particular <property>spacer</property>, it&apos;s possible to write your own CSS classes - and properties in the component style attributes (<emphasis role="italic"><property>style</property>, </emphasis> <emphasis role="italic"><property>styleClass</property></emphasis>) modifying component property.</para> + and properties in the component style attributes (<emphasis ><property>style</property>, </emphasis> <emphasis ><property>styleClass</property></emphasis>) modifying component property.</para> </section> </section> \ No newline at end of file Modified: trunk/docs/userguide/en/src/main/docbook/included/subTable.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/subTable.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/subTable.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -75,7 +75,7 @@ <para>Skins support is described in the <link linkend="ArchitectureOverview">corresponding section</link>. AJAX support is possible because the component is created basing on the <emphasis role="bold"><property>&lt;a4j:repeat&gt;</property></emphasis> component and as a result the component has its possibilities of AJAX updates for a limited set of rows. The component is implemented - with the <emphasis role="italic"><property>&quot;ajaxKeys&quot;</property></emphasis> attribute for a table and in contrast to the <emphasis role="bold"><property>&lt;a4j:repeat&gt;</property></emphasis> outputs the standard HTML + with the <emphasis ><property>&quot;ajaxKeys&quot;</property></emphasis> attribute for a table and in contrast to the <emphasis role="bold"><property>&lt;a4j:repeat&gt;</property></emphasis> outputs the standard HTML structure for table rendering.</para> <programlisting role="XML"><![CDATA[... <rich:dataTable value="#{capitalsBean.capitals}" var="capitals" id="table"> @@ -96,14 +96,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property></emphasis>.</para> +><property>style class redefinition method</property></emphasis>.</para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all subTables at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis -role="italic"><property>style classes</property></emphasis> used by the subTable to your page style sheets</listitem> +><property>style classes</property></emphasis> used by the subTable to your page style sheets</listitem> </itemizedlist> <para>To redefine a style of a particular page, use component class attributes which list is the same as the <property>subTable</property> one and is known to you.</para> </section> Modified: trunk/docs/userguide/en/src/main/docbook/included/suggestionBox.desc.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/suggestionBox.desc.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/suggestionBox.desc.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -34,9 +34,9 @@ <listitem>Setting rules that appear between cells within a table of popup values</listitem> <listitem><emphasis -role="italic"><property>&quot;Event queue&quot;</property></emphasis> and <emphasis +><property>&quot;Event queue&quot;</property></emphasis> and <emphasis -role="italic"><property>&quot;request delay&quot;</property></emphasis> attributes present to divide +><property>&quot;request delay&quot;</property></emphasis> attributes present to divide frequently requests</listitem> <listitem>Managing area of components submitted on AJAX request</listitem> <listitem>Flexible list of components to update after AJAX request managed by attributes</listitem> Modified: trunk/docs/userguide/en/src/main/docbook/included/suggestionBox.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/suggestionBox.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/suggestionBox.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -55,7 +55,7 @@ </rich:suggestionbox> ... ]]></programlisting> -<para>Here is the <emphasis role="italic"><property>bean.autocomplete</property></emphasis> +<para>Here is the <emphasis ><property>bean.autocomplete</property></emphasis> method that returns the collection to pop up:</para> <programlisting role="JAVA"><![CDATA[public List autocomplete(Object event) { String pref = event.toString(); @@ -79,25 +79,25 @@ <itemizedlist> <listitem> <emphasis -role="italic"><property>&quot;for&quot;</property></emphasis><para>The attribute where there is an input component which activation causes a suggestion activation</para> +><property>&quot;for&quot;</property></emphasis><para>The attribute where there is an input component which activation causes a suggestion activation</para> </listitem> <listitem> <emphasis -role="italic"><property>&quot;suggestionAction&quot;</property></emphasis><para> is an accepting parameter of a SuggestionEvent type that returns as a result a collection for rendering in a tool tip window.</para> +><property>&quot;suggestionAction&quot;</property></emphasis><para> is an accepting parameter of a SuggestionEvent type that returns as a result a collection for rendering in a tool tip window.</para> </listitem> <listitem> <emphasis -role="italic"><property>&quot;var&quot;</property></emphasis> <para> +><property>&quot;var&quot;</property></emphasis> <para> a collection name that provides access for inputting into a table in a popup</para> </listitem> </itemizedlist> <para>There are also two size attributes (<emphasis -role="italic"><property>&quot;width&quot;</property></emphasis> and <emphasis +><property>&quot;width&quot;</property></emphasis> and <emphasis -role="italic"><property>&quot;height&quot;</property></emphasis>) that are obligatory for the suggestion component. The attributes have initial Defaults but should be specified manually in order to be changed.</para> +><property>&quot;height&quot;</property></emphasis>) that are obligatory for the suggestion component. The attributes have initial Defaults but should be specified manually in order to be changed.</para> <para>The <property>suggestionBox</property> component, as it is shown on the screenshot, could get any collection for an output and outputs it in a tooltip window the same as a custom dataTable (in several columns)</para> <programlisting role="XML"><![CDATA[... <rich:suggestionbox for="test" @@ -123,7 +123,7 @@ <para>When some string is chosen input receives the corresponding value from the second column containing <property>#{cit.text}</property></para> <para>There is also one more important attribute named <emphasis -role="italic"><property>&quot;tokens&quot;</property></emphasis> that specifies separators after which a set of some characters sequence is defined as a new prefix beginning from this separator and not from the string beginning.</para> +><property>&quot;tokens&quot;</property></emphasis> that specifies separators after which a set of some characters sequence is defined as a new prefix beginning from this separator and not from the string beginning.</para> <para><emphasis role="bold">Example:</emphasis></para> <programlisting role="XML"><![CDATA[... <rich:suggestiobox for="test" suggestionAction="#{bean.autocomplete}" var="cit" @@ -146,13 +146,13 @@ </figure> <para>For a multiple definition use either &quot;,.; &quot; syntax as a value for tokens or link a parameter to some bean property transmitting separators collection.</para> <para>The component also encompasses <emphasis -role="italic"><property>&quot;layout&quot;</property></emphasis> and <emphasis -role="italic"><property>&quot;style&quot;</property></emphasis> attributes corresponding to dataTable +><property>&quot;layout&quot;</property></emphasis> and <emphasis +><property>&quot;style&quot;</property></emphasis> attributes corresponding to dataTable ones for a table appearing in popup (for additional information, read JSF Reference) and custom attribute managing AJAX requests sending (for additional information, see <ulink url="http://www.jboss.org/projects/jbossajax4jsf">Ajax4JSF Project</ulink>).</para> <para>In addition to these attributes common for AJAX action components and limiting requests quantity and frequency, <property>suggestionBox</property> has one more its own attribute limiting - requests (the <emphasis role="italic"><property>&quot;minChars&quot;</property></emphasis> attribute). The attribute defines characters quantity inputted into a field after which AJAX requests are called to perform suggestion.</para> + requests (the <emphasis ><property>&quot;minChars&quot;</property></emphasis> attribute). The attribute defines characters quantity inputted into a field after which AJAX requests are called to perform suggestion.</para> <para> <ulink url="http://livedemo.exadel.com/richfaces-demo/richfaces/suggestionB... you can see the example of <emphasis role="bold">&lt;rich:suggestionBox&gt;</emphasis> usage and sources for the given example. </para> Modified: trunk/docs/userguide/en/src/main/docbook/included/tab.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/tab.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/tab.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -65,7 +65,7 @@ <section> <title>Details of Usage</title> <para>The main component function is to define a content group that is rendered and processed when the <property>tab</property> is active, i.e. click on a <property>tab</property> causes switching onto a <property>tab</property> containing content corresponded to this <property>tab</property>.</para> -<para>A marker on a <property>tab</property> header defined with the <emphasis role="italic"><property>&quot;label&quot;</property></emphasis> attribute. Moreover, each <property>tab</property> could be disabled (switching on this <property>tab</property> is impossible) with the <emphasis role="italic"><property>&quot;disable&quot;</property></emphasis> attribute.</para> +<para>A marker on a <property>tab</property> header defined with the <emphasis ><property>&quot;label&quot;</property></emphasis> attribute. Moreover, each <property>tab</property> could be disabled (switching on this <property>tab</property> is impossible) with the <emphasis ><property>&quot;disable&quot;</property></emphasis> attribute.</para> <programlisting role="XML"><![CDATA[... <rich:tabPanel width="20%"> <rich:tab label="Tab"> @@ -94,7 +94,7 @@ performed right on the client with the corresponding JavaScript and onto another <property>tab</property> with an AJAX request on the server. <property>Tab</property> switching modes are the same as <property>tabPanel</property> ones.</para> -<para>Each <property>tab</property> also has an attribute name (alias for <emphasis role="italic"><property>&quot;id&quot;</property></emphasis> attribute). Using this attribute value it&apos;s possible e.g. to set an active <property>tab</property> on a model level specifying this name in the corresponding attribute of the whole <property>tab</property>.</para> +<para>Each <property>tab</property> also has an attribute name (alias for <emphasis ><property>&quot;id&quot;</property></emphasis> attribute). Using this attribute value it&apos;s possible e.g. to set an active <property>tab</property> on a model level specifying this name in the corresponding attribute of the whole <property>tab</property>.</para> <para>Except the specific component attributes it has all necessary attributes for JavaScript event definition.</para> <itemizedlist> <listitem> @@ -127,10 +127,10 @@ <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use <emphasis -role="italic"><property>style class redefinition method</property>.</emphasis> +><property>style class redefinition method</property>.</emphasis> Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <note><title>Note:</title> A panel appearance and content is defined with a <property>tab</property> panel i.e. on the <property>tab</property> level it&apos;s possible to define only an appearance of this <property>tab</property> header. </note> @@ -138,7 +138,7 @@ <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis -role="italic"><property>style classes</property></emphasis> used by the tab to your page style sheets</listitem> +><property>style classes</property></emphasis> used by the tab to your page style sheets</listitem> </itemizedlist> </section> Modified: trunk/docs/userguide/en/src/main/docbook/included/tabPanel.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/tabPanel.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/tabPanel.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -73,7 +73,7 @@ submitted inside. If a form is placed into each tab, the Action elements of Tab controls appear to be out of the form and content submission inside the panels could be performed only for Action components inside tabs.</note> <para>Switching mode could be chosen with the <property>tabPanel</property> attribute <emphasis -role="italic"><property>&quot;mode&quot;</property></emphasis> with three possible parameters.</para> +><property>&quot;mode&quot;</property></emphasis> with three possible parameters.</para> <itemizedlist> <listitem> Server (DEFAULT)<para>The common submission is performed around <property>tabPanel</property> and a page is completely rendered on a called panel. Only one at a time <property>tabPanel</property> is uploaded onto the client side.</para> @@ -82,7 +82,7 @@ Ajax<para>AJAX form submission is performed around the <property>tabPanel</property>, content of the called <property>tabPanel</property> is uploaded on AJAX request and additionally specified elements in the <emphasis -role="italic"><property>&quot;reRender&quot;</property></emphasis> attribute are rendered. Only one at +><property>&quot;reRender&quot;</property></emphasis> attribute are rendered. Only one at a time <property>tabPanel</property> is uploaded on the client.</para> </listitem> <listitem> @@ -92,12 +92,12 @@ </itemizedlist> <para>As a result, the <property>tabPanel</property> is switched to the second tab according to the action returning outcome for moving onto another page and switching from the second to the first tab is performed.</para> <para>There is also the <emphasis -role="italic"><property>&quot;selectedTab&quot;</property></emphasis> attribute. The attribute keeps +><property>&quot;selectedTab&quot;</property></emphasis> attribute. The attribute keeps an active tab name; therefore, an active <property>tabPanel</property> could be changed with setting a name of the necessary tab to this attribute.</para> <para>There is also the <emphasis -role="italic"><property>&quot;headerAlignment&quot;</property></emphasis> attribute responsible for +><property>&quot;headerAlignment&quot;</property></emphasis> attribute responsible for rendering of <property>tabPanel</property> components. The attribute has several values: left (Default), right, center, which specify Tabs components location on the top of the tabPanel.</para> @@ -144,14 +144,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property></emphasis>.</para> +><property>style class redefinition method</property></emphasis>.</para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all tabPanels at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis -role="italic"><property>style classes</property></emphasis> used by the tabPanel to your page style sheets</listitem> +><property>style classes</property></emphasis> used by the tabPanel to your page style sheets</listitem> </itemizedlist> </section> Modified: trunk/docs/userguide/en/src/main/docbook/included/toggleControl.desc.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/toggleControl.desc.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/toggleControl.desc.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -9,11 +9,11 @@ <title>Description</title> <para>A link type <property>control</property> for switching between <property>togglePanel</property> facets. Target - Panel is specified with <emphasis role="italic"><property>&quot;for&quot;</property></emphasis> + Panel is specified with <emphasis ><property>&quot;for&quot;</property></emphasis> attribute. It can be located inside or outside the <property>togglePanel</property>. As the result of switching between facets previous facet is hidden and another one (specified with - <emphasis role="italic"><property>&quot;switchToState&quot;</property></emphasis> or panel - <emphasis role="italic"><property>&quot;stateOrder&quot;</property></emphasis> attributes) is + <emphasis ><property>&quot;switchToState&quot;</property></emphasis> or panel + <emphasis ><property>&quot;stateOrder&quot;</property></emphasis> attributes) is shown.</para> <figure> <title>ToggleControl component</title> Modified: trunk/docs/userguide/en/src/main/docbook/included/toggleControl.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/toggleControl.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/toggleControl.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -68,13 +68,13 @@ <para>As it was mentioned above, the <property>control</property> could be in any place in layout and linked to a switching panel that is managed with <emphasis -role="italic"><property>&quot;for&quot;</property></emphasis> attribute (in the <emphasis +><property>&quot;for&quot;</property></emphasis> attribute (in the <emphasis -role="italic"><property>&quot;for&quot;</property></emphasis> attribute the full component &quot;id&quot; is specified according to naming +><property>&quot;for&quot;</property></emphasis> attribute the full component &quot;id&quot; is specified according to naming containers).</para> <para>The <property>togglePanel</property> could be also switched from the side of the control instead of being strictly defined in <emphasis -role="italic"><property>&quot;switchOrder&quot;</property></emphasis> attribute of <emphasis role="bold"><property>&lt;rich:togglePanel&gt;</property>.</emphasis></para> +><property>&quot;switchOrder&quot;</property></emphasis> attribute of <emphasis role="bold"><property>&lt;rich:togglePanel&gt;</property>.</emphasis></para> <para><emphasis role="bold">Example:</emphasis></para> <programlisting role="XML"><![CDATA[... <rich:togglePanel id="panel" initialState="empty" switchType="client"> @@ -102,17 +102,17 @@ ... ]]></programlisting> <para>In this example the switching is performed on facets specified in the <emphasis -role="italic"><property>&quot;switchToState&quot;</property></emphasis> attribute.</para> +><property>&quot;switchToState&quot;</property></emphasis> attribute.</para> </section> <section> <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 + class <emphasis ><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 page, redefine this class in your CSS.</para> <para>To define a particular <property>toggle controls</property> appearance, write down your own CSS properties and classes in component style attributes (<emphasis -role="italic"><property>&quot;style&quot;</property>,</emphasis> <emphasis -role="italic"><property>&quot;styleClass&quot;</property></emphasis>)and the properties have been changed.</para> +><property>&quot;style&quot;</property>,</emphasis> <emphasis +><property>&quot;styleClass&quot;</property></emphasis>)and the properties have been changed.</para> </section> </section> \ No newline at end of file Modified: trunk/docs/userguide/en/src/main/docbook/included/togglePanel.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/togglePanel.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/togglePanel.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -75,13 +75,13 @@ (either switched on the client or send requests on the server for switching).</para> <para>The initial component state is defined with <emphasis -role="italic"><property>&quot;initialState&quot;</property></emphasis> attribute, where a facet name that is shown at first is defined.</para> +><property>&quot;initialState&quot;</property></emphasis> attribute, where a facet name that is shown at first is defined.</para> <note><title>Note:</title> It&apos;s also possible to define an <property>&quot;empty&quot;</property> facet to implement the functionality as drop-down panels have and make the facet active when no content is required to be rendered.</note> <para>Switching mode could be defined with the <emphasis -role="italic"><property>&quot;switchType&quot;</property></emphasis> attribute with three possible +><property>&quot;switchType&quot;</property></emphasis> attribute with three possible parameters:</para> <itemizedlist> <listitem> @@ -91,7 +91,7 @@ Ajax<para>AJAX form submission is performed around the panel, content of the called panel is uploaded on an AJAX request and additionally specified elements in the <emphasis -role="italic"><property>&quot;reRender&quot;</property></emphasis> attribute are rendered. Only one at a time panel is uploaded on the client side.</para> +><property>&quot;reRender&quot;</property></emphasis> attribute are rendered. Only one at a time panel is uploaded on the client side.</para> </listitem> <listitem> Client<para> @@ -101,7 +101,7 @@ </itemizedlist> <para>&quot;Facets&quot; switching order could be defined on the side of <emphasis role="bold"><property>&lt;rich:toggleControl&gt;</property></emphasis> component or on the panel. On the side of the togglePanel it&apos;s possible to define facets switching order with the <emphasis -role="italic"><property>&quot;stateOrder&quot;</property></emphasis> attribute. The facets names are enumerated in +><property>&quot;stateOrder&quot;</property></emphasis> attribute. The facets names are enumerated in such an order that they are rendered when a control is clicked, as it&apos;s not defined where to switch beforehand.</para> <programlisting role="XML"><![CDATA[... Modified: trunk/docs/userguide/en/src/main/docbook/included/toolBar.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/toolBar.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/toolBar.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -69,7 +69,7 @@ functionality.</para> <para>Separators are located between components with the help of the <emphasis -role="italic"><property>&quot;itemSeparator&quot;</property></emphasis> attribute +><property>&quot;itemSeparator&quot;</property></emphasis> attribute with four predefined values:</para> <itemizedlist> <listitem> @@ -96,7 +96,7 @@ </mediaobject> </figure> <para>Moreover, for <property>toolBar</property> style - <emphasis role="italic"><property>&quot;width&quot;</property></emphasis> and <emphasis role="italic"><property>&quot;height&quot;</property></emphasis> attributes + <emphasis ><property>&quot;width&quot;</property></emphasis> and <emphasis ><property>&quot;height&quot;</property></emphasis> attributes are placed above all.</para> <para> <ulink url="http://livedemo.exadel.com/richfaces-demo/richfaces/toolBar.jsf... you can see the example of <emphasis role="bold">&lt;rich:toolBar&gt;</emphasis> usage and sources for the given example. @@ -105,14 +105,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property></emphasis>.</para> +><property>style class redefinition method</property></emphasis>.</para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all toolBars at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis -role="italic"><property>style classes</property></emphasis> used by the toolBar to your page style sheets</listitem> +><property>style classes</property></emphasis> used by the toolBar to your page style sheets</listitem> </itemizedlist> <table> <title>Skin parameters redefinition</title> @@ -139,11 +139,11 @@ <section> <title>Definition custom style classes</title> <para>On generating, the component substitutes the default class rich-toolbar-exterior - into <emphasis role="italic"><property>style class</property></emphasis> + into <emphasis ><property>style class</property></emphasis> of a generated component, i.e. to redefine at once all <property>toolBars</property> appearance on a page, redefine this class in your CSS.</para> - <para>The component also has the standard attributes <emphasis role="italic"><property>&quot;style&quot;</property></emphasis> and - <emphasis role="italic"><property>&quot;styleClass&quot;</property></emphasis> that could redefine an + <para>The component also has the standard attributes <emphasis ><property>&quot;style&quot;</property></emphasis> and + <emphasis ><property>&quot;styleClass&quot;</property></emphasis> that could redefine an appearance of a particular component variants.</para> </section> </section> \ No newline at end of file Modified: trunk/docs/userguide/en/src/main/docbook/included/toolBarGroup.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/toolBarGroup.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/toolBarGroup.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -72,7 +72,7 @@ <para>A <property>toolBarGroup</property> is a wrapper component that groups <property>toolBar</property> content and facilitates creation of menu and tool bars. All components defined inside are located on a stylized bar with a possibility to group, arrange on the both bar sides, and place predefined separators between them.</para> <para>Separators are located between components with the help of the <emphasis -role="italic"><property>&quot;itemSeparator&quot;</property></emphasis> attribute with four +><property>&quot;itemSeparator&quot;</property></emphasis> attribute with four predefined values:</para> <itemizedlist> <listitem> @@ -90,7 +90,7 @@ </itemizedlist> <para>To control the group location inside, use the <emphasis -role="italic"><property>&quot;location&quot;</property></emphasis> attribute with left (DEFAULT) and right values.</para> +><property>&quot;location&quot;</property></emphasis> attribute with left (DEFAULT) and right values.</para> <para><emphasis role="bold">Example:</emphasis></para> <programlisting role="XML"><![CDATA[... <rich:toolBar itemSeparator="disc" width="500"> @@ -118,14 +118,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property></emphasis>.</para> +><property>style class redefinition method</property></emphasis>.</para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all toolBarGroups at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis -role="italic"><property>style classes</property></emphasis> used by the toolBarGroup to your page style sheets</listitem> +><property>style classes</property></emphasis> used by the toolBarGroup to your page style sheets</listitem> </itemizedlist> <table> <title>Skin parameters redefinition</title> @@ -157,11 +157,11 @@ <title>Definition custom style classes</title> <para>On generating, the component substitutes the default class rich-toolbar-interior into <emphasis -role="italic"><property>style class</property></emphasis> of a generated component, i.e. +><property>style class</property></emphasis> of a generated component, i.e. to redefine at once all <property>toolBarGroups</property> appearance on a page, redefine this class in your CSS.</para> <para>The component also has the standard attribute style and <emphasis -role="italic"><property>style class</property></emphasis> that could redefine an +><property>style class</property></emphasis> that could redefine an appearance of particular component variants. </para> <para>It&apos;s necessary to define a class according to the corresponding name, so as an Modified: trunk/docs/userguide/en/src/main/docbook/included/tree.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/tree.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/tree.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -68,12 +68,12 @@ structure of a org.richfaces.component.TreeNode type. (You could have a look at this interface description in the API document) The default classes for lists building of a TreeNodeImpl type (it implements a TreeNode interface) for an XML structure XmlNodeData and XmlTreeDataBuilder are implemented in the tree component. Hence, in order to provide your own class for TreeNode, it&apos;s - necessary only to implement this interface, i.e. the <emphasis role="italic"><property>&quot;var&quot;</property></emphasis> attribute contains + necessary only to implement this interface, i.e. the <emphasis ><property>&quot;var&quot;</property></emphasis> attribute contains a name providing an access to data defined with value. </para> <para>For data output, named <property>tree</property> nodes elements are used. Each element, for example depending on its definition, could be rendered with markup defined in one of <property>tree</property> nodes. It&apos;s defined with the - <emphasis role="italic"><property>&quot;nodeFace&quot;</property></emphasis> + <emphasis ><property>&quot;nodeFace&quot;</property></emphasis> attribute that contains treeNode name for elements rendering. </para> <para>On the screenshot there are examples of nodes defined with different templates on the following conditions</para> @@ -89,7 +89,7 @@ </mediaobject> </figure> <para>Switching on nodes opening/closing (expanded/collapsed) could be implemented in three modes. It could be specified - in the <emphasis role="italic"><property>&quot;switchType&quot;</property></emphasis> attribute. </para> + in the <emphasis ><property>&quot;switchType&quot;</property></emphasis> attribute. </para> <itemizedlist> <listitem>AJAX - request onto the server is used for switching </listitem> <listitem>Server - custom requests onto the server are used for switching</listitem> @@ -97,21 +97,21 @@ client script</listitem> </itemizedlist> <para>Common selecting allows also to activate AJAX requests with the - <emphasis role="italic"><property>&quot;ajaxSubmitSelection&quot;</property></emphasis> + <emphasis ><property>&quot;ajaxSubmitSelection&quot;</property></emphasis> attribute (true/false).</para> <para>To set a model saving during requests, use the - <emphasis role="italic"><property>&quot;preserveModel&quot;</property></emphasis>attribute with + <emphasis ><property>&quot;preserveModel&quot;</property></emphasis>attribute with state, request (default) and none values. The attribute is used for cashing data between requests in a state or request. The - <emphasis role="italic"><property>&quot;treeDataLocator&quot;</property></emphasis> attribute + <emphasis ><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>, - <emphasis role="italic"><property>&quot;iconLeaf&quot;</property></emphasis> + The <emphasis ><property>&quot;icon&quot;</property></emphasis>, + <emphasis ><property>&quot;iconCollapsed&quot;</property></emphasis>, + <emphasis ><property>&quot;iconExpanded&quot;</property></emphasis>, + <emphasis ><property>&quot;iconLeaf&quot;</property></emphasis> attributes define icons for the component. Also you can define icons using facets with the same names. If the facets are defined, the corresponding attributes are ignored and facets contents are used as icons. The width of a rendered facet area is 16px. <programlisting role="JAVA"><![CDATA[... @@ -220,14 +220,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property></emphasis>.</para> +><property>style class redefinition method</property></emphasis>.</para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine an appearance of all trees at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis -role="italic"><property>style classes</property></emphasis> used by the tree to your page style sheets</listitem> +><property>style classes</property></emphasis> used by the tree to your page style sheets</listitem> </itemizedlist> </section> <section> Modified: trunk/docs/userguide/en/src/main/docbook/included/treeNode.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/treeNode.xml 2007-07-04 13:06:38 UTC (rev 1462) +++ trunk/docs/userguide/en/src/main/docbook/included/treeNode.xml 2007-07-04 13:13:57 UTC (rev 1463) @@ -65,10 +65,10 @@ <section> <title>Details of Usage</title> <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>, - <emphasis role="italic"><property>&quot;iconLeaf&quot;</property></emphasis> + The <emphasis ><property>&quot;icon&quot;</property></emphasis>, + <emphasis ><property>&quot;iconCollapsed&quot;</property></emphasis>, + <emphasis ><property>&quot;iconExpanded&quot;</property></emphasis>, + <emphasis ><property>&quot;iconLeaf&quot;</property></emphasis> attributes define icons for the component. Also you can define icons using facets with the same names. If the facets are defined, the corresponding attributes are ignored and facets contents are used as icons. The width of a rendered facet area is 16px. <programlisting role="JAVA"><![CDATA[... @@ -126,7 +126,7 @@ in <link linkend="tree">the corresponding section</link>.</para> <para>Default nodes of the tree level as well as ones defined with the <property>treeNodes</property> component could send AJAX requests when selected with the mouse, it&apos;s managed with the - <emphasis role="italic"><property>&quot;ajaxSubmitSelection&quot;</property></emphasis> attribute + <emphasis ><property>&quot;ajaxSubmitSelection&quot;</property></emphasis> attribute (true/false).</para> </section> <section> @@ -145,14 +145,14 @@ <section> <title>Look-and-Feel Customization</title> <para>For skinnability implementation the components use a <emphasis -role="italic"><property>style class redefinition method</property></emphasis>.</para> +><property>style class redefinition method</property></emphasis>.</para> <para>Default style classes are mapped on <emphasis -role="italic"><property>skin parameters</property>.</emphasis></para> +><property>skin parameters</property>.</emphasis></para> <para>To redefine appearance of all treeNodes at once, there are two ways:</para> <itemizedlist> <listitem>to redefine corresponding skin parameters</listitem> <listitem>to add <emphasis -role="italic"><property>style classes</property></emphasis> used by the treeNode to your page style sheets</listitem> +><property>style classes</property></emphasis> used by the treeNode to your page style sheets</listitem> </itemizedlist> </section> <section> @@ -240,8 +240,8 @@ declare and customize the above-mentioned classes in your CSS.</para> <para>It is also possible to change look and feel of specific <property>treeNodes</property> with the help of defining for them - <emphasis role="italic"><property>&quot;selectedClass&quot;</property></emphasis> - and <emphasis role="italic"><property>&quot;highlightedClass&quot;</property></emphasis> + <emphasis ><property>&quot;selectedClass&quot;</property></emphasis> + and <emphasis ><property>&quot;highlightedClass&quot;</property></emphasis> attributes by their specific classes.</para> </section> </section>