BlueMCE2-X cleanup project

[Fatman_do]

Fatman_do was happy with having the Common Images in the skin root.

I don't think there is any objections to this.

No resources or other directory then? (it doesn't matter to me, I like skin root as "all in one", less typing, no directories to reference.)

Lets make this an "Action Item".

If anyone has objections, please speak up.

Even if we deviate from how MCE2 is structured, a simple themepack will make it look like it enough that developers may switch if they like that scheme and want the same look.

I will put forth any effort needed to move foward. I will probably retire Chameleon and move the PluginPack to be availible as variations (ie higher vis versions) to whatever community friendly project evolves from this.

If this requires me helping you update themepacks and other things to a new standard, that is not a problem. I really don't have time to keep up on Chameleon and I am more of a behind the scenes guy. I mean, really, if BaseSkin was 100% AM compatible, there really is no need for Chameleon.

[Fatman_do]

Just wait and try it.

'nuf said. Don't want to be a pest.

[dottore]

I don't think there is any objections to this.

you cannot put all those images in the skin root, it's quite too much for the user and for the skinner. you could even introduce more folders, like:

- _res\listview\ <- containing elements for listviews
- _res\iconview\ <- dito for icons
- _res\....
- ...
- _res\common\ <- icons, arrows and so on

just a thought. when you have skinned the my series, the base plugins and video archiver and some other plugins there are quite a lot of images, even if the plugins mainly use the same images.

[MixMan]

I think Dottore has a really good point here.
When I saw the MyMusics all images, I just shook my haed and said to myself....are thy all really needed.
But I can see GBPVR skinning engine evolve and allowing more things to be skinned, as it what happened the last release.
I will re-do the icon view in the BaseSkin to be more flexible, just changing images.....more like Dottore has done in Sassari.
So it is a good idea to re-skin MyMusic and at the same time renaming and "grouping" images....according to functionality.
So far I have had a look at Weather, News, Video Archive, MusicPlayer, MusicLibrary2 to get a feeling of what images they are using.

I suggest while re-sknning and renaming, we keep the images in a directory called "CommonImages" just to keep them away from the skin root and resources. I will be easy just to search and replace paths later. This means that I will put the Buttons composite images back in the plugin skins. It will be posssible to tag them out later.
I will do this work for the Blue Theme in the BlueMCE2-X skin, that I will post regulary.

I don't agree with McBainUKs suggestion using button_large, small.....then skins may end up like with the resources buttons, where plugin developers has used all 3 sizes for a regular menu button.

It contains Blue, Gold and Steel themes + mods for TitleText and NoListView-Buttons. DesignerGuide masks are also in one Theme.
Pretty good to experiment with since it has images borh in the skin root and the /resources.
Let a new naming standard emerge in the the temporary CommonImage directory.

But we need more BlueMCE2 skins for the rest of the plugins.

[Fatman_do]

you cannot put all those images in the skin root, it's quite too much for the user and for the skinner. you could even introduce more folders, like:

- _res\listview\ <- containing elements for listviews
- _res\iconview\ <- dito for icons
- _res\....
- ...
- _res\common\ <- icons, arrows and so on

just a thought. when you have skinned the my series, the base plugins and video archiver and some other plugins there are quite a lot of images, even if the plugins mainly use the same images.

If plugin-specific icons stayed in their home directory that is not a problem. (It is on MixMan's proposal list). If you move all those icons out, then yes, that is too many.

However, if there is a central place for them, then probably one folder for all the icons is all that is needed, whille keeping all the main screen images in the skin root. There looks like there would be less than 20 images in the skin root this way. Those images left in the skin root would be the primary ones changed to change the look of a skin.

[McBainUK]

plugin-specific icons

examples?

xml files to the new names

what new names? Looking up and down this thread and I couldnt see any decisions on names.

[Fatman_do]

I will re-do the icon view in the BaseSkin to be more flexible, just changing images.....more like Dottore has done in Sassari.

You want an image background, an image overlay, an image selector overlay. That isn't adding much.

I suggest while re-sknning and renaming, we keep the images in a directory called "CommonImages" just to keep them away from the skin root and resources. I will be easy just to search and replace paths later. This means that I will put the Buttons composite images back in the plugin skins. It will be posssible to tag them out later.

I don't see why you need to bother adding buttons back into the plugin skins. I took your download and did a global find-replace on the .xml files and changed all the MCE2 names in the xml files to the new names. Took less than 5 minutes. During that process I even had it change the directory path.
All the xml files are then cleaned up on image naming on what I have here.

[MixMan]

I have been copying images into the CommonImage directory and renaming them. So here is a suggestion of names with images grouped.
I changes the names that I used in the BaseSkin that made images not to be in order. Actually, most names are changed in this suggestion.

It just struck me, that some graphical designers uses transparency on the popups, so they might not be good to use as "info backgrounds". I guess thats why Jeff and Psysic have used other image names for info backgrounds.
Another ting came to mind. We shall have icon_overlay_selected.png and icon_overlay_normal.pngs so Sassari type icon view style can be implemented.

I can see that arrow_up and arrow_down shall be defined as buttons in a future. There has been many requests in the wishlist for Sub to implement page up/down button so GBPVR would work with touch sensitive screens.
Some day he will probably support this......I guess.

[McBainUK]

• Why Background.png AND Background.jpg? My vote is for Background.jpg only as a background should never be transparant
  
• I like the different folder icons.
  
• Whats the difference between List_ViewTransparent.PNG and List_ViewTransparentNormal.PNG ?
  
• I really don't like the name 'ListView' its very undescriptive.
  
• Have you thought about sizes of images? (width and height)
  
• Info backgrounds could be added to the list.
  

-------------------------------------

I don't agree with McBainUKs suggestion using button_large, small.....then skins may end up like with the resources buttons, where plugin developers has used all 3 sizes for a regular menu button.

Did you read the 'aims' section at the top of my proposal? All proposal draft decisions where made in releation to those aims rather then copy useful imges into a folder :p
Another aim behind the proposal was the idea of having an AM like feature that allows for "swapping" of images like AM does with buttons. I would like to expand this to all "sets". ie buttons, list icons, list backgrounds, backgrounds, icons. Obviously some sets would only require a few different types (eg icons). All these sets of images could then be mixed and matched. For example you could have contour blue buttons with transparant list backgrounds.

ps sorry if it sounds like I'm grumpy and hate everything I just think its best to be honest and give feedback / comments. Try to make them constructive

[Fatman_do]

examples?

The My series. It was a global statement on how those images are distributed with a plugin now. Not really relevant now, I like having one directory for all them like what we are trying to do.

what new names? Looking up and down this thread and I couldnt see any decisions on names.

Just playing around. Not anything "final". Mostly changing from MCE2 to a variation on yours and MixMan's.

I only takes me a minute to make a global change so it is no big deal.

In fact, I used \_icons as the directory. I just was stating how fast a change can be made. It took me about 10 minutes to change everything over.