[richfaces-svn-commits] JBoss Rich Faces SVN: r9236 - trunk/docs/userguide/en/src/main/docbook/included.
richfaces-svn-commits at lists.jboss.org
richfaces-svn-commits at lists.jboss.org
Thu Jun 26 08:50:56 EDT 2008
Author: cluts
Date: 2008-06-26 08:50:56 -0400 (Thu, 26 Jun 2008)
New Revision: 9236
Modified:
trunk/docs/userguide/en/src/main/docbook/included/calendar.xml
trunk/docs/userguide/en/src/main/docbook/included/column.xml
trunk/docs/userguide/en/src/main/docbook/included/componentControl.xml
trunk/docs/userguide/en/src/main/docbook/included/contextMenu.desc.xml
trunk/docs/userguide/en/src/main/docbook/included/contextMenu.xml
trunk/docs/userguide/en/src/main/docbook/included/dataDefinitionList.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/dragIndicator.xml
trunk/docs/userguide/en/src/main/docbook/included/dragSupport.xml
trunk/docs/userguide/en/src/main/docbook/included/dropDownMenu.xml
trunk/docs/userguide/en/src/main/docbook/included/effect.xml
trunk/docs/userguide/en/src/main/docbook/included/fileUpload.xml
trunk/docs/userguide/en/src/main/docbook/included/menuGroup.xml
trunk/docs/userguide/en/src/main/docbook/included/portlet.xml
trunk/docs/userguide/en/src/main/docbook/included/push.desc.xml
trunk/docs/userguide/en/src/main/docbook/included/region.xml
trunk/docs/userguide/en/src/main/docbook/included/repeat.xml
trunk/docs/userguide/en/src/main/docbook/included/status.xml
trunk/docs/userguide/en/src/main/docbook/included/support.xml
Log:
RF-672 - corrected names attributes, tags, components and facets for portlet, push, region, repeat, status, support, calendar, componentControl, contextMenu, column, dataList, dataOrderedList, dataDefinitionList, dragIndicator, dragSupport, dropDownMenu, menuGroup, effect, fileUpload components
Modified: trunk/docs/userguide/en/src/main/docbook/included/calendar.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/calendar.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/calendar.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -107,7 +107,7 @@
defined with the <emphasis>
<property>"mode"</property>
</emphasis> attribute with two possible parameters: "<code>ajax</code>" and "<code>client</code>". Default value is
- "client".</para>
+ <code>"client"</code>.</para>
<itemizedlist>
<listitem>
<para><code>Ajax</code></para>
@@ -115,7 +115,7 @@
</itemizedlist>
<para>Calendar requests portions of data from Data Model for a page rendering. If <emphasis>
<property>"dataModel"</property>
- </emphasis> attribute has <property>"null"</property> value, data requests
+ </emphasis> attribute has "null" value, data requests
are not sent. In this case the "<code>ajax</code>" mode is equal to the
"<code>client</code>". </para>
<itemizedlist>
@@ -131,7 +131,7 @@
</emphasis> and <emphasis>
<property>"preloadDateRangeEnd"</property>
</emphasis> attributes was designed only for the
- <property>"client"</property> mode to load some data initially.</para></note>
+ "<code>client</code>" mode to load some data initially.</para></note>
<para><emphasis>
<property>"ondataselect"</property>
</emphasis> attribute is used to define an event that is triggered before date selection.</para>
@@ -159,13 +159,13 @@
<emphasis>
<property>"oncurrentdataselected"</property>
</emphasis> event is fired when the "next/previous month" or "next/previous year" button is pressed,
- and the value is <property>applied</property>.
+ and the value is applied.
</para>
<para>
<emphasis>
<property>"oncurrentdataselect"</property>
</emphasis> event is fired when the "next/previous month" or "next/previous year" button is pressed,
- but the value is <property>not applied</property> yet (you can change the logic of upplying the value). Also this event could be used for possibility of "next/previous month" or "next/previous year" selection canceling. See an example below:
+ but the value is not applied yet (you can change the logic of applying the value). Also this event could be used for possibility of "next/previous month" or "next/previous year" selection canceling. See an example below:
</para>
<para>
<emphasis role="bold">Example:</emphasis>
@@ -185,8 +185,8 @@
<listitem>
<para><emphasis>
<property>"buttonLabel"</property>
- </emphasis> defines a label for the button. If the attribute is set "buttonIcon" and
- "buttonIconDisabled" are ignored </para>
+ </emphasis> defines a label for the button. If the attribute is set <emphasis><property>"buttonIcon"</property></emphasis> and
+ <emphasis><property>"buttonIconDisabled"</property></emphasis> are ignored </para>
</listitem>
</itemizedlist>
<itemizedlist>
@@ -212,11 +212,11 @@
<property>"direction"</property>
</emphasis> are: </para>
<itemizedlist>
- <listitem><para>top-left - a calendar drops to the top and left</para></listitem>
- <listitem><para>top-right - a calendar drops to the top and right</para></listitem>
- <listitem><para>bottom-left - a calendar drops to the bottom and left</para></listitem>
- <listitem><para>bottom-right - a calendar drops to the bottom and right</para></listitem>
- <listitem><para>auto - smart positioning activation</para></listitem>
+ <listitem><para>"top-left" - a calendar drops to the top and left</para></listitem>
+ <listitem><para>"top-right" - a calendar drops to the top and right</para></listitem>
+ <listitem><para>"bottom-left" - a calendar drops to the bottom and left</para></listitem>
+ <listitem><para>"bottom-right" - a calendar drops to the bottom and right</para></listitem>
+ <listitem><para>"auto" - smart positioning activation</para></listitem>
</itemizedlist>
<para> By default, the <emphasis>
<property>"direction"</property>
@@ -225,11 +225,11 @@
<property>"jointPoint"</property>
</emphasis> are: </para>
<itemizedlist>
- <listitem><para>top-left - a calendar docked to the top-left point of the button element</para></listitem>
- <listitem><para>top-right - a calendar docked to the top-right point of the button element</para></listitem>
- <listitem><para>bottom-left - a calendar docked to the bottom-left point of the button element</para></listitem>
- <listitem><para>bottom-right - a calendar docked to the bottom-right point of the button element</para></listitem>
- <listitem><para>auto - smart positioning activation</para></listitem>
+ <listitem><para>"top-left" - a calendar docked to the top-left point of the button element</para></listitem>
+ <listitem><para>"top-right" - a calendar docked to the top-right point of the button element</para></listitem>
+ <listitem><para>"bottom-left" - a calendar docked to the bottom-left point of the button element</para></listitem>
+ <listitem><para>"bottom-right" - a calendar docked to the bottom-right point of the button element</para></listitem>
+ <listitem><para>"auto" - smart positioning activation</para></listitem>
</itemizedlist>
<para> By default, the <emphasis>
<property>"jointPoint"</property>
@@ -444,9 +444,8 @@
<para><code>CalendarDataModelItem</code> provides the following function:</para>
<itemizedlist>
<listitem><para>Date <code>getDate()</code> - returns date from the item. Default implementation returns date.</para></listitem>
- <listitem><para>Boolean <code>isEnabled()</code> - returns <emphasis>
- <property>"true"</property>
- </emphasis> if date is <emphasis>
+ <listitem><para>Boolean <code>isEnabled()</code> - returns "true"
+ if date is <emphasis>
<property>"selectable"</property>
</emphasis> on the calendar. Default implementation returns "true".</para></listitem>
<listitem><para>String <code>getStyleClass()</code> - returns string appended to the style class for the date
Modified: trunk/docs/userguide/en/src/main/docbook/included/column.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/column.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/column.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -378,7 +378,7 @@
If the <emphasis><property>"filterValue"</property></emphasis> attribute isn't empty from the beginning table is filtered on the first rendering.
</para>
<para>
- You can customize the input form using <property>rich-filter-input</property> CSS class.
+ You can customize the input form using "rich-filter-input" CSS class.
</para>
<para>
In order to change filter event you could use <emphasis><property>"filterEvent"</property></emphasis> attribute
Modified: trunk/docs/userguide/en/src/main/docbook/included/componentControl.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/componentControl.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/componentControl.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -95,7 +95,7 @@
<listitem><para>Define a name of a function that is generated (definition is similar to a
definition of <emphasis role="bold">
<property><a4j:jsFunction></property>
- </emphasis>). An "event" argument is passed to this function.</para></listitem>
+ </emphasis>). An "<code>event</code>" argument is passed to this function.</para></listitem>
</itemizedlist>
<para>An example is placed below:</para>
<programlisting role="XML"><![CDATA[...
@@ -145,7 +145,7 @@
<property><rich:componentControl></property>
</emphasis> allows to transfer parameters. The <emphasis>
<property>"disableDefault"</property>
- </emphasis> attribute with <property>"true"</property> value is used instead
+ </emphasis> attribute with "true" value is used instead
of <code>onclick="return false;"</code> attribute for <emphasis role="bold">
<property><h:commandButton></property>
</emphasis> to avoid a problem with form submit and <property>modalPanel</property> showing.</para>
Modified: trunk/docs/userguide/en/src/main/docbook/included/contextMenu.desc.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/contextMenu.desc.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/contextMenu.desc.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -10,7 +10,7 @@
<para>The <emphasis role="bold">
<property><rich:contextMenu></property>
</emphasis> component is used for creation multileveled
- context menus that are activated after a user defines an event (onmouseover, onclick,
+ context menus that are activated after a user defines an event (<emphasis><property>"onmouseover"</property></emphasis>, <emphasis><property>"onclick"</property></emphasis>,
etc.) on any element on the page.</para>
<figure>
<title><emphasis role="bold">
@@ -27,7 +27,7 @@
<title>Key Features</title>
<itemizedlist>
<listitem><para>Highly customizable look and feel</para></listitem>
- <listitem><para>"oncontextmenu" event support</para></listitem>
+ <listitem><para><emphasis><property>"oncontextmenu"</property></emphasis> event support</para></listitem>
<listitem><para>Disablement support</para></listitem>
<listitem><para>Pop-up appearance event customization</para></listitem>
<listitem><para>Usage of shared instance of a menu on a page</para></listitem>
Modified: trunk/docs/userguide/en/src/main/docbook/included/contextMenu.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/contextMenu.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/contextMenu.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -65,7 +65,7 @@
<emphasis role="bold">
<property><rich:contextMenu></property>
</emphasis> is a support-like component. Context menu itself is an invisible panel that
- appears after a particular client side event (onmouseover, onclick, etc) occured on a
+ appears after a particular client side event (<emphasis><property>"onmouseover"</property></emphasis>, <emphasis><property>"onclick"</property></emphasis>, etc.) occurred on a
parent component. The event is defined with an <emphasis>
<property>"event"</property>
</emphasis> attribute. The component uses <emphasis>
@@ -87,7 +87,7 @@
<para>If a value of the <emphasis>
<property>"attached"</property>
- </emphasis> attribute is defined as <property>"true"</property>,
+ </emphasis> attribute is defined as "true",
the component is attached to the parent component. An example is placed below.</para>
<para>
<emphasis role="bold">Example:</emphasis>
@@ -130,9 +130,9 @@
<property><h:panelGroup></property>
</emphasis> one and has a value of the<emphasis>
<property>"attached"</property>
- </emphasis> attribute defined as <property>"true"</property>. Thus,
+ </emphasis> attribute defined as "true". Thus,
the context menu is attached to the parent component. The context menu has two items to
- zoom in (zoom out) a picture by <property>"onclick"</property> event.
+ zoom in (zoom out) a picture by <emphasis><property>"onclick"</property></emphasis> event.
For earch item corresponding JavaScript function is defined to provide necessary action
as a result of the clicking on it. For the menu is defined an <emphasis>
<property>"oncontextmenu"</property>
@@ -142,7 +142,7 @@
<property><h:panelGroup></property>
</emphasis> component with a value of <emphasis>
<property>"id"</property>
- </emphasis> attribute equal to <property>"picture"</property>. You
+ </emphasis> attribute equal to "<code>picture</code>" You
should be careful with such definition, because a client context menu is looked for a
DOM element with a client Id of a parent component on a server. If a parent component
doesn't encode an Id on a client, it can't be found by the <emphasis
@@ -152,7 +152,7 @@
<para> If the <emphasis>
<property>"attached"</property>
- </emphasis> attribute has <property>"false"</property> value,
+ </emphasis> attribute has "false" value,
component activates via JavaScript API with assistance of <emphasis role="bold">
<property><rich:componentControl></property>
</emphasis>. An example is placed below.</para>
Modified: trunk/docs/userguide/en/src/main/docbook/included/dataDefinitionList.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/dataDefinitionList.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/dataDefinitionList.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -78,8 +78,8 @@
<property>"term"</property>
</emphasis> facet, which corresponds to the <emphasis>
<property>"type"</property>
- </emphasis> parameter for the <emphasis>
- <property>"DT"</property>
+ </emphasis> parameter for the <emphasis role="bold">
+ <property><DT></property>
</emphasis> HTML element.</para>
<para>Here is an example:</para>
Modified: trunk/docs/userguide/en/src/main/docbook/included/dataList.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/dataList.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/dataList.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -79,13 +79,13 @@
<property>"type"</property>
</emphasis> attribute, which corresponds to the <emphasis>
<property>"type"</property>
- </emphasis> parameter for the <emphasis>
- <property>"UL"</property>
+ </emphasis> parameter for the <emphasis role="bold">
+ <property><UL></property>
</emphasis> HTML element and defines a marker type. Possible values for <emphasis>
<property>"type"</property>
- </emphasis> attribute are: <property>"disc"</property>,
- <property>"circle"</property>,
- <property>"square"</property>.</para>
+ </emphasis> attribute are: "disc",
+ "circle",
+ "square".</para>
<para>Here is an example:</para>
<programlisting role="XML"><![CDATA[...
Modified: trunk/docs/userguide/en/src/main/docbook/included/dataOrderedList.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/dataOrderedList.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/dataOrderedList.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -95,24 +95,14 @@
<property>"type"</property>
</emphasis>
parameter for the
- <emphasis>
- <property>"OL"</property>
+ <emphasis role="bold">
+ <property><OL></property>
</emphasis>
HTML element and defines a marker type. Possible values for
<emphasis>
<property>"type"</property>
</emphasis>
- attribute are:
- <code>"A"</code>
- ,
- <code>"a"</code>
- ,
- <code>"I"</code>
- ,
- <code>"i"</code>
- ,
- <code>"1"</code>
- .
+ attribute are: "A", "a", "I", "i", "1".
</para>
<para>Here is an example:</para>
Modified: trunk/docs/userguide/en/src/main/docbook/included/dragIndicator.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/dragIndicator.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/dragIndicator.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -90,11 +90,11 @@
</figure>
<para>For indicator customization you need to define one of the following facets:</para>
<itemizedlist>
- <listitem><para><code>single</code></para></listitem>
+ <listitem><para><emphasis><property>"single"</property></emphasis></para></listitem>
</itemizedlist>
<para>Indicator shown when dragging a single element.</para>
<itemizedlist>
- <listitem><para><code>multiple</code></para></listitem>
+ <listitem><para><emphasis><property>"multiple"</property></emphasis></para></listitem>
</itemizedlist>
<para>Indicator shown when dragging several components (for future components that will support
multiple selection).</para>
Modified: trunk/docs/userguide/en/src/main/docbook/included/dragSupport.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/dragSupport.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/dragSupport.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -105,7 +105,7 @@
must be placed inside a wrapper component that outputs child
components and that has the right events defined on it.
Thus, this example won't work, because the
- <code>h:column</code>
+ <emphasis role="bold"><property><h:column></property></emphasis>
tag doesn't provide the necessary properties for redefining
events on the client:
</para>
@@ -128,7 +128,7 @@
However, using
<property>a4j:outputPanel</property>
as a wrapper inside
- <code>h:column</code>
+ <emphasis role="bold"><property><h:column></property></emphasis>
, the following code could be used successfully:
</para>
@@ -236,11 +236,11 @@
<itemizedlist>
<listitem>
- <para>ondragenter</para>
+ <para><emphasis><property>"ondragstart"</property></emphasis></para>
</listitem>
<listitem>
- <para>ondragexit</para>
+ <para><emphasis><property>"ondragend"</property></emphasis></para>
</listitem>
</itemizedlist>
Modified: trunk/docs/userguide/en/src/main/docbook/included/dropDownMenu.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/dropDownMenu.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/dropDownMenu.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -172,23 +172,23 @@
<itemizedlist>
<listitem>
- <para>top-left - a menu drops to the top and left</para>
+ <para>"top-left" - a menu drops to the top and left</para>
</listitem>
<listitem>
- <para>top-right - a menu drops to the top and right</para>
+ <para>"top-right" - a menu drops to the top and right</para>
</listitem>
<listitem>
- <para>bottom-left - a menu drops to the bottom and left</para>
+ <para>"bottom-left" - a menu drops to the bottom and left</para>
</listitem>
<listitem>
- <para>bottom-right - a menu drops to the bottom and right</para>
+ <para>"bottom-right" - a menu drops to the bottom and right</para>
</listitem>
<listitem>
- <para>auto - smart positioning activation</para>
+ <para>"auto" - smart positioning activation</para>
</listitem>
</itemizedlist>
@@ -198,23 +198,23 @@
<itemizedlist>
<listitem>
- <para>tr - a menu is attached to the top-right point of the button element</para>
+ <para>"tr" - a menu is attached to the top-right point of the button element</para>
</listitem>
<listitem>
- <para>tl - a menu is attached to the top-left point of the button element</para>
+ <para>"tl" - a menu is attached to the top-left point of the button element</para>
</listitem>
<listitem>
- <para>br - a menu is attached to the bottom-right point of the button element</para>
+ <para>"br" - a menu is attached to the bottom-right point of the button element</para>
</listitem>
<listitem>
- <para>bl - a menu is attached to the bottom-left point of the button element</para>
+ <para>"bl" - a menu is attached to the bottom-left point of the button element</para>
</listitem>
<listitem>
- <para>auto - smart positioning activation</para>
+ <para>"auto" - smart positioning activation</para>
</listitem>
</itemizedlist>
@@ -222,9 +222,7 @@
<property>"direction"</property>
</emphasis> and <emphasis>
<property>"jointPoint"</property>
- </emphasis> attributes are set to <emphasis>
- <property>"auto"</property>
- </emphasis>.</para>
+ </emphasis> attributes are set to "auto".</para>
<para>Here is an example:</para>
@@ -332,7 +330,7 @@
<para>
The <emphasis><property>"disabled"</property></emphasis> attribute is used for disabling whole
<emphasis role="bold"><property><rich:dropDownMenu></property></emphasis> component. In this case it is
- necessary to define <emphasis><property>"disabled"</property></emphasis> attribute as <property>"true"</property>.
+ necessary to define <emphasis><property>"disabled"</property></emphasis> attribute as "true".
An example is placed below.
</para>
Modified: trunk/docs/userguide/en/src/main/docbook/included/effect.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/effect.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/effect.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -161,7 +161,7 @@
<property>"params"</property>
</emphasis> attribute allows to define the set of options possible for particurar effect. For
example, 'duration', 'delay', 'from', 'to'. Additionally to the options used by the effect
- itself, there are two option that might override the <property>rich:effect</property>
+ itself, there are two option that might override the <emphasis role="bold"><property><rich:effect></property></emphasis>
attribute. Those are: <itemizedlist>
<listitem><para><emphasis>
<property>"targetId"</property>
Modified: trunk/docs/userguide/en/src/main/docbook/included/fileUpload.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/fileUpload.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/fileUpload.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -370,7 +370,7 @@
<emphasis role="bold"><property><rich:fileUpload></property></emphasis>
component also provides a number of JavaScript property,
that can be used to process uploaded files, file states etc.
- The given below example illustrates how the <property>entries[0].state</property> property can be used to get access to the file state.
+ The given below example illustrates how the <code>entries[0].state</code> property can be used to get access to the file state.
Full list of JavaScript properties can be found <link linkend="objectProperties">below</link> .
</para>
Modified: trunk/docs/userguide/en/src/main/docbook/included/menuGroup.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/menuGroup.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/menuGroup.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -116,30 +116,28 @@
<para>Possible values are:</para>
<itemizedlist>
<listitem>
- <para>left - down - a submenu is attached to the left side of the menu and is
+ <para>"left - down" - a submenu is attached to the left side of the menu and is
dropping down</para>
</listitem>
<listitem>
- <para>left - up - a submenu is attached to the left side of the menu and is dropping
+ <para>"left - up" - a submenu is attached to the left side of the menu and is dropping
up</para>
</listitem>
<listitem>
- <para>right - down - a submenu is attached to the right side of the menu and is
+ <para>"right - down" - a submenu is attached to the right side of the menu and is
dropping down</para>
</listitem>
<listitem>
- <para>right - up - a submenu is attached to the right side of the menu and is
+ <para>"right - up" - a submenu is attached to the right side of the menu and is
dropping up</para>
</listitem>
<listitem>
- <para>auto - smart positioning activation</para>
+ <para>"auto - smart" positioning activation</para>
</listitem>
</itemizedlist>
<para> By default, the <emphasis>
<property>"direction"</property>
- </emphasis> attribute is set to <emphasis>
- <property>"auto"</property>
- </emphasis>. </para>
+ </emphasis> attribute is set to "auto". </para>
<para> Here is an example: </para>
<programlisting role="XML"><![CDATA[...
<rich:menuGroup value="Save As..." direction="left-down">
Modified: trunk/docs/userguide/en/src/main/docbook/included/portlet.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/portlet.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/portlet.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -57,10 +57,10 @@
<para>
The main component purpose is realization of possibility to create several instances the same portlet on
one page. But clientId of elements
- should be different for each window. In that case <property>namespace</property> is used for
+ should be different for each window. In that case namespace is used for
each portlet. The <emphasis role="bold">
<property><a4j:portlet></property>
- </emphasis> implemets NaimingContainer interface and adds namespace to all componets on a
+ </emphasis> <code>implemets NaimingContainer</code> interface and adds namespace to all componets on a
page. All portlet content should be wrapped by <emphasis role="bold">
<property><a4j:portlet></property>
</emphasis> for resolving problems mentioned before. </para>
Modified: trunk/docs/userguide/en/src/main/docbook/included/push.desc.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/push.desc.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/push.desc.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -19,6 +19,6 @@
</emphasis>
makes request to minimal code only (not to JSF tree) in order to check the presence of messages in the queue.
If the message exists the complete request is performed. The component doesn't poll registered beans
- but registers EventListener which receives messages about events.</para>
+ but registers <code>EventListener</code> which receives messages about events.</para>
</section>
</root>
Modified: trunk/docs/userguide/en/src/main/docbook/included/region.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/region.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/region.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -91,7 +91,7 @@
<!--..Some content that will be decoded on server after Ajax request.-->
</a4j:region >]]></programlisting>
<para>Therefore, the external region is decoded for the <code>link1</code> and the internal one is decoded for the <code>link2</code>.</para>
- <para>RichFaces allows setting Ajax responses rendering directly basing on component tree nodes without referring to the JSP (XHTML) page code. It could be defined by<emphasis><property> "selfRendered" </property></emphasis>attribute setting to <property>"true"</property> on <emphasis role="bold">
+ <para>RichFaces allows setting Ajax responses rendering directly basing on component tree nodes without referring to the JSP (XHTML) page code. It could be defined by<emphasis><property> "selfRendered" </property></emphasis>attribute setting to "true" on <emphasis role="bold">
<property><a4j:region></property>
</emphasis> and could help considerably speed up a response output. However, this rapid processing could cause missing of transient components that present on view and don't come into a component tree as well as omitting of <emphasis role="bold">
<property><a4j:outputPanel></property>
@@ -106,7 +106,7 @@
<para>The processing could be also accelerated if a region decoded for the processing passes straight away into Encode. But to update some data out of the region or on another region, use the <emphasis >
<property>"renderRegionOnly"</property>
</emphasis>
- attribute set to <property>"false"</property> (<property>"true"</property> on default) to change this behaviour.</para>
+ attribute set to "false" ("true" on default) to change this behaviour.</para>
<para><emphasis role="bold">Example:</emphasis></para>
<programlisting role="XML"><![CDATA[<a4j:region renderRegionOnly="true">
<a4j:commandLink reRender="someID2" value="Link1" id="link1"/>
@@ -119,7 +119,7 @@
</h:panelGroup>
</a4j:region>]]></programlisting>
<para>This example shows that one of the regions is decoded when a link is used inside. Nevertheless,
- if after processing the "link1" is clicked, the first region passes into Encode as a root
+ if after processing the <code>link1</code> is clicked, the first region passes into Encode as a root
region and encode performance time is reduced. This optimization doesn't allow data update out of the
region and should be implemented very carefully. The data out of the region described with <code>renderRegionOnly="false"</code> is updated successfully.
</para>
Modified: trunk/docs/userguide/en/src/main/docbook/included/repeat.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/repeat.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/repeat.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -97,8 +97,8 @@
<title>Note:</title>
<para>The <emphasis role="bold">
<property><a4j:repeater></property>
- </emphasis> component is defined as fully updated, but really updated there are only the row keys which rowKeys includes into the set
- <property>ajaxRowSet</property>
+ </emphasis> component is defined as fully updated, but really updated there are only the row keys which <emphasis><property>"rowKeys"</property></emphasis> includes into the set
+ <emphasis><property>"ajaxRowSet"</property></emphasis>
defined in the <emphasis >
<property>"ajaxKeys"</property>
</emphasis> attribute </para>
@@ -107,7 +107,7 @@
</para>
</note>
<para>One more benefit of this component is absence of strictly defined markup as JSF HTML DataTable and TOMAHAWK DataTable has, hence the components could be used more flexibly anywhere where it's necessary to output the results of selection from some collection.</para>
-<para>The next example shows collection output as a plain HTML list</para>
+<para>The next example shows collection output as a plain HTML list:</para>
<programlisting role="XML"><![CDATA[<ul>
<a4j:repeat ...>
<li>...<li/>
Modified: trunk/docs/userguide/en/src/main/docbook/included/status.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/status.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/status.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -49,7 +49,7 @@
</itemizedlist>
<itemizedlist>
<listitem><para>
- With <emphasis ><property>"Start"/"Stop"</property></emphasis > facets definition:</para>
+ With <emphasis><property>"Start"</property></emphasis>/<emphasis><property>"Stop"</property></emphasis > facets definition:</para>
<programlisting role="XML"><![CDATA[<a4j:status for="stat2">
<f:facet name="start">
<h:graphicImage value="ajax_process.png" />
@@ -121,7 +121,7 @@
<para>There is a possibility to group a <emphasis role="bold"><property><a4j:status></property></emphasis> elements content into <emphasis role="bold"><property><div></property></emphasis> elements, instead of <emphasis role="bold"><property><span></property></emphasis>. To use it, just redefine the <emphasis >
<property>"layout"</property>
</emphasis>
- attribute from <property>"inline"</property>(default) to <property>"block"</property>.</para>
+ attribute from "inline" (default) to "block".</para>
</section>
<section>
<title>Relevant resources links</title>
Modified: trunk/docs/userguide/en/src/main/docbook/included/support.xml
===================================================================
--- trunk/docs/userguide/en/src/main/docbook/included/support.xml 2008-06-26 11:06:48 UTC (rev 9235)
+++ trunk/docs/userguide/en/src/main/docbook/included/support.xml 2008-06-26 12:50:56 UTC (rev 9236)
@@ -87,7 +87,7 @@
<programlisting role="XML"><![CDATA[
<input onkeyup="A4J.AJAX.Submit( Some request parameters )"/>
]]></programlisting>
- <para>As you see from the code, the <property>onkeyup</property>
+ <para>As you see from the code, the <emphasis><property>"onkeyup"</property></emphasis>
event calls a utility RichFaces method that submit a form creating a special marks for a filter informing that it is an Ajax request. Thus, any supports quantity could be added to every component, the supports define component behavior on these events. </para>
<note>
<para>The components: <emphasis role="bold"><property><a4j:commandLink></property></emphasis>, <emphasis role="bold"><property><a4j:commandButton></property></emphasis>, <emphasis role="bold">
More information about the richfaces-svn-commits
mailing list