Posts tagged skinning
Using ADF Faces 11g Skinning for setting the styles of specific component instances or groups of instances
Skinning in ADF Faces is used to define user defined customizations with respect to one of the standard ADF skins. A skin is by and large a CSS document (CSS 3.0) that is interpreted at run time to generate the 'real' CSS documents (3.0 if that is what the browser can handle, 2.0 in most current cases) that will be sent to the browser. The real CSS document is influenced primarily by the server side Skin CSS (CSS 3.0 is converted to 2.0 if that is required) and also by factors like: browser (IE, Firefox, Safari, something else), version (5.5, 6.0, 7.0, 8.0; 2.x, 3.x;…), operating system, locale, etc. The skin is created as an extension of one of three standard skins shipped with ADF Faces.
n this article I would point at an feature of skinning I was not aware of before: skin styles need not apply to all instances of a component (sort of my previous understanding) but can be directed at specific occurrences of components:
- all component instances that have a specific styleClass set - all component instances under a specific ancestor element (that may or may not have a specific styleClass set)
Let us discuss an example of these characteristics of skinning I was not aware of More >
ADF 11g Rich Client Components have a facility called the Change(d) Indicator. The changed attribute is specified using a Boolean value or expression (typically the latter). When the expression evaluates to true, a visual indication is rendered on the component that signifies to the user that the item’s value has changed. While we can use this indicator in any way we see fit, a logical use case would be to highlight with this indicator any field that has been updated as a result of a partial page request/refresh – the AJAX style immediate update of portion of the page as a response to action by the user.
For example: when the temperature is entered in the Temperature Fahrenheit item (or changed using the Spin Controls), an auto submit is performed that in turn leads to an update of the Temperature Celsius item. Because of the changed attribute, the user can clearly identify the items that were automagically changed. Note: In this case we have used a custom skin that specifies another icon for the changed indicator (you will see the default icon later on in this article).