Community skin project

[Old Dog]

The more I think on it, the more I feel that our desire to use Blue as the basis of our standard skin outweighs the overscan issue, especially since it is adjustable now.

So tentatively, I will assume that the answer is no, do not consider overscan in the standard skin.

[Old Dog]

Are you describing a system where the skin would have a set of xml files for the plugins plus an xml file for each of the main menu layouts? If so, AM could probably do this.

In a word, yes.

Let's kick it up a notch.
There could be many skin systems like the one you describe above, one for MVP, one for overscan, one for high contrast, etc. If we allowed the user to change skin systems, the user interface could get messy, which skin...,which main menu...

Should we include this feature, or exlude it because it's messy?

[daphatty]

Let's kick it up a notch.
There could be many skin systems like the one you describe above, one for MVP, one for overscan, one for high contrast, etc. If we allowed the user to change skin systems, the user interface could get messy, which skin...,which main menu...

Should we include this feature, or exlude it because it's messy?

The MVP can be configured to use a different skin in the Config app in case you didn't know.

[Old Dog]

The MVP can be configured to use a different skin in the Config app in case you didn't know.

Yes, and assuming your system is so configured, then when using Appearance Manager on an MVP, the skin for MVPs is modified, but not the skin for the PC/TV and vice-versa.

[MixMan]

I have been doing some test based on my proposal of a standard plugin skin...that will be compatible with all skins and all resolutions.
Success......I have gotten the plugin skins to work with Sassari.
I have sent Dottore a working sample of the "standard skin" proposal for him to review.

If you have read the proposal you have seen that:
Old Dog's ScreenEffect for AM is in the proposal
FatMan_do's Shadow Text is in the proposal
Mixman's ThemePacks s in the the proposal
4 resolutions 720x480, 1280x720, 1024x768 and 1366x768 is in the proposal.

Fatman_do....can't you please publish a zip with all your plugin skins? I would like to have a look at them and see how they work...and could be modified for a proposed standard....that will work as soon as possible.

How about starting to make buttons, listbars, listviews etc.....that Sub could use for a default image skin?

[Fatman_do]

I have been doing some test based on my proposal of a standard plugin skin...that will be compatible with all skins and all resolutions.
Success......I have gotten the plugin skins to work with Sassari.
I have sent Dottore a working sample of the "standard skin" proposal for him to review.

If you have read the proposal you have seen that:
Old Dog's ScreenEffect for AM is in the proposal
FatMan_do's Shadow Text is in the proposal
Mixman's ThemePacks s in the the proposal
4 resolutions 720x480, 1280x720, 1024x768 and 1366x768 is in the proposal.

Fatman_do....can't you please publish a zip with all your plugin skins? I would like to have a look at them and see how they work...and could be modified for a proposed standard....that will work as soon as possible.

How about starting to make buttons, listbars, listviews etc.....that Sub could use for a default image skin?

I will do so as one zip file. Background composite image wise, I followed BaseSkin but added se.png

I didn't include any image files only xml files to keep the size down.
[ATTACHMENT NOT FOUND]

[Old Dog]

I don't understand your proposal. It seems to focus on how to accomplish some specific goals, but I haven't a clue to what those goals are.

Please realize that if I had the experience with your how-to's that you have, I would probably realize the intent intuitively.

I am especially concerned about the references to batch files, executables, environmental variables, etc. I simply hope these are not things the end-user will need to contend with.

[Jeff]

I don't like the batch files and environmental variables either. I have a very hard time getting some of the base skin theme packs to install correctly. I think that all of the stuff that is done in those today could be done in Appearance Manager or some other plug-in. I think it would also be good to work with sub to see if more things can be skinned on the fly without the need to shut down and restart gbpvr. It would make the experience much more interactive and user friendly.

Jeff

[Fatman_do]

I don't like the batch files and environmental variables either. I have a very hard time getting some of the base skin theme packs to install correctly. I think that all of the stuff that is done in those today could be done in Appearance Manager or some other plug-in. I think it would also be good to work with sub to see if more things can be skinned on the fly without the need to shut down and restart gbpvr. It would make the experience much more interactive and user friendly.

Jeff

The batch files and environment variables are due to the fact neither Mixman or myself know anything about programming and this is a layman's hack.

A better process can be done. A plugin can read the config.xml file to find out what the current skin is or maybe some other internal method as well.

I wish I had kept up with coding (abandoned it at age 18 when wanted no more with learning COBOL back in '87).

[Old Dog]

The batch files and environment variables are due to the fact neither Mixman or myself know anything about programming and this is a layman's hack.

A better process can be done. A plugin can read the config.xml file to find out what the current skin is or maybe some other internal method as well.

I wish I had kept up with coding (abandoned it at age 18 when wanted no more with learning COBOL back in '87).

"A better process can be done" -- A better process that does what? What is the goal?