BlueMCE2-X cleanup project

[MixMan]

Common Image Plugin Skins Project
BlueMCE2 image naming is outdated in many ways.....and TitleLogos sizes don't match our needs. BlueMCE2 resource directory is full of images that are not used and plugin unique.

Defining a new Common Image Based Skin that will replace the BlueMCE2 Image Set, will benifit all Plugin Developers and Skin Designers. The plugin skin will be portable by drag and drop the plugin skin into the full skin. We ask all Plugin and Skin developers to help outwith creating the new plugin skins.

The work based on BlueMCE2 images is documented here:

Common Image Naming Definitions
http://gbpvr.com/pmwiki/pmwiki.php/Devel...munitySkin

Common Image based Skin Files
http://gbpvr.com/pmwiki/pmwiki.php/Devel...ySkinFiles

Common Image based Skin Plugin
http://gbpvr.com/pmwiki/pmwiki.php/Devel...SkinPlugin

------------------------------------------------------------------
Old initial text.

I will use this thread and first post to inform you what I a doing and the intentions.

Plugin developers and skinners have invested a lot of time in BlueMCE2 skins.
But it would be very easy to let BlueMCE2 plugin skins to tranform into a "default plugin skin" that could be supported by all skins, even a new image based core skin by Sub.

So what I am doing is.
Narrowing down the common images that are used for the plugins.
So far I have found 32 common images......but there will be more.....folder/icon related.
I will post a BlueMCE2 / BaseSkin image reference list later.
Copying and sometimes moving away plugin unique images from the /resources dir to plugin directory. This will make it easier to take a plugin and just drop in another skin.
BlueMCE2 have 3 different button sizes 165x32, 150x32 and 120x32. BlueMCE2 skinners have used all 3 as regular sub menu buttons. Inconsistent!

This will give us a bunch of images....that there is a need for. Later we can decide what to rename them to.
On the fly.....I am adjusting XML to make room for TitleLogos if it is possible in that plugin.
I am adding the Close / Home button in the upper right corner if possible.
I am adding the transparent overlay used for element positioning by skinners.
I am adding ButtonTextSelected if it is possible.

When doing this I'm thinking, why not having BaseSkins common images in the /resources dir instead. Dropping a graphical design ontop of an XML design would be easier.

I will post the BlueMCE2-X skin for plugin in developers to test with their plugins.
I would like to ave plugin developer/skinners to post BlueMCE2 skins for plugins that doesn't have a BlueMCE2 skin. I will include all post working XML design in the BlueMCE2-X skin.
Naming them "your name"_skin.xml in the plugin skin folder.

[MixMan]

I will use this post to inform my findings of what needs to be decided upon.


- Overscan padding needs to have a "standard" - 10 pixel
- Buttons X,Y positions and size needs to have a "standard". - 15,70
- Baseskin.xml CompositeImages, button image location (padding) - loc=0,X
- Minimum requried text styles in Baseskin.xml, that plugins must support.
- ScreenName X,Y position and X,Y size to allow different sizes. - loc 20,5 size=720,120
- TitleLogos X,Y position and size + top image padding for overscan needs to have a "standard" - loc=0,0 size=720x65 (padding in image)
- Images needs new names and a GuideLine doc so skinning will be consistent.
- New "standard" skin name for the "general" image based plugin skin

- Task image distribution "logic" when applying a skin/theme design?
- Font installation "standard" when applying a skin/theme design ontop of an XML design.
- Sound installation "standard", when applying a skin/theme ontop of an XML design.


Status for Plugin skins
OK=BlueMCE2 skin exist. MixMan mod=allow TitleLogo
? = Status not known

Jeff
Weather, OK (MixMan mod)
Video Archive, OK
Music Player, OK
ShowSearch, ?

Reven
MyMusic. ?
MyVideo, ?
MyPictures, ?
MyPrograms ?
MyMessenger ?
VidPhone ?

Jorm
XRecord, OK
Guide2J - XSearch, ?
Fastfind -XFind. ?
X DVD , ?
WebViewer ?

McBainUK
ThemesManager, OK
Calendar (MixMan mod)
Gmail. OK
UKCimenaListings, ?
Screen Saver Plugin, ?
VolumeOSD, ?

Psycik
MusicLibrary2, OK
SystemStatus, OK (MixMan mod)
Recordings2, ?

Other
Calculator, OK (MixMan mod)
News. OK
CD Player, OK (Mixman mod)
Stocks ?
Shutdown, OK (Mixman mod)
Caller ID
Appearance

Obsolete "buggy" plugins
Music Albums
Music Albums II
Disk Space

Latest Image Name proposal and documents from Mixman and McBainUK with facts/suggestions for skins can be found here:
http://hyperlinkx.com//pmwiki/uploads/CommonImages.zip

[MixMan]

I will use this post to sum up what is suggested and later "agreed" upon.
Note! that my own suggestion will mean "huge" changes to ThemePacks and BaseSkin

- Sub will have the last saying when it comes to naming images. (MixMan)
- New skin name for image based plugin skins, to avoid confusion with BlueMCE2 skin. (MixMan)
- Common images are stored in a new "CommonImage" folder. (MixMan)
- Common images are stored in the /resources folder. (MixMan)
- Plugin unique image are stored in the plugin skin directory. (MixMan)
- Plugin unique image are stored in the /resources folder. (Jeff)
- The "standard" image based skin MUST be maintaned by the plugin developer.

Image Names should be grouped eg (MixMan)
Background_xxxx
Button_xxxx
Popup_xxxx
ListView_xxxx
IconView_xxxx
TitleLogo_xxxx
Line_xxxx
TVguide_xxxx
Search_xxxx


Theme/SkinPack Directory Structure (MixMan)
+ -- Baseskin.xml
| Preview.jpg
| Readme.txt
| License.txt
|-- "CommonImages" (upcoming name)
|--TaskImages (distributed to "plugin name" as task.png)
|--"Main Menu"
|--"Panels"
|--"OSD"
|--Fonts (Distributed/Copy to %windir%/fonts)
|--Sounds (Distributed/copy to BleepBloop sounds)
|--"Backgrounds" (AM)
|--"ButtonSets" (AM)
|--"SkinEffects" (AM)
|--"Resources" (BlueMCE2 images)


Core Theme Images
These would be the "theme" images, that a skinner would modify to change the looks of a skin.

Background.jpg == Screen background. (Plugin)
Title_Bar.png == An banner image across all screens

Background_List.png == A background for list displays
Background_OSD.png == A background for OSD controls
Background_Popup.png == A background for popup displays
Background_PopupBig.png == A background for popup displays where size is closer to full screen
Background_PopupSmall.png == A background for popup displays where size is smaller than normal

Button_Close.png == A button for mouse support to close active menu
Button_Normal.png == A standard size button unselected
Button_Selected.png == A standard size button selected
ButtonSmall_Normal.png == A smaller size button unselected (typically for popups)
ButtonSmall_Selected.png == A smaller size button selected (typically for popups)

ListView_Folder.png == Small folder graphic used in listmode
ListView_Normal.png == A unselected item in a list
ListView_Selected.png == A selected item in a list
ListView_SelectedActive.png == A selected item in a list that does not have focus
ListViewDetail_Normal.png == A larger unselected item in a list
ListViewDetail_Selected.png == A larger selected item in a list
ListViewDetail_SelectedActive.png == A larger selected item in a list that does not have focus

IconView_Normal.png == A unselected item in a Icon list
IconView_Selected.png == A selected item in a Icon list
IconView_SelectedActive.png == A selected item in a Icon list that does not have focus
IconView_Folder.png == A folder icon used in Icon list displays
IconView_Music.png == A music icon used in Icon list displays
IconView_Photo.png == A photo icon used in Icon list displays
IconView_Video.png == A video icon used in Icon list displays

TVGuide_Grid6.png == A TV Guide grid with 6 channels
TVGuide_Grid7.png == A TV Guide grid with 7 channels

More_Down.png == A indicator (usually an arrow) for more selections
More_Left.png == A indicator (usually an arrow) for more selections
More_Right.png == A indicator (usually an arrow) for more selections
More_Up.png == A indicator (usually an arrow) for more selections

Plugin Theme Images
These would be the "utility" images. They can be modified by a skinner, but typically are not.

Background_Text.png == A background for misc. text displays
Background_TextNarrow.png == A background for misc. text displays where height is much greater than width
Background_TextWide.png == A background for misc. text displays where width is much greater than height

ButtonPageDown_Normal == Not used. Provision for possible touchscreen support
ButtonPageDown_Selected == Not used. Provision for possible touchscreen support
ButtonPageUp_Normal == Not used. Provision for possible touchscreen support
ButtonPageUp_Selected == Not used. Provision for possible touchscreen support

BulletBall_Blue.png == An indicator for compatible remote controls
BulletBall_Green.png == An indicator for compatible remote controls
BulletBall_Red.png == An indicator for compatible remote controls
BulletBall_Yellow.png == An indicator for compatible remote controls

IconView_DVD.png == A DVD icon used in Icon list displays
IconView_FolderMusic.png == A Folder icon used in Icon list displays
IconView_FolderParent.png == A parent directory icon used in Icon list displays
IconView_FolderPhoto.png == A Folder icon used in Icon list displays
IconView_FolderVideo.png == A Folder icon used in Icon list displays

Icon_NoCoverArt.png == A graphic where no cover art is present
Icon_Pause.png == A graphic to display a pause icon
Icon_Play.png == A graphic to display a play icon
Icon_Record.png == A graphic to display a record icon
Icon_Stop.png == A graphic to display a stop icon

ListView_FolderParent.png == Small folder graphic used in listmode

Line_Horizontal.png == A line image used as a separator
Line_Vertical.png == A line image used as a separator

Developer_Mask.png == A temporary background image to help with layout
Empty_Image.png == A blank image used to rename as an image you want no graphic for.

CommonImage Definitions
http://gbpvr.com/pmwiki/pmwiki.php/Devel...munitySkin

CommonImage Skin Files
http://gbpvr.com/pmwiki/pmwiki.php/Devel...ySkinFiles

BlueMCE2-X full skin
http://hyperlinkx.com/pmwiki/uploads/BlueMCE2-X.zip


Plugin unique images
Other images that are plugin unique should stay with the plugin folder.
This will make it easier to "drag and drop" plugin skins between skins.
(Maybe a plugin unique directory may be defined as well?)

TaskImages (MixMan)
Stored in TaskImage dir with "plugin skin dir name"_task.png.
Distributed to plugin skin dir as task.png

TitleLogos (MixMan Advisor skin AddOns)
Stored is CommonImages with group name (or plugin unique name)
TitleLogo_Television.png
TitleLogo_Music.png
TitleLogo_Photo.png
TitleLogo_Video.png
TitleLogo_Recordings.png
TitleLogo_Search.png
TitleLogo_System.png
TitleLogo_Weather.png
TitleLogo_News.png
TitleLogo_Program.png
TitleLogo_Internet.png
TitleLogo_Appearance.png
TitleLogo_Default.png (used in PM3 type skin where the is an image in the titlelogo)

[Jeff]

- Plugin unique image are stored in the plugin skin directory. (MixMan)

I think all images should be stored in the resource directory. That way plug-ins that want to can easily share images.

Jeff

[MixMan]

Thanks Jeff for yout comment/suggestion. It is noted in the post.

Regarding batch files. There is nothing special with the themepacks, the bach files just copy the files and directory contents in the ZIP/SFX.
If I was a programmer I would write a program that would read the GBPVR InstallDir from the registry and the "current" skin from the config.xml.
Then the ThemePack would unpack itself to a "temp" directory and te program would copy the directory content from there and install the fonts.

Perhaps one day we will see a universal plugin/theme/skin installer program that is really easy to use, just like zipping a file...or as I do it with WinRar.
Graphical designers really need something that is easy to use.

[Fatman_do]

Thanks Jeff for yout comment/suggestion. It is noted in the post.

Regarding batch files. There is nothing special with the themepacks, the bach files just copy the files and directory contents in the ZIP/SFX.
If I was a programmer I would write a program that would read the GBPVR InstallDir from the registry and the "current" skin from the config.xml.
Then the ThemePack would unpack itself to a "temp" directory and te program would copy the directory content from there and install the fonts.

Perhaps one day we will see a universal plugin/theme/skin installer program that is really easy to use, just like zipping a file...or as I do it with WinRar.
Graphical designers really need something that is easy to use.

Mixman,
I am looking into the reading the xml file with the nullsoft installer. I am close to getting something here. Once names are refined and nailed down, you should be able to re-use the same script over and over for different themes. After that, it is as simple as right clicking on the script file and selecting "compile script".

[Fatman_do]

Anything I can do to help? Our skins are joined at the hip.

I see alot of things that can be simplified, but this is xml textstyle related and menu layouts. Some of that effort may be wasted based on sub changes.

[McBainUK]

Some of that effort may be wasted based on sub changes.

This is true, and is the reason I've put my little skining project on hold.

Not a bad thing tho, can't wait to play with the new methods

[MixMan]

Anything I can do to help? Our skins are joined at the hip.

I see alot of things that can be simplified, but this is xml textstyle related and menu layouts. Some of that effort may be wasted based on sub changes.

You could help checking the common images list and see what more images should be defined in a documentation, that we would present to Sub.

Another thing that I dont have a clue about, is how much should be reserved for overscan......in border pixel "padding" for a 720x480 skin.

I think that the images that builds the icons in the icon views (Music, Photo Video) should be defined to be more flexible like MediaPortal or Sassari.
I will do that for the BaseSkin....some day.

I don't see that Subs new definition as that much impact on the plugin skins. Plugin developers have used their own text definitions in the skins an mostly used Arial as a font.
These text styles could be narrowed down and "grouped" in a later stage.

[Fatman_do]

You could help checking the common images list and see what more images should be defined in a documentation, that we would present to Sub.

Another thing that I dont have a clue about, is how much should be reserved for overscan......in border pixel "padding" for a 720x480 skin.

I think that the images that builds the icons in the icon views (Music, Photo Video) should be defined to be more flexible like MediaPortal or Sassari.
I will do that for the BaseSkin....some day.

I don't see that Subs new definition as that much impact on the plugin skins. Plugin developers have used their own text definitions in the skins an mostly used Arial as a font.
These text styles could be narrowed down and "grouped" in a later stage.

Overscan has been mentioned at 10%. My HTPC does not display with overscan, I adjusted it out of the video card so I do not know.

How images for icons are built can be left up to plugin author or skin creator. I just think a common name for selection and non-selection should be established. Backgrounds are more commonly used than a forground image. If a skinner wishes to do something different, that is up to them.

As far as textstyles are concerned, I think subs new definition method can go a long way with common styles pre-defined in the baseskin.xml.

Plugin specific textstlyes will always exsist, but some elements tend to be similarly sized (list text, list icon text, general description text.)

Plugins like Weather will hardly need common definitions, but I can see many others using it. Most of the standard font sizes in plugins are around 13pt. It doesn't seem like much maybe on a single plugin basis, but applied to an entire skin would make a dramatic impact. If "GeneralText" is one font style on one screen and another style on others, that makes a skin look less polished. Since "GeneralText" is usually 13pt, having it defined in baseskin.xml makes sense. Once sub's new method is introduced, a plugin can choose to use that same GeneralText font and color, but use its own size.

That is something that should be considered when cleaning up BlueMCE2.

Don't concern yourself too much, let me look into it.