From richfaces-svn-commits at lists.jboss.org Wed Mar 18 06:09:13 2009 Content-Type: multipart/mixed; boundary="===============2010031083842209564==" MIME-Version: 1.0 From: richfaces-svn-commits at lists.jboss.org To: richfaces-svn-commits at lists.jboss.org Subject: [richfaces-svn-commits] JBoss Rich Faces SVN: r12998 - trunk/docs/userguide/en/src/main/docbook/modules. Date: Wed, 18 Mar 2009 06:08:09 -0400 Message-ID: --===============2010031083842209564== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2= 009-03-18 09:58:40 UTC (rev 12997) +++ trunk/docs/userguide/en/src/main/docbook/modules/RFCarchitectover.xml 2= 009-03-18 10:08:09 UTC (rev 12998) @@ -3155,7 +3155,7 @@ However, if you don't want the RichFaces components and st= andard HTML controls to be skinned automatically and perform the skinnability impl= ementation yourself, you might encounter with a problem, namely standard HTML con= trols in such - browsers as Opera and Safari will affected by standard controls skinni= ng featured. ( + browsers as Opera and Safari will be affected by standard controls ski= nning. ( Here you can ge= t more details on how to disable skinnability.) In brief, to disable the skinnability mechanism of RichFaces you= need to set the @@ -3205,8 +3205,8 @@ XCSS File Format XCSS files are the core of RichFaces components skinnability. XCSS is an XML formatted CSS that adds extra functionality to th= e skinning - process - XCSS extends skinning possibilities by parsing the XCSS file tha= t contains all + process. = + XCSS extends skinning possibilities by parsing the XCSS file that conta= ins all look-and-feel parameters of a particular component into a standard CSS= file that a web browser can recognize. XCSS file contains CSS properties and skin parameters mappings. = Mapping of a CSS @@ -3225,7 +3225,7 @@ ... ]]> - During processing the code in the shown example will be parsed i= nto a standard + During processing the code in the shown example is parsed into a= standard CSS format. - SKIN-NAME.properties - a XCSS file that contains + SKIN-NAME.properties - a file that contains properties of the new skin. Location: "\src\main\resources\SKIN-PACKAGE\SKIN-NAME\css\" @@ -3399,7 +3399,7 @@ - gradientType is a predefined property to set + gradientType - 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. @@ -3423,7 +3423,7 @@ - SKIN-NAME-ext.xcss / If the command is executed= with + SKIN-NAME-ext.xcss If the command is executed w= ith the "DcreateExt" key set to "true", the configur= ation SKIN-NAME-ext.xcss file that imports XCSS file defining styles for t= he standard controls will be created. Location: @@ -3439,11 +3439,11 @@ Now you can start editing the XCSS files located in "\src\main\resources\SKIN-PACKAGE\SKIN-NAME\css\". New style= properties can be assigned to the selectors (the selectors listed in the XCSS fil= es) in two - ways, which are both valid, and it'up to the developer what way t= o choose. + ways, which are both valid, and it'up to you what way to choose. = - Applying a standard CSS coding approach, i.e. you can add css p= roperties - to the given selectors are you normally do while doing CSS coding. T= he only + 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 <f:verbatim> <![CDATA[ ...]]> </f:verbatim> tags. @@ -3601,7 +3601,7 @@ All the changes that were planned to be preformed are done and n= ow 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 - "P-n-S" folder of the skin project be executing mvn c= lean + "P-n-S" folder of the skin project by executing mvn c= lean install command. This procedure results in creating a "target" folder that contains a .jar file with a compiled n= ew skin, it our case the file is named "P-n-S-1.0.-SNAPSHOT.jar". The n= ext step is @@ -3633,7 +3633,7 @@ enable ]]> - The result of both action is displayed on the figure below. + The result of both operations is displayed on the figure below.<= /para>
Plug-n-Skin feature in action. --===============2010031083842209564==--