skin xml files

[Tuathanach]

Is it possible to include in the zip containing the skin art to include any gui xml files which are required to make the skin display properly, this would make it easier to have several custom skins. the xml files in the zip would take preferance over default ones meanning default xml's wouldn't have to be touched. This would make it easy to switch back to origanal skins without having to restore origanal xml files as they would already be there.

Thanks

[Arerano]

I really like this idea and had some similar already.

However, XML changes I make work with all "official" skins.
Maybe one could have different XML and SKIN mods and the XML mod defines with which SKINS it works.
eg:
"default" layout (XMLs) -> works* with skins group: "default"
Arerano layout (XMLs) -> works with skin group: "default"
Tuathanach layout (XMLs) -> works with skin group: "TuatanachSkin"*

*works with can also be taken as "requires"
*name it as you wish.

Or maybe the other way around:
skin X NEEDS the Y-compatible XMLs

Y can be "default" or some "custom name".
the XMLs name could even have some version number included which can be bumped in case the XMLs change in a way which would lead to bugs with "old/incompatible XMLs", then refuse loading them.

I am tired.... hope I expressed it well enought

[Caarrie]

this seems smiliar to http://www.hydlaaplaza.com/smf/index.php?topic=26917 but for gui not chars

[Arerano]

this seems smiliar to http://www.hydlaaplaza.com/smf/index.php?topic=26917 but for gui not chars

Not really, Tuathanach's idea was to "include XMLs" in the zip file which contains the skin.
My idea takes it a step further to "configurable skin" and "configurable layout" of which each skin defines which kind of layout (or layout group) it works with.

That other thing is simply overriding what is already there.

Indeed, some overriding-logic as of "what's taken from where, and if it isn't in the zip, take the original thing" would make things easier, but the key point - as I understood it, is "having user XMLs together with the skin".
Concerning the "overriding", one could also define in the XMLs on which the own set is based, or rather a "fallback" set. (one that has to be used for missing files.)