Author: ilya_shaikovsky
Date: 2011-03-15 12:02:57 -0400 (Tue, 15 Mar 2011)
New Revision: 22226
Modified:
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/standardSkinning/standardSkinning.xhtml
Log:
just changed wrong context-param names.
Modified:
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/standardSkinning/standardSkinning.xhtml
===================================================================
---
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/standardSkinning/standardSkinning.xhtml 2011-03-15
14:56:45 UTC (rev 22225)
+++
branches/4.0.X/examples/richfaces-showcase/src/main/webapp/richfaces/standardSkinning/standardSkinning.xhtml 2011-03-15
16:02:57 UTC (rev 22226)
@@ -71,18 +71,18 @@
<p>There three ways of applying skinning to application:</p>
<ul>
- <li>By default <b>org.richfaces.ENABLE_CONTROL_SKINNING</b> context
+ <li>By default <b>org.richfaces.enableControlSkinning</b> context
param is set to <b>true</b> and it means that all standard elements
on the page will be skinned. (CSS style classes for elements based on
their names and type attribute values will be applied). You may
redefine it to <b>disable</b> in order to turn it off.</li>
- <li>By default <b>org.richfaces.ENABLE_CONTROL_SKINNING_CLASSES</b>
+ <li>By default <b>org.richfaces.enableControlSkinningClasses</b>
context param is set to <b>false</b> and it means that basic elements
nested to element having <i>rich-container</i> class will be skinned.
It could be also turned off using <b>disable</b> value.</li>
<li>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.ENABLE_CONTROL_SKINNING_CLASSES</b>
+ This classes added to the page also according to
<b>org.richfaces.enableControlSkinningClasses</b>
context-param.</li>
</ul>
Show replies by date