You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Andy Schwartz (Commented) (JIRA)" <de...@myfaces.apache.org> on 2012/03/06 15:59:57 UTC

[jira] [Commented] (TRINIDAD-2234) Pregeneration of skin style sheets

    [ https://issues.apache.org/jira/browse/TRINIDAD-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223299#comment-13223299 ] 

Andy Schwartz commented on TRINIDAD-2234:
-----------------------------------------

Note that this issue:

TRINIDAD-2235 Skinning: stable names for generated style sheets

Is a pre-requisite for any skin pregeneration solution.  Without stable names for generated style sheets, it won't be possible for Trinidad applications to route style sheet requests hosted/pregenerated style sheets since the file names would not necessarily align.
                
> Pregeneration of skin style sheets
> ----------------------------------
>
>                 Key: TRINIDAD-2234
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2234
>             Project: MyFaces Trinidad
>          Issue Type: New Feature
>          Components: Skinning
>    Affects Versions: 2.0.1-core
>            Reporter: Andy Schwartz
>            Assignee: Andy Schwartz
>            Priority: Minor
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira