Skin XML suggestion

[gruskada]

Sub,
I'm working with my WYSIWYG designer for SkinTools, and came up with something that I think may help both people who work with the XML files manually and my application.
Right now, there is no logical connection in between a composite image and a special element. For example, I can't tell just from looking at the skin.xml file in Main Menu, that this composite image:

Code:

<CompositeImage name="NormalButtonImage" size="166,45">    
    ...            
</CompositeImage>

is related to the "Buttons" Special Element:

Code:

<SpecialElement name="Buttons" loc="280,90" spacing="38" alwayCentered="false" maxVisibleButtons="7" allowTopBottomWrap="false" showNumbers="false"/>

So right now, I have to set up relationships in my code, then tell my code not to display the composite images that are related to a special element, as the element should determine how they are drawn.

I think that this can all be solved with something the following syntax:

Code:

<CompositeImage name="NormalButtonImage" size="166,45" specialElement="Buttons">    
...                
</CompositeImage>

Basically it's the same way you handle TextStyles. Adding this shouldn't break existing skins, and will also make it easier for anyone manually editing a skin's XML file to clearly see the realtionships without having to run GBPVR.

Obviously, you know the big picture, and why this may not be a good idea. I'd love to hear your thoughts on this.

gruskada

[sub]

I know it would make your project easier, but to be honest, there often isnt a direct relationship between a special element and a composite element. I've typically use a special element when I've needed to represent some positional information, but there is not a picture to go at the location.

[gruskada]

I know it would make your project easier, but to be honest, there often isnt a direct relationship between a special element and a composite element.

Wow, you're quick. Anyway, I just thought it would be helpful in the cases where there is a relationship (like everywhere a "Buttons" special element is used).

gruskada

[gruskada]

I think something like this would be my ideal skin XML file to work with:

Code:

<settings>
    <CompositeImages>
        <CompositeImage name="[required]" size="[required]" specialElement="[optional]">
    </CompositeImages>
    
    <!--- used for positioning only --->
    <SpecialElements>
        <SpecialElement name="[required]" loc="[required]">
    </SpecialElements>

    <!--- used to set variables only --->
    <Variables>
        <Variable name="[required]" value="[required]" specialElement="[optional]">
    </Variables>    
</settings>

...ducking for cover :eek:

gruskada

[psycik]

My only concern with the above, is why do we need size information on the compositeimage and the special element, since theoretically thewy should be the same.

Other than that, naming convention helps as well.

If I have SE LeftList then I'll probably make a CI called LeftListImage.

But that's just me.

[gruskada]

My only concern with the above, is why do we need size information on the compositeimage and the special element, since theoretically thewy should be the same.

Other than that, naming convention helps as well.

If I have SE LeftList then I'll probably make a CI called LeftListImage.

But that's just me.

There's no size info (width,height) on the special element, just position info (Loc), which is just an x,y coord.

gruskada