CommunitySkin project next phase....?

[Fatman_do]

Judging by the tag lines in signatures, and posts, it appears this skin is has turned out well and many users use it daily.

I wish I had more time to put into it so the Widescreen version. I want to add support for all plugins that are capable of 1280x720 resolution, it just may take some time.

Sub mentioned there are significant changes coming up in the next release of 'Blue', and I am anxious for the test releases to see what new bits he has added.

Depending on the scope of changes, the CommunitySkin(s) may be best suited to follow more code examples in that version.

The current structure of the baseskin.xml files are somewhat bloated, and maybe there can be improvements.

The code talk is not really the user's concern, it is for those that help develop and support this skin.

What I am asking, however, is that users and developers that use this skin...

What do you like about it?
What do you hate?
What would you like to see added or removed?
Is an "all-in-one" install (like it is now) ideal?
Would you prefer a more "modular" install process where you have to download the specific plugin's skin file separately?
Wish there were more themes? (Help needed for this!)
What?
What?
What?

Keep in mind, some of the features of the skin are related to the SkinPlugin (developed by McBainUK). There are some items on the todo list for that plugin, but any additional comments are welcome here as well.

More technical talk about the nuts and bolts changes will be in the developer's threads, I just wanted to get an idea of what people really think about the skin.

[McBainUK]

Yes, I am also excited about the new GB-PVR release and the changes it will bring.

Would you prefer a more "modular" install process where you have to download the specific plug-in's skin file separately?

IMHO this would complicate things. If you want the latest version of a skin it would be ideal to just download one file and that's it. Also, if you want to try out a new plug-in you don't have to hunt for it's skin file cos you already have it!

some of the features of the skin are related to the SkinPlugin

The plan is too add a 'save theme' feature for the next round of CommunitySkin changes. As fatman_do said feel free to post anything about the skin or the SkinPlugin no matter how small (or big!).

McBainUK

[psycik]

One of my only concerns with the communityskin is that it adds a dependancy to my plugin (which generally I don't like).

But also it means that I have another level on synchronisation (as well as with subs api/skinning elements).

other than that i use if myself on my main gbpvr box (not on the mvp yet, and I couldn't be bothered increasing the fonts on all screens by a +3).

I not sure what the best method for updating is, whether i make changes to "my" communitySkin files, or whether i continue to update only the blue skin and get the communitySkin admins (fatman_do) to update the community for my plugins.

[Ted the Penguin]

I just want to say that I like what you are doing with the community skin, but I personally don't use it.

the reason for this is pretty logical. last summer I got an HDTV... and I didnt like how 720x480 skins looked when stretched to a higher resolution (1360x768) so I switched to Sassari. Then I wanted to change the look of Sassari (I like red :p), so I got involved with the development of that skin, etc. etc. so I now use sassari, because I helped to make it, and it looks pretty much exactly like I want it to.

cheers, and thanks for all the work on the community skin!

as for your question about a modular install. I dont think that is the best way to go, the skin files are not large, so there should be no problem with space, and most normal users dont look in the skins directory anyways, so it doesnt matter if there is alot of stuff there that they dont use.

[pz1]

Would you prefer a more "modular" install process where you have to download the specific plugin's skin file separately?

You could interpret modular install also as downloading one thing, but than have the option to only install what you like/need. I personally hate messy drives with a lot of stuff that I never use. So a modular install would be most welcome

[kayak4ever]

I like the flexibility of the community skin and the fact that you test it out so well that everything works as well as with Blue skin. I particularly like being able to add my own background picture.

I prefer an all-in-one download because it is less complicated for me.

[-Oz-]

I like Community Skin because it always works. It doesn't bother me that its an all in one install...

What i want: A way in config or somewhere easy to see which version I'm running so I know if I need to update.

I only have an SDTV so I don't seem to have any widescreen issues. HTPC2 is hooked to a widescreen and community skin works fine there.

Another reason to use it is all the plugins are skinned.

I've only used the skin plugin once but that one time it was nice to have.

[Carlito]

What i want: A way in config or somewhere easy to see which version I'm running so I know if I need to update.

You can look in the system screen and it will tell you which version you are using. At least it does in the widescreen edition, but i'm pretty sure the standard one does too.

[Fatman_do]

You can look in the system screen and it will tell you which version you are using. At least it does in the widescreen edition, but i'm pretty sure the standard one does too.

Yes it does.

[Fatman_do]

I don't have a problem with an all-in-one install method, just wondered if there was another way to go about it. It doesn't pose a problem maintaining the skin either way.

I will probably try out a "Custom" install option which allows you to pick and choose plugins for those that wish to limit disk footprint.