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.
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.
Best Regards
MixMan
[SIZE="1"]
Antec Fusion case with Gigabyte GA-MA78GM-SH, AMD X2 4850e, 2GB RAM, AMD780G Onboard graphics. WinTV-PVR 150 MCE (With FM), Twinhan DVB-T, 750GB + 250GB HDD. Windows XP Pro SP3, MCE 2005 Remote, 29" 4:3 monitor and a 47" Philips 9603H LCD[/SIZE]
MixMan
[SIZE="1"]
Antec Fusion case with Gigabyte GA-MA78GM-SH, AMD X2 4850e, 2GB RAM, AMD780G Onboard graphics. WinTV-PVR 150 MCE (With FM), Twinhan DVB-T, 750GB + 250GB HDD. Windows XP Pro SP3, MCE 2005 Remote, 29" 4:3 monitor and a 47" Philips 9603H LCD[/SIZE]