"Community Skin" testers needed.

[MixMan]

I made image renaming for archive/videos the other day.
Did't change any text names though.
GeneralText could be renamed to ListText
The rest is fine in my eyes.

How about a DetailText and DetailTextSelected (Perhaps large and small that could be used in DetailViews (recordings, stocks, weather, sportscores) Normally 14pt.
The small variant normally 12pt

[McBainUK]

How about a DetailText and DetailTextSelected

I could go for BackgroundText. I still think it would be useful to have BackgroundTextSmall and BackgroundTextLarge as well. If the idea is that plug-in developers create a single version of their skin which can then be quickly customized only by chaning the baseskin file that may mostly work, but in cases where the plug-in developer has placed serveral things in the same area they may need the font size to be small, for example, so being able to use BackgroundTextSmall would be helpful.
Jeff

Yes, was thinking this also. Using same example, I useuallt have the Cinema name in a larger font then the cinema address/tel num.

Have made a wiki page for proposed text style names. Too all, please contribute

[Jeff]

By the way, if the only plug-ins using GeneralText and SelectedGeneralText were mine, they are not hard coded. They are defined in the skin file and can be changed.

Jeff

[MixMan]

Yes, was thinking this also. Using same example, I useuallt have the Cinema name in a larger font then the cinema address/tel num.

Have made a wiki page for proposed text style names. Too all, please contribute

All plugins including Blue have have ButtonText today. Why on earth, change that to ButtonNormal ?
It shall remain ButtonText otherwise the Subs fallback fails? (it does it anyway now)
Let Sub decide on Text definitions !

[Fatman_do]

Alright.

So we could have something like:

TitleAreaTextSmall
TitleAreaTextNormal
TitleAreaTextLarge

That could be used for time, sort method, calendar date, weather headers, ect.
Text that would be used in the title area and possibly drawn over a title bar image. (Name may not be best in my example)

Then you have the same for PopupTextSmall, Normal, Large.
Self explanitory.
Would we want several PopupTextTags (Text usually followed by a colon ie. Artist: )? Or would those be one size normally?

BackgroundTextSmall, Normal, Large.
Those could be used for remote control hints or any other text that is drawn over the background image and/or the Background_Text image.

ListViewTextSmall, Normal, Large.
Non-selectable text drawn over a List Background. (we have selector texts).

Just shooting from the hip here.

[Fatman_do]

By the way, if the only plug-ins using GeneralText and SelectedGeneralText were mine, they are not hard coded. They are defined in the skin file and can be changed.

Jeff

Not that I remember.

This is what I did for example in the Music Player jukebox skin.xml

Code:

        [COLOR="SeaGreen"]<!--<TextStyle name="ScreenName" color="LightGray" typeFace="Arial" size="17" style="bold"/>-->
        <!--<TextStyle name="ButtonText" color="White" typeFace="Arial" size="12" style="bold"/>-->[/COLOR]
        <TextStyle name="TitleBarText" color="White" typeFace="Arial" size="14" style="bold" />
    [COLOR="SeaGreen"]    <!--     Renamed as ListText and ListTextSelected
        <TextStyle name="GeneralText" color="LightGray" typeFace="Arial" size="13" style="bold"/>
        <TextStyle name="SelectedGeneralText" color="White" typeFace="Arial" size="13" style="bold"/>
        -->[/COLOR]
        <TextStyle name="NowPlayingTitle" color="Yellow" typeFace="Arial" size="14" style="bold"/>
        <TextStyle name="NowPlayingInfo" color="White" typeFace="Arial" size="14" style="bold"/>
        <TextStyle name="WaitMessage" color="Black" typeFace="Arial" size="14" style="bold"/>

[Fatman_do]

I made image renaming for archive/videos the other day.
Did't change any text names though.
GeneralText could be renamed to ListText
The rest is fine in my eyes.

How about a DetailText and DetailTextSelected (Perhaps large and small that could be used in DetailViews (recordings, stocks, weather, sportscores) Normally 14pt.
The small variant normally 12pt

As a "side note" to this, I think maybe our image definition for ListViewDetail.... is not tall enough. Right now it is 470x50, but several other plugins like the ones listed above would benefit from a taller source image when scaled. (Gmail is another one). 470x75 might work out better. If larger texts are possible with the possiblility 3 lines of text in a detail selection, 50 just doesn't scale well.

Just one of my findings in going through things.

Maybe the source image for ListView_Selected/Normal should get a bump to 30 or 35 also? Scaling the images down always looks better than upscaling.

[McBainUK]

It shall remain ButtonText otherwise the Subs fallback fails? (it does it anyway now)

Maybe, for once, instead of declaring a way of doing things is gospel, why not propose an alternative :mad:

I have not looked at current textstyles but if ButtonText is already used then that should be considerd.

Let Sub decide on Text definitions

Is this what he is doing for the 98.x Blue skin? I havnt played with the pre-releases yet. Sub?

[MixMan]

Maybe, for once, instead of declaring a way of doing things is gospel, why not propose an alternative :mad:

I have not looked at current textstyles but if ButtonText is already used then that should be considerd.


Is this what he is doing for the 98.x Blue skin? I havnt played with the pre-releases yet. Sub?

Sorry, I don't know how in many posts I have tried to explain how we should get all plugins to work with all skins. No one has confirmed or understood my suggestions with that basic idea.? You all are focused on creating something new without considering what exists.

I'm about tho withdraw from this whole discussion.
I will probably remove plugin support from the Advisor/Baseskin skin gradually....as it look right now.

[Fatman_do]

Is this what he is doing for the 98.x Blue skin? I havnt played with the pre-releases yet. Sub?

Whatever happens with 98+ shouldn't be a roadblock to new ideas at this time. Things might change slowly as ideas are "proofed", and they may not ever change if there is no benefit to them.

Those that have kept up with me through all these threads will probably remember that the baseskin.xml was my main focus for maximum compatibility, regardless of skinning style or method.

Right now, I don't think what is currently in 'blue' or what is in the next version of 'blue' should stop a Community skin project from testing new ideas and methods. This puts us in the seat of beta testers and skinning "developers" so sub doesn't have to mess with it at this time. This is how things can get filtered back into blue if we are sucessful in providing a clean and effiecient system that can provide benefits to sub instead of asking him to make changes just because we want him to.