[ajax4jsf-svn-commits] JBoss Ajax4JSF SVN: r290 - trunk/docs/userguide/en/src/main/docbook/included.

Author: smukhina Date: 2007-06-28 07:34:21 -0400 (Thu, 28 Jun 2007) New Revision: 290 Modified: trunk/docs/userguide/en/src/main/docbook/included/ajaxListener.xml trunk/docs/userguide/en/src/main/docbook/included/commandButton.xml trunk/docs/userguide/en/src/main/docbook/included/commandLink.xml trunk/docs/userguide/en/src/main/docbook/included/form.xml trunk/docs/userguide/en/src/main/docbook/included/htmlCommandLink.xml trunk/docs/userguide/en/src/main/docbook/included/support.xml Log: language correction Modified: trunk/docs/userguide/en/src/main/docbook/included/ajaxListener.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/ajaxListener.xml 2007-06-28 09:14:36 UTC (rev 289) +++ trunk/docs/userguide/en/src/main/docbook/included/ajaxListener.xml 2007-06-28 11:34:21 UTC (rev 290) @@ -6,6 +6,6 @@ </a4j:region>]]> </programlisting> <para> - Every time when AJAX request triggered from "region" method "processAjax" of "bean" will be called. + Every time when AJAX request triggered from &quot;region&quot; method &quot;processAjax&quot; of &quot;bean&quot; will be called. </para> </root> \ No newline at end of file Modified: trunk/docs/userguide/en/src/main/docbook/included/commandButton.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/commandButton.xml 2007-06-28 09:14:36 UTC (rev 289) +++ trunk/docs/userguide/en/src/main/docbook/included/commandButton.xml 2007-06-28 11:34:21 UTC (rev 290) @@ -53,7 +53,7 @@ <title>Note:</title> <para>AJAX support is built in and it&apos;s not necessary to add nested <emphasis role="bold"><property>&lt;a4j:support&gt;</property></emphasis> to the component.</para> </note> - <para>Common JSF navigation could be performed after AJAX submit and partial rendering, but Navigation Case must be defined as <emphasis role="bold"><property>&lt;redirect/&gt;</property></emphasis> in order to avoid problems with some browsers.</para> + <para>Common JSF navigation could be performed after an AJAX submit and partial rendering, but Navigation Case must be defined as <emphasis role="bold"><property>&lt;redirect/&gt;</property></emphasis> in order to avoid problems with some browsers.</para> <para>As any Ajax4jsf component sending AJAX requests and processing server responses <emphasis role="bold"><property>&lt;a4j:commandButton&gt;</property></emphasis> has all attributes described above (see <emphasis role="bold"><property>&lt;a4j:support&gt;</property></emphasis> chapter) that provide the required behavior of requests sending (delay, limitation of submit area and rendering, and etc.)</para> </section> </chapter> \ No newline at end of file Modified: trunk/docs/userguide/en/src/main/docbook/included/commandLink.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/commandLink.xml 2007-06-28 09:14:36 UTC (rev 289) +++ trunk/docs/userguide/en/src/main/docbook/included/commandLink.xml 2007-06-28 11:34:21 UTC (rev 290) @@ -35,7 +35,7 @@ <title>Creating on a page</title> <para><emphasis role="bold"><property>&lt;a4j:commandLink&gt;</property></emphasis> is used in the same way as <emphasis role="bold"><property>&lt;h:commandLink&gt;</property></emphasis>, but with definition of the area that is updated after the response comes back from the server.</para> <programlisting role="XML"><![CDATA[<a4j:commandLink reRender="someData" action="#{bean.action1}" value="Link"/>]]></programlisting> - <para>This definition of the component provides a link, a click on the link causes an AJAX form + <para>This definition of the component provides a link, and a click on the link causes an AJAX form submit on the server, &quot;action1&quot; method performance, and rendering of the component with &quot;someData&quot; id after the response comes back from the server.</para> </section> Modified: trunk/docs/userguide/en/src/main/docbook/included/form.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/form.xml 2007-06-28 09:14:36 UTC (rev 289) +++ trunk/docs/userguide/en/src/main/docbook/included/form.xml 2007-06-28 11:34:21 UTC (rev 290) @@ -50,7 +50,7 @@ <section> <title>Key attributes and ways of usage</title> <para>The difference with the original component is that all hidden fields required for command links are always rendered and it doesn't depend on links rendering on the initial page. It solves the problem with invalid links that weren't rendered on a page immediately, but after some AJAX request.</para> - <para>Beginning with release 1.0.5 additional attributes that make this form variant universal appear. With a new attribute definition as ajax=<emphasis role="italic"> + <para>Beginning with release 1.0.5 additional attributes that make this form variant universal have appeared. With a new attribute definition as ajax=<emphasis role="italic"> <property>&quot;true&quot;</property> </emphasis>, it becomes possible to set AJAX submission way for any components inside, i.e. not a page URL is used as an <emphasis role="italic"> <property>&quot;action&quot;</property> Modified: trunk/docs/userguide/en/src/main/docbook/included/htmlCommandLink.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/htmlCommandLink.xml 2007-06-28 09:14:36 UTC (rev 289) +++ trunk/docs/userguide/en/src/main/docbook/included/htmlCommandLink.xml 2007-06-28 11:34:21 UTC (rev 290) @@ -47,7 +47,7 @@ </section> <section> <title>Key attributes and ways of usage</title> - <para>The difference with the original component is that all hidden fields required for command links with child <emphasis role="bold"> + <para>The difference with the original component is that all hidden fields required for command links with the child <emphasis role="bold"> <property>&lt;f:param&gt;</property> </emphasis> elements are always rendered and it doesn't depend on links rendering on the initial page. It solves the problem with invalid links that weren&apos;t rendered on a page immediately, but after some AJAX request.</para> <programlisting role="XML"><![CDATA[<a4j:form> Modified: trunk/docs/userguide/en/src/main/docbook/included/support.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/included/support.xml 2007-06-28 09:14:36 UTC (rev 289) +++ trunk/docs/userguide/en/src/main/docbook/included/support.xml 2007-06-28 11:34:21 UTC (rev 290) @@ -43,7 +43,7 @@ <a4j:support event="onkeyup" reRender="repeater"/> </h:inputText> <h:outputText id="repeater" value="#{bean.text}"/>]]></programlisting> - <para>On every keyup event generated by an input field, form is submitted on the server via Ajax and + <para>On every keyup event generated by an input field, a form is submitted on the server with the help of Ajax and on a response coming from the server, element with &quot;repeater&quot; id, founded in a DOM tree is redrawn according to a new data from the response.</para> </section> @@ -77,7 +77,7 @@ </note> <para>With the help of <emphasis role="italic"> <property>&quot;onsubmit&quot;</property></emphasis> and <emphasis role="italic"> - <property>&quot;oncomplete&quot;</property></emphasis> attributes the component allows using JavaScript before (for request sending conditions checking) and after AJAX response processing termination (for performance of user-defined activities on the client) </para> + <property>&quot;oncomplete&quot;</property></emphasis> attributes the component allows using JavaScript before (for request sending conditions checking) and after an AJAX response processing termination (for performance of user-defined activities on the client) </para> <para><emphasis role="bold">Example:</emphasis></para> <programlisting role="XML"><![CDATA[<h:selectOneMenu value="#{bean.text}"> <f:selectItem itemValue="First Item " itemLabel="First Item"/> @@ -86,7 +86,7 @@ <a4j:support event="onblur" reRender="panel" onsubmit="if(!confirm('Are you sure to change the option ?')) {form.reset(); return false;}" oncomplete="alert('Value succesfully stored')"/> </h:selectOneMenu>]]></programlisting> - <para>In example there is the condition checking (confirm) is used before request sending and message printing after the request processing is over. </para> + <para>In example there is the condition checking (confirm) is used before request sending and message printing after the request processing is over. </para> <para>The components allows different AJAX request managing ways for its various optimization in particular conditions such as: <itemizedlist> <listitem> @@ -122,7 +122,7 @@ <para><emphasis role="italic"><property>&quot;requestDelay&quot;</property></emphasis> is an attribute that defines a time interval in seconds minimally permissible between responses. </para> - <para><emphasis role="italic"><property>&quot;eventQueue&quot;</property></emphasis> is an attribute for naming of the queue where the next response is kept in till its processing, but if the next event comes in till this time, the waiting event is taken away, replacing with a new one. + <para><emphasis role="italic"><property>&quot;eventQueue&quot;</property></emphasis> is an attribute for naming of the queue where the next response is kept in till its processing, but if the next event comes in till this time is over, the waiting event is taken away, replacing with a new one. </para> <para><emphasis role="italic"><property>&quot;ignoreDupResponces&quot;</property></emphasis> is an attribute that allows to disable any updates on the client after an AJAX request if another AJAX request is already sent. @@ -138,7 +138,7 @@ <h:outputText value="#{person.name}" id="test"/> </form>]]></programlisting> <para>This example clearly shows mentioned above attributes. If quick typing in a text field happens, every next requests sending is delayed for a second and requests quantity is reduced. The requests are kept in the queue &quot;myQueue&quot; till its the sending. -Moreover, if the next request is already sent, the rerendering after the previous request is banned, and +Moreover, if the next request is already sent, the rerendering after the previous request is banned, and it helps to avoid unnecessary processing on the client.</para> </listitem> </itemizedlist>