[timdog82001]

thats probably a good point about the customization. I think its good to have a few custom options available in the stock skin, but we don´t want so many it clutters the code, slows down the skin (due to massive xml files), or complicates things for the end user. Those sorts of things are better suited for skin mods, where the user has a choice to include it or not. If we do end up thinking up a lot of good ideas for custom options, but they seem too many to include in the default skin, we could do something, like just have a couple of team supported mods you could download, either from the team website if we end up making one, or even just from the XBMC Black Market website, which is still young, as it currently only provides themes and sound packs, but will be hosting skin mods in the future. (http://blackmarket.ictcsc.net/). If we did take such a route, we would have to make sure it was done in a way where it would be where the mods would be fairly easy to update with the skin (perhaps the use of includes could facilitate this?), and also, I think it´s probably not something we´d want to even start until the skin was VERY near to its absolute final form. Anyway, I suppose if we did do something like that, we could just have like two versions of a mod perhaps, a light, and a fat version, or something like that...or perhaps even just one would be sufficent. I doubt we´d come be coming up with THAT many custom things that are worth putting in anyway. Anyway...if we wanted to find a way to include some respectable customization options without confusing new users or slowing down or cluttering the skin unnecesarily, it seems to me that this would be a good way to approach it.