[DEV] XML layouts for CS-SD + CS-HD

[Hairy]

Fatman_do,

Just tinkering around the skin and have found some of the popup xmls reference: "PopupList_Normal/Selected" graphics, are these new. I can't remember doing graphics for these before and I don't think I've any done for CS Blue, also there's nothing in the ..Resources\Graphics" folder or skin plugin.

Should we add PopupList_Normal/Selected graphics or alter the reference in the xml's

edit: or alternatively we could referenced them as List_Normal_Inactive_Selected.png in the baseskin.xml ???

I've also referenced these (in the baseskin.xml) to the detail pngs, so that they change with user selection.

[Hairy]

Fatman_do

Could I just clarify the above please.

Are there any objections to referencing the PopupList graphics in the Baseskin.xml to existing graphics (my preference would be the Detail png's, as they appear the closest fit size wise), rather than duplicating the graphics in the resource folder.

cheers

[Fatman_do]

The reason for the difference was due to a request for a skin theme based on sassari skin that used a different colour in popups than regular screens.

We can compensate for that then by issuing a specific baseskin.xml file that uses a different graphic that is downloaded with that specific theme.

That may be the more efficient way to go, for a one-off unique theme.

[Hairy]

The reason for the difference was due to a request for a skin theme based on sassari skin that used a different colour in popups than regular screens.

We can compensate for that then by issuing a specific baseskin.xml file that uses a different graphic that is downloaded with that specific theme.

That may be the more efficient way to go, for a one-off unique theme.

Sorry fatman_do, you have definitely explain that to me before, maybe even more than once :o. This thing is a beast, it's hard to keep track of everything.

Correct me if I'm wrong here, but if we leave the reference to the PopupList graphics in the SkinPluginConfig and the baseskin. Then future theme developers, who'd like to make use of the feature, can include those graphics in the resource folder and reference them in the baseskin.

And since we're not with CS Blue, I can remove the graphics from the resource folder and reference them to the existing detail graphics in the baseskin.

[Fatman_do]

You are correct Hairy.

[Fatman_do]

Do you guys think we need to identify the plugin HD resources so they and SD images, ect don't overwrite each other on a "mixed" install. (HD main display with SD clients).

Example:
Background\
CS-Blue
CS-Blue_HD

[McBainUK]

"mixed" install. (HD main display with SD clients)

I've been considering this...

If it was mixed it would mean you could create a theme with HD and SD parts...is this really what we want? Thinking about what Hairy said in another thread it would mean a mismatch of 4:3 and 16:9 images and layouts which I think might be a bit messy. We already have the concept of "shared" which we control.

If we put the split higher up like this:
...\Plugins\SkinPlugin4\Resources\ - CommunitySkin4-SD
...\Plugins\SkinPlugin4\ResourcesHD\ - CommunitySkin4-HD

and then added a bit of logic in the SkinPlugin to use a particluar resouces folder based on the active skin, it would mean you would only see (for example) SD options from an MVP running CommunitySkin4-SD and as you're running CommunitySkin4-HD on your 50 foot screen in the main room :p, you would see only HD options.

Thoughts?

[Hairy]

it would mean a mismatch of 4:3 and 16:9 images and layouts which I think might be a bit messy.

Agreed, ideally we'd really want to keep them (especially the layout stuff) separate.

If we put the split higher up like this:
...\Plugins\SkinPlugin4\Resources\ - CommunitySkin4-SD
...\Plugins\SkinPlugin4\ResourcesHD\ - CommunitySkin4-HD

and then added a bit of logic in the SkinPlugin to use a particluar resouces folder based on the active skin, it would mean you would only see (for example) SD options from an MVP running CommunitySkin4-SD and as you're running CommunitySkin4-HD on your 50 foot screen in the main room :p, you would see only HD options.

If we could do this, then I think that would be a fantastic way to go.

It's funny I was just thinking that it would be really handy if I could run both versions in my dev machine, but couldn't see how to keep the plugin stuff separate. Both of you guys are way ahead, thinking about how it would benefit users. I would have got there eventually... I promise

[Fatman_do]

I've been considering this...

If it was mixed it would mean you could create a theme with HD and SD parts...is this really what we want? Thinking about what Hairy said in another thread it would mean a mismatch of 4:3 and 16:9 images and layouts which I think might be a bit messy. We already have the concept of "shared" which we control.

If we put the split higher up like this:
...\Plugins\SkinPlugin4\Resources\ - CommunitySkin4-SD
...\Plugins\SkinPlugin4\ResourcesHD\ - CommunitySkin4-HD

and then added a bit of logic in the SkinPlugin to use a particluar resouces folder based on the active skin, it would mean you would only see (for example) SD options from an MVP running CommunitySkin4-SD and as you're running CommunitySkin4-HD on your 50 foot screen in the main room :p, you would see only HD options.

Thoughts?

Sounds like a plan.

[McBainUK]

Great. Added to the list.