BlueMCE2-X cleanup project

[Fatman_do]

I just uploaded SystemStatus again with correct Image names and added the Close button. Fatman_Do had done som copy and pasting and had gotten wrong image names a wrong width on ListView_Normal.
"sloppy" changing of XML values.
Why don't we rename the previous skin.xml a keep a couple of versions in the ZIP so it is possible to see the changes?

That is odd, my version of the plugin had the close button. I did do a rush job of copy and pasting in there to complete adding of images where they were missing before I left for a few hours for son's practice. I should have reviewed it more before posting, sorry.

[Fatman_do]

You removed them, so they where not there.

Correct, they are a provisional button that is not used yet so they were removed from the images.

My suggestion as to keep both types.
Ask Reven and Psysic what they think about MoreUp and PageUp indicators, since it is their skins that will be affected. Otherwise thy might tweak them back. Then we missed the idea with this tread....to have the plugin developers do the skinning.

The whole point is NOT what do plugin authors want their up/down indicators to look like. They don't need to care. They would know they use More_Up.png for an indicator and ButtonPageUP_Selected.png for user inputs. That is what a naming standard is used for.

You are using ButtonPageUP_Selected.png because you want those "more_up" images to look different than the other "more_up" images used elswhere because that is what MCE2 did. That is a mis-application of an image naming standard.

[McBainUK]

They would know they use More_Up.png for an indicator and ButtonPageUP_Selected.png for user inputs. That is what a naming standard is used for.

You are using ButtonPageUP_Selected.png because you want those "more_up" images to look different than the other "more_up" images used elswhere because that is what MCE2 did. That is a mis-application of an image naming standard.

My proposal

• Put ButtonPageUP_Selected.png/ButtonPageDown_Selected.png back in the list of common images (might as well have them now, ready for use in the future).
  
• If the more up/down/left/right indicator icon is clickable then use ButtonPageUP/Down/Left/Right.
  
• If the item is not clickable use More_Up/Down/Left/Right.
  

[MixMan]

Correct, they are a provisional button that is not used yet so they were removed from the images.



The whole point is NOT what do plugin authors want their up/down indicators to look like. They don't need to care. They would know they use More_Up.png for an indicator and ButtonPageUP_Selected.png for user inputs. That is what a naming standard is used for.

You are using ButtonPageUP_Selected.png because you want those "more_up" images to look different than the other "more_up" images used elswhere because that is what MCE2 did. That is a mis-application of an image naming standard.

I use More_Up/Down in main menus, but I wouldn't use PageUp/Dow type buttons there. MoreUp/Down also exist in BlueMCE2, so why haven't skin designers used them. We shall not question or rule what type of design the skinners shall use, just make rules for nameing, otherwise the these buttons will appear anyway with names like arrow_rounded_nofocus, and then we are back to the situation where plugins skin are not portable with drag and drop..
The idea was to port BlueMCE2 plugins to a image compatible Conmon Image Set....so all XML designs/skins could benifit from a well defined naming standard.
You have done a great job Fatman_do with defining names and documenting this. But we also need names for possible upcoming or existing image designs that are used in skins. So we just shold decide the name and location for the PageUp/Down image type.

It would be great if Tipstir and plugin designers would start using CommonImage based skins. That is the goal for our work. I will sum up the intentions and benefits in the first post of this tread.

The community skin (core XMLs) is a Fatman_do skin design, and I think it is great that you are doing it. I would design those XMLs different, but I will touch them...those XMLs are your project.

[McBainUK]

The idea was to port BlueMCE2 plugins to a image compatible Conmon Image Set....so all XML designs/skins could benifit from a well defined naming standard.

So you want different skins (as in xml layout) to work off the common image names? If thats the case then the community skin is just one to start it off.

Although with multiple xml's it requires skinners to keep them up to date with the latest plugins / core screens...

[Fatman_do]

I use More_Up/Down in main menus, but I wouldn't use PageUp/Dow type buttons there. MoreUp/Down also exist in BlueMCE2, so why haven't skin designers used them.

I think you mean plugin designers instead of skin designers here?
If so, the answer is because there is no "standard" for MCE2. They just looked in the resources directory and said "That looks nice, I will use that here." That is why the green button is used in the same place with different names everywhere in the skin.

We shall not question or rule what type of design the skinners shall use, just make rules for nameing, otherwise the these buttons will appear anyway with names like arrow_rounded_nofocus, and then we are back to the situation where plugins skin are not portable with drag and drop..

Exactly why I am saying do not use ButtonPageUP_Selected as a substitiute for More_Up. It is like you are using "more_up2.png".

Pretend you don't know what any images look like. Would you use an image named ListView_Normal.png as a background for text because that is what was used in MCE2?
Weather plugin:

Code:

        <CompositeImage name="ExtendedForecast" size="540,480">
            <DrawImage filename="..\resources\icon_empty_nofocusl.png" loc="0,35" size="540,70"/>
            <DrawImage filename="..\resources\icon_empty_nofocusl.png" loc="0,195" size="540,70"/>
            <DrawImage filename="..\resources\icon_empty_nofocusl.png" loc="0,355" size="540,70"/>
            <DrawText text="@Title" loc="0,0" size="540,75" textStyle="Title" align="Center"/>
            <DrawText text="@UpdateTime" loc="0,430" size="540,35" textStyle="AsOf" align="Center"/>
        </CompositeImage>

The idea was to port BlueMCE2 plugins to a image compatible Conmon Image Set....so all XML designs/skins could benifit from a well defined naming standard.
You have done a great job Fatman_do with defining names and documenting this. But we also need names for possible upcoming or existing image designs that are used in skins. So we just shold decide the name and location for the PageUp/Down image type.

It would be great if Tipstir and plugin designers would start using CommonImage based skins. That is the goal for our work. I will sum up the intentions and benefits in the first post of this tread.

The community skin (core XMLs) is a Fatman_do skin design, and I think it is great that you are doing it. I would design those XMLs different, but I will touch them...those XMLs are your project.

Stop right there. This is NOT my skin. You can change whatever you wish. Anybody can change whatever they wish (ie Community). I think you are confusing my effort to use the correct name in the correct place as being the owner of this project. It is not a Fatman_do skin design. Never was, never will be.

Please do not take my position personally. I know why you want to use the button images there. I understand fully. I just fear that if this is a reference skin, it may be confusing as to why two different image names are used for the same thing, that is all.

[Fatman_do]

My proposal

• Put ButtonPageUP_Selected.png/ButtonPageDown_Selected.png back in the list of common images (might as well have them now, ready for use in the future).
  
• If the more up/down/left/right indicator icon is clickable then use ButtonPageUP/Down/Left/Right.
  
• If the item is not clickable use More_Up/Down/Left/Right.
  

That is all I was ever saying. That is what the point is of an image name standard.

[McBainUK]

That is all I was ever saying. That is what the point is of an image name standard.

I know, just wanted to put it in writing

Do you agree Mixman?

[MixMan]

That is all I was ever saying. That is what the point is of an image name standard.

OK I just thought that the plugins designers should have the same "freedom" to make a design with common images, as they have had with BlueMCE2.
We still haven't heard much from the plugin developers or Sub. It is their time to talk now. The "foundation" is laid.

[Fatman_do]

OK I just thought that the plugins designers should have the same "freedom" to make a design with common images, as they have had with BlueMCE2.
We still haven't heard much from the plugin developers or Sub. It is their time to talk now. The "foundation" is laid.

They always have the freedom to use whatever they want. This is just what they "should" use, regardless of what skin is used or what the images look like.