BlueMCE2-X cleanup project

[Fatman_do]

See what you think.

Changes I made:

• I noticed two files were .gif, I saved them in a GIF folder, and made .png copies.
  
• I copied "background_faded" and "panel_list_viewtran....." since those are unique to MCE2 into a MCE2-specific folder.
  
• Moved Panel_net_radio.png to "out" (provided panel_dialog.png works for it)
  
• Removed background.png, background.jpg is GBPVR standard.
  
• Renamed background_mask.png to developer_mask.png (seemed like a good idea?)
  
• Changed graphic for icon_file_photo.png from a film reel to a camera. (I know images are not "set" yet, but just made it look more photo related)
  
• Changed Button_MenuNormal.png, Button_MenuSelected.png to Button_Normal.png and Button_Selected.png (Just to save on typing, but it doesn't bother me if the word Menu is there.)
  

[ATTACHMENT NOT FOUND]

(I removed both proposal documents from this to reduce zip file size)

[MixMan]

See what you think.

Changes I made:

• I noticed two files were .gif, I saved them in a GIF folder, and made .png copies.
  
• I copied "background_faded" and "panel_list_viewtran....." since those are unique to MCE2 into a MCE2-specific folder.
  
• Moved Panel_net_radio.png to "out" (provided panel_dialog.png works for it)
  
• Removed background.png, background.jpg is GBPVR standard.
  
• Renamed background_mask.png to developer_mask.png (seemed like a good idea?)
  
• Changed graphic for icon_file_photo.png from a film reel to a camera. (I know images are not "set" yet, but just made it look more photo related)
  
• Changed Button_MenuNormal.png, Button_MenuSelected.png to Button_Normal.png and Button_Selected.png (Just to save on typing, but it doesn't bother me if the word Menu is there.)
  

[ATTACHMENT NOT FOUND]

(I removed both proposal documents from this to reduce zip file size)

Looks good man.

I named the botton_normal.png ---> Button_MenuNormal.png
so normal and selected menu buttons should be in group order.

I have another suggestion
Core images starts with capital letters and plugin used with normal letters eg

Popup_Dialog.png
panel_dialog.png

How about that.....then Sub will see our thinking directly.
I don't think he has any experience with image skinning...and see how we uses the images in our skins. I think his images based skin should support our basic functions....otherwise it is no meaning with all this, if plugin developers can't skin the basic functions they want. (BlueMCE2 lookalike)
The ListView padding can cause incompatibility with plugins and themes....as it did for you.
Things to consider even for Sub... I think......otherwise I will not use the new naming standard for images that causes "problems" with plugins.

Also the resolutions baseskin.xml vs the plugin resolution should be considered, when there is a possibility for it.
I will skip the 720x480 resolution, since it is to "blurry" on modern monitors.
720x480 is made for an oldfashion American TV-set, not for todays HD screens.
Lets take GBPVR GUI into todays technology.

[Fatman_do]

Looks good man.

I named the botton_normal.png ---> Button_MenuNormal.png
so normal and selected menu buttons should be in group order.

I have another suggestion
Core images starts with capital letters and plugin used with normal letters eg

Popup_Dialog.png
panel_dialog.png

Sure.

The ListView padding can cause incompatibility with plugins and themes....as it did for you.

Maybe reduce it to 5 pixels? or none?

......otherwise I will not use the new naming standard for images that causes "problems" with plugins.

I don't understand this part. Is this referring to the padding?

[Fatman_do]

Also the resolutions baseskin.xml vs the plugin resolution should be considered, when there is a possibility for it.
I will skip the 720x480 resolution, since it is to "blurry" on modern monitors.
720x480 is made for an oldfashion American TV-set, not for todays HD screens.
Lets take GBPVR GUI into todays technology.

The default should stay 720x480 if it takes less CPU to do so. If there is little difference, then it doesn't matter.

There can be Higher res "PluginPacks" maybe.

I know you are moving to 1024x768, but how about 1080x720? That is a perfect 1.5x1.5 scaling of 720x480, and is the same vertically as 1280x720 Wide Screen.
There may not be much benefit going the extra 48 pixels in the vertical.

Just a thought.

[MixMan]

The default should stay 720x480 if it takes less CPU to do so. If there is little difference, then it doesn't matter.

There can be Higher res "PluginPacks" maybe.

I know you are moving to 1024x768, but how about 1080x720? That is a perfect 1.5x1.5 scaling of 720x480, and is the same vertically as 1280x720 Wide Screen.
There may not be much benefit going the extra 48 pixels in the vertical.

Just a thought.

1366x768 have the same font size as 1024x784
I don't want to have font size problems with 4:3 and 16:9 versions.
How will a 720x480 plugin skins work with a 1024x768 core skin?
Font and button size problems if those defenitions are kept in the baseskin.xml.
Thats why I think the button definitions should be in the plugin skin but tagged out.
Untagging the buttons....and the plugin skin would work with a 1024x768 core skin.
This is what I did and sent an exapmle to Dottore. All current plugin skin would work with Sassari with minor changes in his baseskin.xml and the plugin skins.

Listviews with 5px border or less will give boring design opportunities.

I think we have come a long way....hope Sub and the oters understands all the benefits......I not so sure of that.

[MixMan]

Fatman_do
My goals with all this......for Sub to get an image based skin, so it would be possible to drop the most popular skin graphical designs images and main menu and then get almost the same look as they have.
I have shown that it is possible to make XMLs that works that way.
Then skin designing would would have more with artwork to do than XML editing. This is why GBPVR has so few skins and most of them are working so badly with both core functions and plugins.
GBPBR really sucks in that aspect, only Blue skin works......and how fun is with only one skin working....for this kind of software?

I will probably don't release BlueMCE2-X. It is to big (30Mb with AM buttons, steel and gold themes)
It will remain ThemePacks.
I will start on BaseSkin 1024x768 very soon. You can have the 720x480 XMLs if you want to.

[Fatman_do]

Fatman_do
My goals with all this......for Sub to get an image based skin, so it would be possible to drop the most popular skin graphical designs images and main menu and then get almost the same look as they have.
I have shown that it is possible to make XMLs that works that way.
Then skin designing would would have more with artwork to do than XML editing. This is why GBPVR has so few skins and most of them are working so badly with both core functions and plugins.
GBPBR really sucks in that aspect, only Blue skin works......and how fun is with only one skin working....for this kind of software?

I will probably don't release BlueMCE2-X. It is to big (30Mb with AM buttons, steel and gold themes)
It will remain ThemePacks.
I will start on BaseSkin 1024x768 very soon. You can have the 720x480 XMLs if you want to.

Ideally, "ThemePacks" are all that would be needed. To me, the xml's are the important part. After McBainUK gets back from the weekend and adds his input (BTW I appreciate a "developer" taking the time with this), I could change out MCE2 in a hour or less for a "phase 1 test run". Stripping out the themepacks and AM stuff as extra downloads.

Have you done any xml changes to the MCE2-x yet, or is it still how you last posted it on your site?

[MixMan]

No I haven't updated the BlueMCE2-X on the web.
I did a test with the music and the iconview with the BlueMCE2 images.
I will go an vacation for week now, so I hope that you guys have come to a conclusion that benefits all GBPVR users.
Jeffs and Revens input would also be very valuble.

I think the CommonImage pack you posted is good for a proposal.
When Sub has looked at our stuff and said what the thinks we can make a couple of "image packs" that he can use for testing with his skin, and see how it works with the sub menus.

[Fatman_do]

Listviews with 5px border or less will give boring design opportunities.

If you allow 5 pixels for a drop shadow, 5 pixels for a border of sorts, and start Selectors 20 pixels from "0" edge, that should be enough. Basically use your Listview developer image, and start the list selectors at the "blue" color, without padding.

That is something that can be played around with. Make separate plugin test downloads of a few select plugins to get the feel of it.

Enjoy your vacation...

[MixMan]

If you allow 5 pixels for a drop shadow, 5 pixels for a border of sorts, and start Selectors 20 pixels from "0" edge, that should be enough. Basically use your Listview developer image, and start the list selectors at the "blue" color, without padding.

That is something that can be played around with. Make separate plugin test downloads of a few select plugins to get the feel of it.

Enjoy your vacation...

Thanks man

The best way to start avacation....is to make a post.

The DesignerGuide that I use is made for 800x600 resolution so 20px in that is around 15px in a 720480 skin. At least 10px ListView padding should be allowed for graphical design.

Added an image to the Title_Bar. So there is an image shown when testing.
Added an Empty_Image.png......for those who don't understand that an image can be blank/empty/transparent....to use for replaceing an image that not wants to be seen.
Enclosed a Music Library2 skin for the CommonImage directory.
http://hyperlinkx.com/pmwiki/uploads/CommonImages.zip