sounds like a nice feature. +1 On Fri, Jan 15, 2010 at 1:13 AM, Blake Sullivan <blake.sulli...@oracle.com> wrote: > looks good. > > -- Blake Sullivan > > Jeanne Waldman (JIRA) said the following On 1/14/2010 4:08 PM PT: >> >> 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 >> >> >> 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. >> >> >> >> > >
-- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
