Common Images Plugins Skins & Community Skin Project

[McBainUK]

The other idea is to center the arrow image in the 40x20 area instead of crowded to one side

If you took it to 30x30, and had the image centered it would allow for any "arrow design". Should the xmls really be changing the look of a standard image just because it would make an arrow look flat? What if it was a curvey 'funky' arrow?

Remember this:

You have to approach it as not having any idea what the graphics look like.

With a 30x30 image and a choice of arrows (wide, tall, big small etc), the user can choose one they like and the xml would draw it correctly on screen. If the xml's allow for a 30x30 image then layout wont be affected.

The 2nd arrow could be a thin vertical -> like arrow but it would still "fit" in the xmls.

[Fatman_do]

30x30 or 40x30?

The second allows a more squat design.

Let me make some test images.

[Fatman_do]

Here are replacement images. We do need to design for the entire zone (like we do for Background_List).

This is what we should be using for 40x20 or 40x30 or 30x30.

[ATTACHMENT NOT FOUND]

[ATTACHMENT NOT FOUND]

[ATTACHMENT NOT FOUND]

[McBainUK]

What meant was. Make it possible to create a "Theme" from a CommonImage file set. So users could make their Image selections and then make a "Save Theme" without renaming the directory _CommonImages.
Sounds like a lot of work....but I think end users would like it.

Hmm. Have you looked at a theme xml file? They are made up of a list of skinItems with pointers to the file or folder to use as the image for that item

skinItemName="BackgroundEditableSkinItem" type="SingleImage"
image="%IMAGESETDIR%\Backgrounds\Blue.jpg"
/>

To 'save' a theme you have two options:
1. Create a theme xml file with pointers to the images currently in use. - this isnt possible because you don't know the orginal location (Skin/SkinPlugin/...) of the current background.jpg file in the _CommonImages folder.

2. The only way is to have a MyThemes folder which contains sub folders for each saved theme. In the sub folder names 'McBainUK theme 1', for example, all the images currently in the _CommonImages folder would be copied out to this folder. On 'theme load' the images would be copied back in to _CommonImages.

Problem with this is you would have duplicate images, which is what I have been trying to avoid with use of a shared PluginSkin folder and theme file pointers. Although code wise, it could be done quite easily.

----------------------------
I think it should be left for now tho, see if there are any problems with the system before moving on to advanced featrures like personal theme save/load. For now a user could, if the wanted to, make a theme xml file themselves by editing an example one.

[McBainUK]

Here are replacement images. We do need to design for the entire zone (like we do for Background_List).

This is what we should be using for 40x20 or 40x30 or 30x30.

My vote is for 30x30. As it allows for flexability regarding types of arrows. The extra 10px in the y direction would allow for an arrow with a 'tail' eg ->

[MixMan]

If you took it to 30x30, and had the image centered it would allow for any "arrow design". Should the xmls really be changing the look of a standard image just because it would make an arrow look flat? What if it was a curvey 'funky' arrow?

Remember this:
With a 30x30 image and a choice of arrows (wide, tall, big small etc), the user can choose one they like and the xml would draw it correctly on screen. If the xml's allow for a 30x30 image then layout wont be affected.

The 2nd arrow could be a thin vertical -> like arrow but it would still "fit" in the xmls.

This is what I meant. It is the most flexible design to use a sqare eg 30x30 in the XMLs and change the graphics for different looks. It is more flexible when applying themes to the XMLs.
Not difficult to understand is it?

[MixMan]

Hmm. Have you looked at a theme xml file? They are made up of a list of skinItems with pointers to the file or folder to use as the image for that item



To 'save' a theme you have two options:
1. Create a theme xml file with pointers to the images currently in use. - this isnt possible because you don't know the orginal location (Skin/SkinPlugin/...) of the current background.jpg file in the _CommonImages folder.

2. The only way is to have a MyThemes folder which contains sub folders for each saved theme. In the sub folder names 'McBainUK theme 1', for example, all the images currently in the _CommonImages folder would be copied out to this folder. On 'theme load' the images would be copied back in to _CommonImages.

Problem with this is you would have duplicate images, which is what I have been trying to avoid with use of a shared PluginSkin folder and theme file pointers. Although code wise, it could be done quite easily.

----------------------------
I think it should be left for now tho, see if there are any problems with the system before moving on to advanced featrures like personal theme save/load. For now a user could, if the wanted to, make a theme xml file themselves by editing an example one.

Yepp, I have seen how the Themes work and I understand.
I agree, leave it as it is. Users can post their _CommonImage files ....as a Theme.

Thanks again for a great plugin.

[Fatman_do]

This is what I meant. It is the most flexible design to use a sqare eg 30x30 in the XMLs and change the graphics for different looks. It is more flexible when applying themes to the XMLs.
Not difficult to understand is it?

Ok 30x30 it is. It is not difficult to understand, the only problem I had was with the source image itself being too limiting.

[MixMan]

Ok 30x30 it is. It is not difficult to understand, the only problem I had was with the source image itself being too limiting.

Very good, this will allow serveral grapical designs.

FYI
I have reskinned the BaseSkin to 1024x768.
But I am disappointed, because using listviews is very slow, but the sharpness of the text makes a huge difference on my monitor.
I found several hardcoded stuff in Search, Recordings and TVguide.
I notified Sub about the findings, so he can implement changes in the future.
So I will not release the BaseSkin HD in the near future. :-(

[Fatman_do]

I updated the arrows.

30x30 white
30x30 white with red background (developer version)

What I also did is create two themes to use the SkinPlugin for developing.

Use the Develop theme for layout, then use the MCE2 Theme for screen shots.

The Develop theme uses the Developer_Background_List, Developer More_Up...., and a Developer Title_Bar (new which is faded blue with red stripe.).

[ATTACHMENT NOT FOUND]