2012-02-22, 06:19
I have made a fair attempt at a skinnable, localisable plugin - XSqueeze.
It uses a WindowXML - and loads the fallback skin file from Default/720p etc.
As far as I can tell, if users of non-Confluence want to skin this, then the skin maker has to create a particular file (XSqueezeNowPlaying.xml) and supply that with their skin.
It seems to me a better way would for this to be included with the add on (meaning it's easier for non skin writers to supply me with one they have knocked up) and for the addon to detect their current skin (how) and create the appriopriate WindowXML directly.
Is this a good approach? It seems less likely that skinners will find, get motivated, and make the appropriate xml than users of the plugin ...and then they would quickly benefit all users of the particular plugin+skin combination.
Your thoughts appreciated (especially if I have misunderstood how this is supposed to work!!)
It uses a WindowXML - and loads the fallback skin file from Default/720p etc.
As far as I can tell, if users of non-Confluence want to skin this, then the skin maker has to create a particular file (XSqueezeNowPlaying.xml) and supply that with their skin.
It seems to me a better way would for this to be included with the add on (meaning it's easier for non skin writers to supply me with one they have knocked up) and for the addon to detect their current skin (how) and create the appriopriate WindowXML directly.
Is this a good approach? It seems less likely that skinners will find, get motivated, and make the appropriate xml than users of the plugin ...and then they would quickly benefit all users of the particular plugin+skin combination.
Your thoughts appreciated (especially if I have misunderstood how this is supposed to work!!)