2010-09-17, 10:36
Has anyone ever brought up the idea of making the various elements of skins compatible with the addons.
Kind of like a mix & match selector for skins. So the Wrap view for one skin could be used in another.
I know that it's no possible right now because of the way skins are written, but could it be possible?
It would require skin elements to be more self sufficient, and more self contained, but I think it could lead to better skin development.
Currently to create a skin, one has to create a whole bunch of views, and seeing how this is done is our free time, great skin ideas don't always see the light of day. A few views are created, but the rest is never finished.
If skins were broken up into separate elements, we could add different view modes ideas from various skinners to suit our taste. I really like the homepage from one skin, but think the list view from another is better for me, currently, I have to take them both apart, merge them together, and create a "MOD" to get what I want. Having the various elements separated would allow me to simply choose my home screen, and then choose my list view, no hacking together interfaces.
Granted each element would become a little more complicated because of the need to add color/background settings, but most skins have a whole slew of options for each screen already.
The skin selector page in settings would be more complicated, ie. a home selector, a video file view selector, a music library view selector, but most could be set automatically by downloading the various skin addons.
I think it would speed up design advancements, and give the end user what they want, exactly how they want it. Whole complete skins could still be released, but users could swap in and out the various element they want.
Instead of having various skin folders (skin.night, skin.confluence) it would look for like this:
Just an idea. Anyone have any thoughts on it?
Kind of like a mix & match selector for skins. So the Wrap view for one skin could be used in another.
I know that it's no possible right now because of the way skins are written, but could it be possible?
It would require skin elements to be more self sufficient, and more self contained, but I think it could lead to better skin development.
Currently to create a skin, one has to create a whole bunch of views, and seeing how this is done is our free time, great skin ideas don't always see the light of day. A few views are created, but the rest is never finished.
If skins were broken up into separate elements, we could add different view modes ideas from various skinners to suit our taste. I really like the homepage from one skin, but think the list view from another is better for me, currently, I have to take them both apart, merge them together, and create a "MOD" to get what I want. Having the various elements separated would allow me to simply choose my home screen, and then choose my list view, no hacking together interfaces.
Granted each element would become a little more complicated because of the need to add color/background settings, but most skins have a whole slew of options for each screen already.
The skin selector page in settings would be more complicated, ie. a home selector, a video file view selector, a music library view selector, but most could be set automatically by downloading the various skin addons.
I think it would speed up design advancements, and give the end user what they want, exactly how they want it. Whole complete skins could still be released, but users could swap in and out the various element they want.
Instead of having various skin folders (skin.night, skin.confluence) it would look for like this:
Quote:-xbmcSkin elements could also choose to use a global setting from the appearance screen for things like font color if they wanted.
----skin
------home
---------alaska.xml
---------alaska.xpr
------video library
---------night.xml
---------night.xpr
------video filemode
---------aeon.xml
---------aeon.xpr
------keyboard
---------confluence.xml
---------confluence.xpr
------settings
---------confluence.xml
---------confluence.xpr
.......
Just an idea. Anyone have any thoughts on it?