Posts tagged styling
In a recent article (http://technology.amis.nl/2013/04/02/adf-dvt-using-the-tree-map-visualization-component-to-compare-relative-sizes-and-distributions/) I discussed the ADF DVT Treemap component. This component visualizes data in such a way that comparisons between data values for different records and categories can quickly be made. The size of areas is a measure for some numerical value. As an additional dimension, the color of the areas can be used to identify groups (all members of the group having the same color) or to visualize a second numerical value (color can range for example from dark red to rich green depending on the net revenue per record).
This article describes the situation where we want to use multiple Treemap instances lined up. Each Treemap instance represents a collection of records on one or possibly multiple levels. Each instance can be drilled down into independently. And each instance can represent a different data set, even though we want to compare these data sets. Using a PanelGridLayout, it is easy to position multiple instances in a row or a grid. Using the inline style to scale the width and height of the Treemap instances, we can set the relative More >
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 >