I'm wondering if people are ok with this Skin API I plan to add for
Issue 1687 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. Thanks, Jeanne |
- Re: [TRINIDAD][API]TRINIDAD-1668 Spee... Simon Lessard
- Re: [TRINIDAD][API]TRINIDAD-1668 ... Blake Sullivan
- Re: [TRINIDAD][API]TRINIDAD-1668 ... Simon Lessard
- Re: [TRINIDAD][API]TRINIDAD-1668 ... Blake Sullivan
- Re: [TRINIDAD][API]TRINIDAD-1668 ... Blake Sullivan
- Re: [TRINIDAD][API]TRINIDAD-1668 ... Simon Lessard
- Re: [TRINIDAD][API]TRINIDAD-1668 ... Blake Sullivan
- Re: [TRINIDAD][API]TRINIDAD-1668 ... Simon Lessard
- Re: [TRINIDAD][API]TRINIDAD-1668 ... Blake Sullivan
- RE: [TRINIDAD][API]TRINIDAD-1668 ... Maria Kaval
- [TRINIDAD][API] TRINIDAD-1687 add a Skin api that will cle... Jeanne Waldman