Details
-
New Feature
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
2.0.1-core
-
None
Description
Trinidad skinning dynamically generates style sheets at runtime to meet context-specific (ie. platform/agent/locale/accessibility-specific) skinning requirements. While dynamic generation of style sheets is beneficial in that it allows fine tuning of which styles are delivered for particular contexts, it can complicate some use cases.
One case that dynamic generation makes particularly difficult is where the application and its resources are split across separate hosts/domains. In this case, resources are typically hosted on a dedicated server that can be:
a) Shared across multiple applications, thus improving the likelihood of browser cache hits. And...
b) More easily fronted by a CDN (without also having to route all application traffic through a CDN ).
Since a single skin definition can result in an arbitrary number of generated style sheets, it is not possible to host Trinidad skin/style sheets on a dedicated server - ie. there is currently no reliable way to pre-generate all possible variants of any given skin.
This issue requests that we add a new skin pregeneration feature that would allow all style sheet variants for any skin to be generated prior to application deployment. This would facilitate the the split application/resources scenario described above.