BlueMCE2-X cleanup project

[McBainUK]

I think they shouldn't be buttons for now.

I agree. If I implement touch screen page up/down support I will most likely, (or copy subs way if it is different and I am able to), just make the more up and more down indicators clickable.

[Fatman_do]

For an even more "Transparent" looking ScreenName Text, try this line

<TextStyle name="ScreenName" color="#2562b0" typeFace="Arial" size="32" style="bold" />

I think it might match better for MCE2 themes. (when Title_Bars are shut down)

Use this as the title_bar.png file. It is a 5px stripe at the bottom that represents the "padding" in the image. It is less intrusive in the scheme.

[ATTACHMENT NOT FOUND]

[Fatman_do]

I did a "refresh" of just about everything on this wiki page.

Changes include:

Updated every plugin listed to latest agreement on button close and screen name location.

Changed Title_Bar.png to be less invasive for development purposes. It is now the image I added in the above post. (When final theme is released, that blue stripe will be removed.)

Baseskin.xml has now been updated to control the xml colors of TV Guide and Live Guide, with those plugins being modified to do the same.

Screen Name color has been modified to make look more "transparent" to the MCE2 background.

This is what it looks like so far...

[ATTACHMENT NOT FOUND]

Change a few images, and a different baseskin.xml file (I only changed screen name text here) and you have a whole new look. Image offset for list background is not "up to spec." in this screen shot.
[ATTACHMENT NOT FOUND]

The goals of all this work is to have these images work with many different image based skins, regardless of the xml layout and styles.

A new skin in the future could have the buttons on the right side of the screen and still be able to have either look and change graphics to suit the skinner or home user's needs.

[McBainUK]

I did a "refresh" of just about everything on this wiki page.

Nice work fatman, see you've been busy. Around 20 plugins left to skin - then comes the testing / tweaking...

[McBainUK]

Added IconView_Music.png and IconView_FolderMusic support to the Music Libary skin.

Uploaded, now rev 04.

[McBainUK]

Nice work guys. Churning out these skins pretty quick now...

[MixMan]

I agree. If I implement touch screen page up/down support I will most likely, (or copy subs way if it is different and I am able to), just make the more up and more down indicators clickable.

More_Up/Down are more indicators today.....in the TVguide.
Perhaps should keep them small as they are and move them into the TVguide skin directory.
Then let ButtonPage Up/Down be the new Up/Down buttons.
That is more consitent with the naming.

[Fatman_do]

More_Up/Down are more indicators today.....in the TVguide.
Perhaps should keep them small as they are and move them into the TVguide skin directory.
Then let ButtonPage Up/Down be the new Up/Down buttons.
That is more consitent with the naming.

When they become buttons instead of indicators, then they will be identified and used as ButtonPageUP..... buttons. That makes sense, and there will be a visible difference between them and regular, non-clickable indicators to avoid confusion.

As far as sizes go, they can be scaled to whatever size is needed by the plugin. Nothing has to be used as the size the image is. If these indicators are kept in the CommonImages folder, a consistant look among all screens is preserved. TV Guide can define it to be smaller, other plugins can define it to be larger.

[MixMan]

Shouldn't we make this visible on the Wiki and inform plugin developers and skinners about whats going on?
Skinning plugins might take off then.

[Fatman_do]

I didn't notice it wasn't visible from the normal wiki methods. We can change that.

(I always click on "what's new").

Most developers have been reading this thread, but there is nothing wrong with going more public.

I imagine some are just waiting for the new baseskin.xml mehtods used by the next version of 'blue', and letting us skinners mess with graphics standards.