For example, at the moment of this writing, the only supported skins are 'sam' and 'rime', so all components that support these skins have subdirectories inside 'skins' named exactly 'sam' and 'rime'. The name of this subdirectory should match the name of the skin across the entire project. Inside this directory, there should be a subdirectory for every skin that the component supports. However, it is possible to place these files in any location. They are placed, by convention, in a directory named ' skins' inside the component's source directory. These are all the raw, unprocessed skin-related files (i.e. It is important to first clarify what is meant by original files in this context. modified CSS files and generated images) will ultimately be prepared in the same way for JSF's resource handling mechanism. In any case, the resulting resources (i.e. Optionally, these resources will undergo an optimization that consists of generating sprite images. CSS and image files) are prepared at build time for JSF 2's resource handling mechanism. Therefore, in ICEfaces, all resources used for skinning components (i.e. There is a well-defined URL format that must be used to access resources through this mechanism.Resources are contained in resource libraries.The relevant points to this article are the following: It is explained in detail in section 2.6 of the JSF 2.0 specification. JSF 2 has its own resource handling mechanism. Finally, it describes how all CSS files of a skin are merged into one file.
#Sprite image cleaner how to#
It also explains how to add more components and skins to this process. This article describes the two different ways of skinning a component and explains how the various skin-related resources are prepared at build time to be served by JSF.
0 kommentar(er)
