Author: smukhina Date: 2009-06-03 11:06:36 -0400 (Wed, 03 Jun 2009) New Revision: 14452 Modified: branches/community/3.3.X/docs/photo_album_app_guide/en/src/main/docbook/includes/uploadImages.xml branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/comboBox.desc.xml branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/comboBox.xml branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/contextMenu.xml branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/fileUpload.xml branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/hotKey.desc.xml branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/jsFunction.desc.xml branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/jsFunction.xml branches/community/3.3.X/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml Log: https://jira.jboss.org/jira/browse/RF-7287 "client side" is replace with "client-side" everywhere in RF guides where the phrase is used as a complex adjective "server side" is replace with "server-side" everywhere in RF guides where the phrase is used as a complex adjective Modified: branches/community/3.3.X/docs/photo_album_app_guide/en/src/main/docbook/includes/uploadImages.xml =================================================================== --- branches/community/3.3.X/docs/photo_album_app_guide/en/src/main/docbook/includes/uploadImages.xml 2009-06-03 12:30:46 UTC (rev 14451) +++ branches/community/3.3.X/docs/photo_album_app_guide/en/src/main/docbook/includes/uploadImages.xml 2009-06-03 15:06:36 UTC (rev 14452) @@ -19,7 +19,7 @@ <para>Definition of permitted file types in the &quot;Open File&quot; dialog window;</para> </listitem> <listitem> - <para>A number of additional client side object properties.</para> + <para>A number of additional client-side object properties.</para> </listitem> </itemizedlist> <para> Modified: branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/comboBox.desc.xml =================================================================== --- branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/comboBox.desc.xml 2009-06-03 12:30:46 UTC (rev 14451) +++ branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/comboBox.desc.xml 2009-06-03 15:06:36 UTC (rev 14452) @@ -24,7 +24,7 @@ <title>Key Features</title> <itemizedlist> <listitem> - <para>Client side suggestions</para> + <para>Client side-suggestions</para> </listitem> <listitem> <para>Browser like selection</para> Modified: branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/comboBox.xml =================================================================== --- branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/comboBox.xml 2009-06-03 12:30:46 UTC (rev 14451) +++ branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/comboBox.xml 2009-06-03 15:06:36 UTC (rev 14452) @@ -65,7 +65,7 @@ <para>The <emphasis role="bold"> <property>&lt;rich:comboBox&gt;</property> </emphasis> - is a simplified suggestion box component, that provides input with client side suggestions. + is a simplified suggestion box component, that provides input with client-side suggestions. <!-- component consists of an <property>input field</property>, the <property>button</property> and the <property>popup list</property> of suggestions attached to input. If you want to see the popup list you can press the <property>button</property> or type the first letter of suggested word in the <property>input field</property>. Modified: branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/contextMenu.xml =================================================================== --- branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/contextMenu.xml 2009-06-03 12:30:46 UTC (rev 14451) +++ branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/contextMenu.xml 2009-06-03 15:06:36 UTC (rev 14452) @@ -65,7 +65,7 @@ <emphasis role="bold"> <property>&lt;rich:contextMenu&gt;</property> </emphasis> is a support-like component. Context menu itself is an invisible panel that - appears after a particular client side event (<emphasis><property>&quot;onmouseover&quot;</property></emphasis>, <emphasis><property>&quot;onclick&quot;</property></emphasis>, etc.) occurred on a + appears after a particular client-side event (<emphasis><property>&quot;onmouseover&quot;</property></emphasis>, <emphasis><property>&quot;onclick&quot;</property></emphasis>, etc.) occurred on a parent component. The event is defined with an <emphasis> <property>&quot;event&quot;</property> </emphasis> attribute. The component uses <emphasis> Modified: branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/fileUpload.xml =================================================================== --- branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/fileUpload.xml 2009-06-03 12:30:46 UTC (rev 14451) +++ branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/fileUpload.xml 2009-06-03 15:06:36 UTC (rev 14452) @@ -626,7 +626,7 @@ <table id="objectProperties"> - <title>Client side object properties</title> + <title>Client side-object properties</title> <tgroup cols="2"> <thead> <row> @@ -739,7 +739,7 @@ <table id="objectPropertiesWithAttributes"> - <title>Client side object properties available with specific <link + <title>Client-side object properties available with specific <link linkend="fileUploadEventAttributes"> event attributes</link></title> <tgroup cols="2"> <thead> Modified: branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/hotKey.desc.xml =================================================================== --- branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/hotKey.desc.xml 2009-06-03 12:30:46 UTC (rev 14451) +++ branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/hotKey.desc.xml 2009-06-03 15:06:36 UTC (rev 14452) @@ -10,7 +10,7 @@ <title>Description</title> <para>The <emphasis role="bold"> <property>&lt;rich:hotKey&gt;</property> - </emphasis> component allows to register hot keys for the page or particular elements and to define client side processing functions for these keys. + </emphasis> component allows to register hot keys for the page or particular elements and to define client-side processing functions for these keys. </para> </section> <section> Modified: branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/jsFunction.desc.xml =================================================================== --- branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/jsFunction.desc.xml 2009-06-03 12:30:46 UTC (rev 14451) +++ branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/jsFunction.desc.xml 2009-06-03 15:06:36 UTC (rev 14452) @@ -11,7 +11,7 @@ <para> The <emphasis role="bold"> <property>&lt;a4j:jsFunction&gt;</property> - </emphasis> component allows to invoke the server side data and return it in a JSON format to use in a client JavaScript calls. + </emphasis> component allows to invoke the server-side data and return it in a JSON format to use in a client JavaScript calls. </para> </section> </chapter> \ No newline at end of file Modified: branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/jsFunction.xml =================================================================== --- branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/jsFunction.xml 2009-06-03 12:30:46 UTC (rev 14451) +++ branches/community/3.3.X/docs/userguide/en/src/main/docbook/included/jsFunction.xml 2009-06-03 15:06:36 UTC (rev 14452) @@ -106,7 +106,7 @@ </emphasis> is similar to <emphasis role="bold"> <property>&lt;a4j:commandButton&gt;</property> </emphasis>, but it could be activated from the JavaScript code. It allows to invoke some - server side functionality and use the returned data in the JavaScript function invoked from + server-side functionality and use the returned data in the JavaScript function invoked from <emphasis><property>&quot;oncomplete&quot;</property></emphasis> attribute. Hence it&apos;s possible to use <emphasis role="bold"> <property>&lt;a4j:jsFunction&gt;</property> Modified: branches/community/3.3.X/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml =================================================================== --- branches/community/3.3.X/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2009-06-03 12:30:46 UTC (rev 14451) +++ branches/community/3.3.X/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2009-06-03 15:06:36 UTC (rev 14452) @@ -340,7 +340,7 @@ events are produced simultaneously, they will come to the server simultaneously. JSF implementations (especially, the very first ones) does not guaranty that the request that comes first will be served or passed into the JSF lifecycle first. The order - how the server side data will be modified in case of simultaneous request might be + how the server-side data will be modified in case of simultaneous request might be unpredictable. Usage of eventsQueue attribute allows to avoid possible mess. Define the queue name explicitly, if you expect intensive Ajax traffic in your application. </para> <para> The next request posted in the same queue will wait until the previos one is not @@ -820,7 +820,7 @@ update will be performed. </para> </listitem> <listitem> - <para> If you want to involve the server side validators and navigate to the + <para> If you want to involve the server-side validators and navigate to the next page only if the Validation phase is passed successfully, you can replace <emphasis role="bold"> <property>&lt;h:commandButton&gt;</property>