CommunitySkin 4 Open development thread.

[McBainUK]

Add new selector images for popup box lists.

What is the reasoning/history for this? I assume you mean something like "Popup_List_Selected_Popup.png" ?

[Fatman_do]

Question for Fatman_do:

"Would the move to 16x9 HD require two different xml layouts for the CS? I thought the move to a percentages layout (rather than pixel) would possibly negate that?"

Really, for a majority of the menu's it is fine as is. I am thinking of special cases where Reven has asked for an extra column on some of the library screens.

[Fatman_do]

What is the reasoning/history for this? I assume you mean something like "Popup_List_Selected_Popup.png" ?

Some popups have lists elements to them. Ted the Penguin requested (as this is what sassari does).

[Hairy]

Since this is the place for ideas.

Maybe a re gig of the plugin layout. I was thinking of a single page layout, something like the default search guide plugin. A menu breadcrumb idea where each selection loads another. When you load the plugin page there are 4 main buttons, selecting one of those then loads another selection and so on.

• Load Theme
  
• Edit Theme
  
• Save Theme
  
• Main Menu

Theme series could be grouped by name with variations as a sub selection. Edit theme could be broken down into:

• Layout

[INDENT][INDENT]Theme Layout
Mainmenu Layout
TV Guide layout
Fonts[/INDENT][/INDENT]

• Graphics

[INDENT][INDENT]all the various graphics grouped by folder[/INDENT][/INDENT]

A description might be useful to describe each option and explain that certain main menu layout require certain main menu masks for example. Also maybe the preview images maintaining aspect ratio: so 4:3 for Sd and 16:9 for HD.

I've attached a crude mock up to give the idea.

What do people think?

[Hairy]

The other thing I was thinking about was, if the CS and plugin are combined into one installer.

Would it make sense to include the plugin, SD/HD default graphics and just the bare bones of CS files (just those files not dynamically changed by the plugin). Then on install the user is asked whether they use a HD or SD display, this then triggers the script that the plugin uses to copy over the relevant files into the CS folder.

It could cut down the size of the package considerably.

[steeb]

This is where gbpvr users interested in participating with the development of the next version should post ideas, changes, comments, ect.

Interesting isn't it that this is how the thread begins, but no one except the Devs appear to be talking to each other. Why? As I think the Comm 3 skin is brilliant.

I'm an end user, no Dev skills but user end skills are well honed.....

I know what I'd like to see from the next release of the Comm skin but am interested to see who else is :p

Steeb

[Fatman_do]

I'm an end user, no Dev skills but user end skills are well honed.....

I know what I'd like to see from the next release of the Comm skin but am interested to see who else is :p

Steeb

And that would be......?

[Fatman_do]

Oh, and nothing really will get started until after the next gbpvr release.

[steeb]

Fair doo's,

I think we're all waiting on latest release, but I'd always thought the Dev's had some pre-knowledge of what changes may be had.

I saw a post from Sub today that said latest release contained nothing special.

For me what I would love to see is Comm skin and Skin Plugin contained in 1 download as a bundle.

Cheers

Steeb

[Fatman_do]

Fair doo's,

I think we're all waiting on latest release, but I'd always thought the Dev's had some pre-knowledge of what changes may be had.

I saw a post from Sub today that said latest release contained nothing special.

For me what I would love to see is Comm skin and Skin Plugin contained in 1 download as a bundle.

Cheers

Steeb

We cannot discuss pre-release changes to the public, so sorry no insight here. I am going to work on bundling the two together and breaking out the themes. Maybe see something on this next week. I am also posting an incremental update once I update the wiki.