Author: smukhina Date: 2008-07-15 08:35:17 -0400 (Tue, 15 Jul 2008) New Revision: 9605 Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/jsFunction/usage.xhtml trunk/samples/richfaces-demo/src/main/webapp/richfaces/plugnskin/usage.xhtml trunk/samples/richfaces-demo/src/main/webapp/richfaces/standardSkinning/usage.xhtml Log: http://jira.jboss.com/jira/browse/RF-398 language is corrected in livedemo Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/jsFunction/usage.xhtml =================================================================== --- trunk/samples/richfaces-demo/src/main/webapp/richfaces/jsFunction/usage.xhtml 2008-07-15 12:28:53 UTC (rev 9604) +++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/jsFunction/usage.xhtml 2008-07-15 12:35:17 UTC (rev 9605) @@ -11,7 +11,7 @@ <p>a4j:jsFunction component is very similar to a4j:commandButton, but allows to perform an Ajax request from a Javascript code directly. The component sends a request using a standard JSF approach, so the JSF form is required. The following example - shows how the part of the page is re-rendered when a user hovers over the names. + shows how the part of a page is re-rendered when a user hovers over the names. </p> <fieldset class="demo_fieldset"> @@ -37,7 +37,7 @@ </a>. </p> <p> - As for any other Ajax components, you can use <b>reRender</b> attribute to update the area(s) of the page + As for any other Ajax components, you can use <b>reRender</b> attribute to update the area(s) of a page after an Ajax Response comes back. Also, you can use <b>data</b> attribute and <b>oncomplete</b> attribute to take the data from the server and use them for Javascript to call them. For additional information about Javascript oriented and other important attributes of a4j:jsFunction read Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/plugnskin/usage.xhtml =================================================================== --- trunk/samples/richfaces-demo/src/main/webapp/richfaces/plugnskin/usage.xhtml 2008-07-15 12:28:53 UTC (rev 9604) +++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/plugnskin/usage.xhtml 2008-07-15 12:35:17 UTC (rev 9605) @@ -27,7 +27,7 @@ by taking the base skin as basis and plugging-in custom styles. </p> <p> - You may freely create your own pluggable skin in a next way: + You may freely create your own pluggable skin in the next way: </p> <ul> <li> @@ -39,17 +39,17 @@ root folder of richfaces. </li> <li> - <b>Create new pluggable skin inside project</b> using + <b>Create new pluggable skin inside the project</b> using <i>mvn cdk:add-skin -Dname=*SKIN-NAME* -Dpackage=*SKIN-PACKAGE*</i> from the folder created on the previous step. </li> </ul> <p> - In the result you'll get new skin project. + In the result you'll get a new skin project. </p> <p class="note"> In order to check some other optional parameters for CDK commands and - more info about the feature in general - visit corresponding + more info about the feature in general - visit the corresponding developer guide section and explore <b>Laguna</b> skin project in richfaces/samples svn. </p> @@ -74,8 +74,8 @@ </li> </ul> <p> - All classes for all the components and standard skinning classes already - listed in corresponding imported xcss files. So you'll only need to fill them + All classes for all the components and standard skinning classes are already + listed in corresponding imported xcss files. Thus you'll only need to fill them with the properties you need. </p> <p> Modified: trunk/samples/richfaces-demo/src/main/webapp/richfaces/standardSkinning/usage.xhtml =================================================================== --- trunk/samples/richfaces-demo/src/main/webapp/richfaces/standardSkinning/usage.xhtml 2008-07-15 12:28:53 UTC (rev 9604) +++ trunk/samples/richfaces-demo/src/main/webapp/richfaces/standardSkinning/usage.xhtml 2008-07-15 12:35:17 UTC (rev 9605) @@ -30,21 +30,21 @@ </p> <p> This feature provides styling for standard HTML form elements - in order to be highly compilant to RichFaces common look'n'feel. There + in order to be highly compilant with RichFaces common look'n'feel. There should be two ways of applying skins to elements: </p> <ul> <li> Skinning style classes are applied to elements by element name and type attribute (where applicable). No additional steps - required from an application developer. Application initialization + are required from an application developer. Application initialization parameter serves for enabling/disabling the feature. </li> <li> Several style classes are provided for different types of elements. That style classes have predefined names. Application developer should manually assign classes to controls that need - skinning or assign class to an element that contains controls. + skinning or assign a class to an element that contains controls. </li> </ul> <p> @@ -89,7 +89,7 @@ will be skinned. It could be also turned off using <b>disable</b> value. </li> <li> - Rich faces also provides predefined classes which can be applied by end developer + RichFaces also provides predefined classes which can be applied by an end developer to elements need to be skinned separately. This classes added to the page also according to <b>org.richfaces.CONTROL_SKINNING_CLASSES</b> context-param. </li> @@ -113,7 +113,7 @@ </rich:panel> </fieldset> <p> - And the last one way means that classes with names corresponding to elements names + And the last one means that classes with names corresponding to elements names will be added to the application pages and possible to set manually: </p> <fieldset class="demo_fieldset">