BlueMCE2-X cleanup project

[McBainUK]

What shall we do about the TitleLogos?

Are they needed?

[MixMan]

Are they needed?

Optional for a plugin designers as many of the other images.
For plugin skins, mostly Not and Yes for some plugins with BlueMCE2 and ThemePacks
For Core skins, Yes - All BlueMCE2 and the ThemePacks uses TitleLogos

[MixMan]

Look at the first 3 posts. I have edited them much.....and added more status and suggestions.

[Fatman_do]

Optional for a plugin designers as many of the other images.
For plugin skins, mostly Not and Yes for some plugins with BlueMCE2 and ThemePacks
For Core skins, Yes - All BlueMCE2 and the ThemePacks uses TitleLogos

If this is dealing with the MCE2 skin and Themepacks specifically, yes they are needed. Other than that, it is not required.

If this is part of an image library, as an optional skinning tool like all the other images, that is fine.

It can even be renamed to ".....BannerImage.png" to reflect themepack usage descriptions (I don't think of those as "Logos").

Instead of ..\resources\ , I think ..\images sounds better.

[MixMan]

I agee with you Fatman_do
Perhaps Banner_xxxx would be better name......or ScreenNameImage_xxxx
Original BlueMCE2 used xxxx_logo. I guessed thats why I added Title to have a better description.

Tipstir uses ..\images for storing images, so I guess he would oppose to this name.
Dottore uses ..\res for storing images.

Wonder what their view on standardising image names is ?
I guess they will choose their own way.

But is guess this whole thing will make it easier for future graphical designers.
The current skinners will modify skins and add things, just like you and I do.

[dottore]

i use a mishmash between plugin image naming (my series images) and my own naming with a clear name and variations after a "_", i.e. "arrow_up.png". i use "_res" for storing images, not "res". this is because folders starting with "_" are listed first in windows explorer, which makes it easier to find them. "resources" is too long, too much to type when skinning something.

i am against title images/logos. they cannot be translated.

[McBainUK]

use "_res" for storing images, not "res". this is because folders starting with "_" are listed first in windows explorer, which makes it easier to find them. "resources" is too long, too much to type when skinning something.

i am against title images/logos. they cannot be translated.

agree with all of this

[Fatman_do]

i use a mishmash between plugin image naming (my series images) and my own naming with a clear name and variations after a "_", i.e. "arrow_up.png". i use "_res" for storing images, not "res". this is because folders starting with "_" are listed first in windows explorer, which makes it easier to find them. "resources" is too long, too much to type when skinning something.

i am against title images/logos. they cannot be translated.

I use "_DirectoryName" on my computers for that same reason.

[Fatman_do]

Tipstir uses ..\images for storing images, so I guess he would oppose to this name.

Images just sounds more natural, why would someone oppose using a similar name? It is not like that is unique and creative.

Use Dottore's method then and use "..\_Images\" or even "..\_img\"

I would still put all GUI images in the skin root, with all the "helper" icons in that shared directory. (I think this is in line with what MixMan's latest proposal is)

McBainUK's Name sequence is:
[size] item [state]

MixMan's latest is
item_(undefined)
BaseSkin uses several combinations.

I like the underscore, with size last. (easier to read a long list)

So how about a combination of both methods, arranged differently.
[item]_state[size]

Button_Normal.png
Button_NormalSmall.png
Button_NormalSquare.png
Button_NormalWide.png
Button_Selected.png
Button_SelectedSmall.png
Button_SelectedSquare.png
Button_SelectedWide.png
Popup_Background.png
Popup_BackgroundLarge.png
Popup_BackgroundSmall.png

ect.

You could even trim off the word "Background" from the popups to save typing, because Popup.png, Popup_Large.png, and Popup_Small.png should be enough.

[MixMan]

Images just sounds more natural, why would someone oppose using a similar name? It is not like that is unique and creative.

Use Dottore's method then and use "..\_Images\" or even "..\_img\"

I would still put all GUI images in the skin root, with all the "helper" icons in that shared directory. (I think this is in line with what MixMan's latest proposal is)

McBainUK's Name sequence is:
[size] item [state]

MixMan's latest is
item_(undefined)
BaseSkin uses several combinations.

I like the underscore, with size last. (easier to read a long list)

So how about a combination of both methods, arranged differently.
[item]_state[size]

Button_Normal.png
Button_NormalSmall.png
Button_NormalSquare.png
Button_NormalWide.png
Button_Selected.png
Button_SelectedSmall.png
Button_SelectedSquare.png
Button_SelectedWide.png
Popup_Background.png
Popup_BackgroundLarge.png
Popup_BackgroundSmall.png

ect.

You could even trim off the word "Background" from the popups to save typing, because Popup.png, Popup_Large.png, and Popup_Small.png should be enough.

Very good suggestions Fatman_do

I use diretories starting with All...something so they will be in the top of directory structure.
The same reason as you named yours _....something

TitleLogos in the ThemePacks are used for a "top bar" with a graphical design element. In Mayhem3 the TitleLogo is an image with a submenu specific image.
It is only n BlueMCE2 it is text in the TitleLogo image. So I think we can see this as a port of the original design.
ContourHC has a graphical "top bar" similar to the "TitleLogo" element.

It is only Dottores Sassari that do not use "top bars"

So the TitleLogo graphic element have a wider use in skin designs than you think.