[richfaces-svn-commits] JBoss Rich Faces SVN: r12998 - trunk/docs/userguide/en/src/main/docbook/modules.

Author: msorokin Date: 2009-03-18 06:08:09 -0400 (Wed, 18 Mar 2009) New Revision: 12998 Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml Log: https://jira.jboss.org/jira/browse/RF-5737 org.richfaces.CONTROL_SKINNING_LEVEL option is documented Modified: trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml =================================================================== --- trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2009-03-18 09:58:40 UTC (rev 12997) +++ trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2009-03-18 10:08:09 UTC (rev 12998) @@ -3155,7 +3155,7 @@ <para> However, if you don&apos;t want the RichFaces components and standard HTML controls to be skinned automatically and perform the skinnability implementation yourself, you might encounter with a problem, namely standard HTML controls in such - browsers as Opera and Safari will affected by standard controls skinning featured. ( + browsers as Opera and Safari will be affected by standard controls skinning. ( <link linkend="ScriptsandStylesLoadStrategy">Here</link> you can get more details on how to disable skinnability.) </para> <para> In brief, to disable the skinnability mechanism of RichFaces you need to set the @@ -3205,8 +3205,8 @@ <title>XCSS File Format</title> <para> XCSS files are the core of RichFaces components skinnability. </para> <para> XCSS is an XML formatted CSS that adds extra functionality to the skinning - process </para> - <para> XCSS extends skinning possibilities by parsing the XCSS file that contains all + process. + XCSS extends skinning possibilities by parsing the XCSS file that contains all look-and-feel parameters of a particular component into a standard CSS file that a web browser can recognize. </para> <para> XCSS file contains CSS properties and skin parameters mappings. Mapping of a CSS @@ -3225,7 +3225,7 @@ </u:selector> ... ]]></programlisting> - <para> During processing the code in the shown example will be parsed into a standard + <para> During processing the code in the shown example is parsed into a standard CSS format. </para> <programlisting role="CSS"><![CDATA[... .rich-component-name { @@ -3369,7 +3369,7 @@ </listitem> <listitem> <para> - <property>SKIN-NAME.properties</property> - a XCSS file that contains + <property>SKIN-NAME.properties</property> - a file that contains properties of the new skin. Location: &quot;\src\main\resources\SKIN-PACKAGE\SKIN-NAME\css\&quot; </para> @@ -3399,7 +3399,7 @@ </listitem> <listitem> <para> - <property>gradientType</property> is a predefined property to set + <property>gradientType</property> - a predefined property to set the type of gradient applied to the new skin. Possible values are glass, plastic, plain. More information on gradient implementation you can find further in this chapter. </para> @@ -3423,7 +3423,7 @@ </listitem> <listitem> <para> - <property>SKIN-NAME-ext.xcss</property> / If the command is executed with + <property>SKIN-NAME-ext.xcss</property> If the command is executed with the &quot;DcreateExt&quot; key set to &quot;true&quot;, the configuration SKIN-NAME-ext.xcss file that imports XCSS file defining styles for the standard controls will be created. Location: @@ -3439,11 +3439,11 @@ <para>Now you can start editing the XCSS files located in &quot;\src\main\resources\SKIN-PACKAGE\SKIN-NAME\css\&quot;. New style properties can be assigned to the selectors (the selectors listed in the XCSS files) in two - ways, which are both valid, and it&apos;up to the developer what way to choose. </para> + ways, which are both valid, and it&apos;up to you what way to choose. </para> <itemizedlist> <listitem> - <para>Applying a standard CSS coding approach, i.e. you can add css properties - to the given selectors are you normally do while doing CSS coding. The only + <para>Standard CSS coding approach, i.e. you can add CSS properties + to the given selectors. The only thing, you have to keep in mind is that the selectors must be inside <code>&lt;f:verbatim&gt; &lt;![CDATA[ ...]]&gt; &lt;/f:verbatim&gt;</code> tags.</para> @@ -3601,7 +3601,7 @@ <para>All the changes that were planned to be preformed are done and now you can proceed to building the new PlugnSkinDemo skin and import it into the project. As you read in the previous section, the skin should be built in the - &quot;P-n-S&quot; folder of the skin project be executing <code>mvn clean + &quot;P-n-S&quot; folder of the skin project by executing <code>mvn clean install</code> command. This procedure results in creating a &quot;target&quot; folder that contains a .jar file with a compiled new skin, it our case the file is named &quot;P-n-S-1.0.-SNAPSHOT.jar&quot;. The next step is @@ -3633,7 +3633,7 @@ <param-value>enable</param-value> </context-param> ]]></programlisting> - <para>The result of both action is displayed on the figure below.</para> + <para>The result of both operations is displayed on the figure below.</para> <figure> <title>Plug-n-Skin feature in action. </title> <mediaobject>