[DEV] Resources: OSD

[McBainUK]

(confused...)

What about the all the (strangely named) OSD buttons? It was my assumption that we would use these and then copy a subset (play, stop etc) to the _CoreImages folder on application.

What is the target filename/folder of the ControlIcons EditableSkinItem? What images, now, are in the Graphics\OSD folder?

[McBainUK]

If that's alright, am I right in thinking that we're feature/element complete for a beta test?

Is this going to be a closed or open beta? I think there are still a few things to do: http://gbpvr.com/pmwiki/pmwiki.php/Devel...ySkinTasks

Most importantly:
* Create CS_Blue theme file. [MCBAINUK, ALL]
* Create CS_Blue - Dark theme file. [MCBAINUK, ALL]
* The previews in some of the folders (eg Menu) need to be updated to reflect the default CS Blue theme. [MCBAINUK, ALL]
* Set current theme theme.xml and preview to the (to be created) CS Blue theme (Manually create CurrentTheme.xml file for CS Blue). [MCBAINUK, FATMANDO]

Mostly related to the preview system and that it enables users to apply changes and save custom themes.

[Hairy]

(confused...)

What about the all the (strangely named) OSD buttons? It was my assumption that we would use these and then copy a subset (play, stop etc) to the _CoreImages folder on application.

What is the target filename/folder of the ControlIcons EditableSkinItem? What images, now, are in the Graphics\OSD folder?

Sorry about that, I have an absolutely terrible habit of talking about things an assumed step ahead of where I really should be and this really is having a negative impact on these finer details. Genuinely I can appreciate that I'm now contributing to what must feel to you like a moving target :o

To try and clarify the control icons, as fatman_do has pointed out these are presently only really used in the OSD, (so aren't really high on the list). I've slipped into seeing them as possibly more useful. So my thinking (and assumption) was along the lines of a separate set of graphics ie as a separate selectable option, but with the same file naming structure as appears in the OSD folder. Their initial purpose is to be loaded into the OSD skin folder, for use there, but later the possibility of being re-named and copied to the _Coreimages skin folder if needed by plugins. The separation allows users to select one colour for the OSD and another for the control graphics that appear in that OSD eg the user might want a black OSD but prefer green control icons.

I've made up some colour variations of these control icons and have placed them in a "...Resources\Graphics\ControlIcons" folder, ready for commitment to the SVN. I have also worked up some more colour variations for selected items.

I can now see more clearly where you are coming from as relates to folder/file naming (and as a result I've tweaked the buttons folder/naming very slightly to accommodate the additional colours). I was focus on trying to keep the folder/file naming as close to how they're referenced in the skin (simple because it's easier for me while I develop) but I may have lost sight of user friendliness/acceptability.

I'll upload what I've got done this morning, for you to have a look.

[Hairy]

Is this going to be a closed or open beta? I think there are still a few things to do: http://gbpvr.com/pmwiki/pmwiki.php/Devel...ySkinTasks

Most importantly:
* Create CS_Blue theme file. [MCBAINUK, ALL]
* Create CS_Blue - Dark theme file. [MCBAINUK, ALL]
* The previews in some of the folders (eg Menu) need to be updated to reflect the default CS Blue theme. [MCBAINUK, ALL]
* Set current theme theme.xml and preview to the (to be created) CS Blue theme (Manually create CurrentTheme.xml file for CS Blue). [MCBAINUK, FATMANDO]

I think we'll be able to put together the theme.xmls handy enough when we lock down the resource folder. I think I'll be able to do the Cs_Blue/dark ones based on the xml you sent me.

I've purposely avoided adding any preview images, just in case Beta feedback means an aesthetically change and I'd have to do them all again. For me stuff like previews and info/descriptions are polish.

Open or closed? I've no idea.

[McBainUK]

I've purposely avoided adding any preview images, just in case Beta feedback means an aesthetically change and I'd have to do them all again. For me stuff like previews and info/descriptions are polish.

Fair point. CurrentTheme.xml is a must though.

[Hairy]

Based on how the resource folder now stands I've had a go at filling in the blanks for the graphics in the BACKUP CurrentTheme.xml you sent me. I hope I've done it right.

[McBainUK]

The separation allows users to select one colour for the OSD and another for the control graphics that appear in that OSD eg the user might want a black OSD but prefer green control icons.

This is the step I missed. Having them independent is fine with me.

I'll upload what I've got done this morning, for you to have a look.

Great.

Based on how the resource folder now stands I've had a go at filling in the blanks for the graphics in the BACKUP CurrentTheme.xml you sent me. I hope I've done it right.

Thanks, will take a look.

[McBainUK]

Based on how the resource folder now stands I've had a go at filling in the blanks for the graphics in the BACKUP CurrentTheme.xml you sent me. I hope I've done it right.

Could I ask you to help with the final 5 blanks?

Graphics.ControlIcons
Graphics.ScreenHeader
Graphics.NoCoverArt
Graphics.OSD
Layout.TVGuide

[Hairy]

Attached.

I didn't see a reference for controlicons but that would be:

• \Icon\Blue
  

In the zip is a duplicate xml with the three changes needed for the CS_Blue version of the theme:

• Background
  
• Background Mask
  
• PopBackground