[DEV] Resources: Layout folder

[Hairy]

I think I've got the guts of this done and I'd like to check format and naming.

3 Main plugins:

• I've updated the meta view xml's
  
• I've renamed "Slick" to "CS Blue - Slick" and included the list-background.png required. I'm proposing that the CSplugin loads this graphic from here. This then allows for future versions like Reflect - Slick and Glow - Slick each with their own specific list-background.png graphic.
  
• I've included the standard (multi view) XML in a folder called Standard - we could go with Standard View, Default or Default View something like that ???
  

MainMenu:

• I've added the 3 main vertical mainmenu layouts (left, center, right)
  
• I've been thinking with the Horizontal and slick views but I think there is a bug with how GB handles the Background Mask.png here. It loads it initially but when you return to the mainmenu form a plugin view it no longer loads. I was trying to use this graphic to create the same effect, since the plugin is already setup to load a Background Mask.png. These views aren't show stoppers for me personally, and if required we can easily borrow subs graphics and layout for slick until we get something worked out.
  

TVGuide

• Added the 5 different views previously discussed
  
• I haven't added any live-guide.xml formatting yet. How do you guys think we should add this?, as a separate choice or some kind of complimentary layout based on the actual TVGuide.xml chosen.
  

OSD:

• I wasn't exactly sure how to format this, here's how I presently have it. 2 sub folders - Internal Graphics and External Graphics. Internal Graphics folder has 2 files - Blue.xml and Black.xml and uses GB to generate the OSD graphics. External Graphics folder has 2 folders - Blue and Black, each contain the skin.xml and the 6 separate png's that make up the OSD (the plugin could then load the graphics based on the colour chosen)
  
• I have also made up a photoshop file for ControlIcons (this enables me to create various colour options). These are the transport controls that appear when you move the mouse in the OSD. They may also be useful to media plugins that may require transport controls. I don't really know what to suggest, implementation wise, but the option of multiple coloured control/transport icons is there.
  

Baseskin (layout?):

• I'm not sure what to call this folder - Layout, Main Layout, Global Layout, Master Layout ???
  
• I've added standard text (13/15pt) and large text (15/17pt)
  

Not directly related to this post, but to clarify. Anything that I've placed (in the graphics or layout folders) in a CS Blue folder is intended to be used specifically (but obviously not exclusively) for CS Blue. Anything else is intended to be theme independent. So any graphics or formatting not in a CS Blue folder are intended to also be used independently from CS Blue.

[Fatman_do]

Sounds good. I haven't had time at home lately to look at all the latest updates, will download latest and check everything out.

[McBainUK]

Is it possible to uploaded what you've got so we can see the folders and images, easier to get it in my head if I can read your post while looking at things.

I haven't added any live-guide.xml formatting yet. How do you guys think we should add this?, as a separate choice or some kind of complimentary layout based on the actual TVGuide.xml chosen.

I think these should be separate options as IMO they're two separate screens.

[Hairy]

Sure, files added to the code page.

[McBainUK]

I've been working my way through the new additions to the Resources folder and have some questions....

• I've been thinking with the Horizontal and slick views but I think there is a bug with how GB handles the Background Mask.png here. It loads it initially but when you return to the mainmenu form a plugin view it no longer loads. I was trying to use this graphic to create the same effect, since the plugin is already setup to load a Background Mask.png.
  

I've been manually copying and renaming the backgroundmask images and all seems well. What do you by it loads initially but not later?

3 Main plugins:

* I've renamed "Slick" to "CS Blue - Slick" and included the list-background.png required. I'm proposing that the CSplugin loads this graphic from here. This then allows for future versions like Reflect - Slick and Glow - Slick each with their own specific list-background.png graphic.
* I've included the standard (multi view) XML in a folder called Standard - we could go with Standard View, Default or Default View something like that ???

Fine with me.

Anything that I've placed (in the graphics or layout folders) in a CS Blue folder is intended to be used specifically (but obviously not exclusively) for CS Blue. Anything else is intended to be theme independent. So any graphics or formatting not in a CS Blue folder are intended to also be used independently from CS Blue.

Do you mean some options have extra files that are not referenced by the image/file tags in SkinPluginConfig.xml? If so these extra files will not currently be copied by the plugin.

[Hairy]

I've been manually copying and renaming the backgroundmask images and all seems well. What do you by it loads initially but not later?

For me it appears to be a quirk that effects the horizontal and slick menu layouts, you won't see it with what I uploaded because they are all Vertical menu's. But you can see the effect by changing:

Code:

from:
  <MenuType type="Centered2"/>

to:
  <MenuType type="Horizontal"/>

Slick introduced two new graphics for the menu folder:

1. background_overlay.png: gives a graduated filter effect to all GB screens+plugins
   
2. menu_backdrop.png: is a framing graphic for the menu
   

I was trying to reproduce the same effect of menu_backdrop.png via the Background Mask.png. I haven't messed with either views (horizontal+slick) enough to workout what I think is the best way to handle them. Both of the above new graphics may need to be introduced as a selectable option, but I just don't really know yet and I'm more than happy for either of you guys to take a look and make that call. I can make up any graphics deemed necessary.

Do you mean some options have extra files that are not referenced by the image/file tags in SkinPluginConfig.xml? If so these extra files will not currently be copied by the plugin.

I don't know the SkinPluginConfig.xml well enough to say. I was more trying to explain the rationale for the folder naming and layout. For example in the graphics folder:

• Background, BackgroungMask and popups are in CS Blue (or derivatives) folders, as they are intended to be used together to form the CS Blue theme.
  
• Task Images, buttons, selectors, text backgrounds, etc are in more generic folders as they are intended to be also used outside of CS Blue.
  

In the layout folder:

• Baseskin, slick views are in CS Blue folders
  
• TVGuides, meta views, Mainmenus are intended to be more generic.
  

It was my plan to adopt this method of naming folders for future themes. So if I create elements specifically for a theme they will go in a theme named folder, where as if I want to extend the more generic elements with further colours and/or styles they will be add to existing folders or generic descriptive named folders.

[McBainUK]

I don't know the SkinPluginConfig.xml well enough to say. I was more trying to explain the rationale for the folder naming and layout. For example in the graphics folder:

• Background, BackgroungMask and popups are in CS Blue (or derivatives) folders, as they are intended to be used together to form the CS Blue theme.
  
• Task Images, buttons, selectors, text backgrounds, etc are in more generic folders as they are intended to be also used outside of CS Blue.
  

In the layout folder:

• Baseskin, slick views are in CS Blue folders
  
• TVGuides, meta views, Mainmenus are intended to be more generic.
  

It was my plan to adopt this method of naming folders for future themes. So if I create elements specifically for a theme they will go in a theme named folder, where as if I want to extend the more generic elements with further colours and/or styles they will be add to existing folders or generic descriptive named folders.

No problem, a like the naming structure. I got the wrong end of the stick - hence the "it might not work!" post.

I'm working my way through the graphics and folders, making them SkinPlugin visible (adding entries to the SkinPluginConfig.xml file, adding info.xml and preview.jpg files where required). Expect a SVN commit in the next day or two.

[McBainUK]

OSD proposal: http://forums.nextpvr.com/showthread.php?p=324228

[McBainUK]

Baseskin (layout?):

• I'm not sure what to call this folder - Layout, Main Layout, Global Layout, Master Layout ???
  
• I've added standard text (13/15pt) and large text (15/17pt)

I'm not sure whether this kind of option (text size, colour etc) should be tied into a range of Theme specific XML files or moved to a Text category which directly edits the (whatever theme) baseskin.xml file.

Thoughts?

[Fatman_do]

My question based on this is, are the xmls different other than just text size and colour?
If there is no tweaking of the baseskin.xml file to accommodate the larger size, then it makes sense to be in the Text category.

I have been working on the installer, trying to crack the config running or not "nut" so I haven't spent as much time on the resources folder. Cleaned a few things up, but not much.