Community Skin named colors.

[Fatman_do]

Here is a list of what is going on in the baseskin.xml file for named colors.

This section is what is used currently by the Community skin and by blue.

Code:

<NamedColors>
    <!--TV Guide Colors, Do NOT use vertical gradients  -->
<NamedColor name="NormalListing" color="Transparent"/>
<NamedColor name="ScheduledListing" color="Horizontal:#990000-#AA0000"/>
<NamedColor name="SelectedListing" color="#009900"/>
<NamedColor name="SelectedScheduledListing" color="Horizontal:#440000-#BB0000"/>
<NamedColor name="ConflictListing" color="Horizontal:#442200-#AA5533"/>        
<NamedColor name="SelectedConflictListing" color="Horizontal:#664422-#CC8844"/>
    <!-- the surrounds must be solid colours for now -->
<NamedColor name="ListingSurround" color="#0F59B2"/>
<NamedColor name="ChannelIconSurround" color="Transparent"/>
<NamedColor name="ChannelNameRectangle" color="Transparent"/>
<NamedColor name="SelectedListingSurround" color="Transparent"/>    

    <!-- System plugin disk drive pie chart -->    
<NamedColor name="TotalDiskSpace" color="#660000" />
<NamedColor name="FreeDiskSpace" color="#006600" />
        
    <!-- ListView Selection Background Color styles, no longer used by 'Blue', but used by plugins -->
<NamedColor name="Selection" color="Blue" />

These are new values used by blue, for xml colors

Code:

<!-- standard selection highlight colours -->
<NamedColor name="StandardSelectionBackground" color="Blue" />    
    <!-- standard popup colours -->
<NamedColor name="PopupBackground" color="Black" />
<NamedColor name="PopupBorder" color="White" />
    <!-- standard list colours -->
<NamedColor name="ListBackground" color="Black" />
<NamedColor name="ListBorder" color="LightGray" />
</NamedColors>

This is new stuff to play with and consider.

Code:

<!-- standard font colours -->
<NamedColor name="ButtonNormal" color="LightGray" />
<NamedColor name="ButtonSelected" color="LightGray" />

<NamedColor name="ListViewActive" color="LightBlue" />
<NamedColor name="ListViewNormal" color="LightGray" />
<NamedColor name="ListViewSelected" color="Yellow" />
        
<NamedColor name="BackgroundText" color="LightGray" />
<NamedColor name="BackgroundTag" color="Yellow" />
        
<NamedColor name="PopupText" color="LightGray" />
<NamedColor name="PopupTag" color="Yellow" />
        
<NamedColor name="ListText" color="LightGray" />
<NamedColor name="ListTag" color="Yellow" />
        
<NamedColor name="[B]ScreenText[/B]" color="LightGray" />
<NamedColor name="ScreenTag" color="Yellow" />
        
<NamedColor name="TitleText" color="#a2c9f1" />
<NamedColor name="TitleTag" color="Yellow" />
    <!--For use with DrawTextWithOutline-->
<NamedColor name="GeneralOutline" color="Black" />
<NamedColor name="NormalOutline" color="Transparent" />
<NamedColor name="SelectedOutline" color="Black" />

The thought process here is that the textstyles will used NamedColor values like :

Code:

<TextStyle name="ScreenText" [B]color="ScreenText[/B]" typeFace="Arial" size="13" style="bold" />
<TextStyle name="ScreenTextLarge" [B]color="ScreenText[/B]" typeFace="Arial" size="16" style="bold" />

Changing a named color will effect those two textstyles. Also, if a plugin desired to use a custom sized or named "ScreenText" element, they could do this to keep the same look.

Code:

<TextStyle name="Temperature" [B]color="ScreenText[/B]" typeFace="Arial" size="20" style="bold" />

It is not possible yet to "pass along" a 'typeFace' or 'style' value. (At least that I am aware of)

[McBainUK]

This all looks OK. Its a good way of getting round the problem with Hardcoded textstyles - still able to use the correct colors which will keep the aim of readability/contrast.

[McBainUK]

Shouldnt take much to implement too, all thats needed is to edit baseskin.xml and take the colours out of the common textstyles.

[Fatman_do]

Will be in the next baseskin.xml released.