[
https://issues.apache.org/jira/browse/TRINIDAD-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeanne Waldman resolved TRINIDAD-1687.
--------------------------------------
Resolution: Fixed
Fix Version/s: 1.2.13-core
> add a Skin api that will clear the skin file(s) and reload at runtime
> ---------------------------------------------------------------------
>
> Key: TRINIDAD-1687
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1687
> Project: MyFaces Trinidad
> Issue Type: New Feature
> Components: Skinning
> Reporter: Jeanne Waldman
> Assignee: Jeanne Waldman
> Fix For: 1.2.13-core
>
> Attachments: SkinIsDirtyAPITrunk.patch
>
>
> We've had several requests where someone wants to reload the skin on demand
> but without needing the web.xml's CHECK_FILE_MODIFICATION flag on. On
> instance is the design time team who wants to muck with skins and reload them
> on demand.
> The proposed public API is on the Skin object. It is:
> /**
> * Check to see if this Skin has been marked dirty.
> * The only way to mark a Skin dirty is to call setDirty(true).
> * @return true if the Skin is marked dirty.
> */
> abstract public boolean isDirty();
> /**
> * Sets the dirty flag of the Skin. Use this if you want to regenerate the
> skin.
> * During rendering, if isDirty is true,
> * the skin's css file will be reprocessed regardless of whether the css
> file has been modified
> * or if the CHECK_FILE_MODIFICATION flag was set.
> * The Skinning Framework calls setDirty(false) after the skin has been
> reprocessed.
> */
> abstract public void setDirty(boolean dirty);
> A patch will be available soon.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
