Couple of Color Themes for Project Mayhem III, Red & Blue

Or we define a default include file that skinners can use

ThemeDefault.xml

and override with:

Theme<name>.xml

That way all the default stuff is in ThemeDefault.xml, and anything in there is overridden by the new theme. XBMC therefore just checks for the other theme override whenever it sees ThemeDefault.xml

Cheers,
Jonathan

hello,

the screenshots look really nice! going straight foward to do a test....

cu lolol

Cheers Jezz! Going to try that out now

@jm - Sounds great, I'm assuming that would mean we could override any xml files defined in a skin?

No. It would override the *single* xml file ThemeDefault.xml

This ofcourse could be included anywhere you like, so you technically could change practically anything.

Its not a new skin at all. The code would lookup /Red/Pal/Mypics.xml if it cant find it, it would then use /Pal/Mypics.xml (for every file it would first try the Red folder if the file doesnt exist it would drop back to default folders). So you just create a folder with the same name as the the xpr and use the same folder structure for every file you wish to replace all others would fall back to the default. This doesnt kill compatibility of any skin and makes it easy to patch in themes. It also means that if you select a theme called /NoGames.xpr you could add a folder NoGames and remove all the links to my games from any or all xmls. It allows for much larger themes than just colors and means you can totally rearrange the skin for an HD theme or an In car small LCD screen theme. If you wanted to change the colors under the old way you just make Red.xpr and a a folder caled Red, and in Red/Pal/include.xml change the colors

Forgive me if I sound foolish... but can I get a list of the images that are contained in a theme currently? I'd like to produce a couple (or give the attempt) but I'd like to make certain I use all the images needed and only those needed.

Never the mind.. I just extracted them all

jmarshall Wrote:Or we define a default include file that skinners can use

ThemeDefault.xml

and override with:

Theme<name>.xml

That way all the default stuff is in ThemeDefault.xml, and anything in there is overridden by the new theme. XBMC therefore just checks for the other theme override whenever it sees ThemeDefault.xml

Cheers,
Jonathan

Yeah that has alot better performance.

BritneysPAIRS Wrote:Its not a new skin at all. The code would lookup /Red/Pal/Mypics.xml if it cant find it, it would then use /Pal/Mypics.xml (for every file it would first try the Red folder if the file doesnt exist it would drop back to default folders). .... It allows for much larger themes than just colors and means you can totally rearrange the skin for an HD theme or an In car small LCD screen theme. If you wanted to change the colors under the old way you just make Red.xpr and a a folder caled Red, and in Red/Pal/include.xml change the colors

Actually what you are suggesting I guess is like a 'diff' for a skin that will use either the theme version or the default version. The problem I see with this is that I am worried it would be annoying to maintain the themes as the main skin changes. Just changing an include seems more in line with what a "theme" should be.

jmarshall Wrote:No. It would override the *single* xml file ThemeDefault.xml

This ofcourse could be included anywhere you like, so you technically could change practically anything.

Okay, I've just had a read through the wiki, sounds like a good idea

I disagree cause you can change the include if you want only anyway. But use it for nearly any purpose you can think of theme wise.