Community skin project

[MixMan]

I strongly agree this should be the leading principle.

You guys.....have a look at the BaseSkin's baseskin.xml file.
I is using the baseskin.xml to the max almost for changing stuff in a skin.
Dont worry......baseskin.xml will be used for basic stuff.

[Fatman_do]

Sample of a code style that developers may be able to come up with a way to work with off into the future.(also is in this post as an edit)


Baseskin.xml:

Code:

<ListViewBackground>[color=Blue]<DrawImage filename="..\resources\Listview.png"/>[/color]</ListViewBackground>
<PopUpBackground>[color=Blue]<DrawRoundedRect radius="5" borderWidth="2" borderColor="White" fillColor="Black"/>[/color]</PopUpBackground>
<[B]ListItemNormal[/B]>[color=Blue]<DrawImage filename="..\resources\ListItemNormal.png"/>[/color]</ListItemNormal>

ect. you get the point.

plugin skin .xml:

Code:

<CompositeImage name="ListViewNormalItem" size="500,30">            
    <Element name="[B]ListItemNormal[/B]" loc="3,3" size="494,24"/>
    <DrawText text="@title" loc="5,4" size="390,25" textStyle="ListViewItems" align="Left"/>
    <DrawText text="@lastRecordingDate" loc="5,4" size="495,25" textStyle="ListViewItems" align="Right"/>
</CompositeImage>

[Old Dog]

(Edit: added quote)

Old Dog,

Would you mind, if you had time, to outline in more detail what you are thinking. I am not sure I have a grasp on all the specifics that you may have in mind. I have an abstract, but I don't want to assume I know the details. You can put in a post, it doesn't have to be anything formal. I like to print things out and run thru them and highlight things and make notations. I can do this easier off-line.

What makes this project difficult is not the task at hand but rather the participants in the effort. It is my intention here to develop a plan that will allow the participants to begin working together and to provide the opportunity for them to workout their differences in a contructive manner. That's all folks!

All of us need to drop our commitment to the past and establish a commitment to this project.

Goals and background

Accept Blue as the standard.

We will produce two sets of xml files for the standard. Files in the first set are devoid of all graphical elements, the second set of files include graphical elements appropriate to Blue. Files in the first set are proper subsets of files in the second set.

When a developer creates a new plug-in they will create both xml files. The first file defines the information layout, the second simply adds graphics.

The layout file allows the developer to focus on the organization and placement of the plug-in output, i.e. blocks of information, using the default text styles defined in BaseSkin.xml. When satisfied with the layout, the developer will add the graphics for Blue. The layout file will also be useful to the skinner as a starting point for their graphics design.

The Plan

Beginning with the core features, we will create new xml files for Blue. We will begin each feature by polling the community to identify the best existing implementation of the feature. We will use that implementation as a starting point. Note that what we are most concerned with in our poll is the text presentation; the organization, placement, and fonts.

By the time we have finished the core features, we will probably have a good definition of the BaseSkin.xml, especially text styles.

After completing the core features, we will release the community skin for review. We need to develop a plan to deal with this review period.

The next phase of the project focuses on plug-in features. We will select each plug-in one at a time by polling the community. Once we have selected a plug-in, we will poll for the best implementation. We will create the two xml files for each plug-in.

Note that as we reach a consensus, we will be able to split-up into teams and address plug-ins in parallel. During the first phase we should work as a single, unruly, mob; we need to workout our differences and we must reach a consensus.

As long as we think of what "I" can do instead of what "we" can do, we will get nowhere.

[sub]

Sample of a code style that developers may be able to come up with a way to work with off into the future.(also is in this post as an edit)


Baseskin.xml:

Code:

<ListViewBackground>[COLOR=blue]<DrawImage filename="..\resources\Listview.png"/>[/COLOR]</ListViewBackground>
<PopUpBackground>[COLOR=blue]<DrawRoundedRect radius="5" borderWidth="2" borderColor="White" fillColor="Black"/>[/COLOR]</PopUpBackground>
<[B]ListItemNormal[/B]>[COLOR=blue]<DrawImage filename="..\resources\ListItemNormal.png"/>[/COLOR]</ListItemNormal>

ect. you get the point.

plugin skin .xml:

Code:

<CompositeImage name="ListViewNormalItem" size="500,30">            
    <Element name="[B]ListItemNormal[/B]" loc="3,3" size="494,24"/>
    <DrawText text="@title" loc="5,4" size="390,25" textStyle="ListViewItems" align="Left"/>
    <DrawText text="@lastRecordingDate" loc="5,4" size="495,25" textStyle="ListViewItems" align="Right"/>
</CompositeImage>

I've already added something like that in the next release, but not quite in the same way you've asked for. In the next release there will be a new <DrawCompositeImage> skinning command. This addition will be very useful...

[Fatman_do]

I've already added something like that in the next release, but not quite in the same way you've asked for. In the next release there will be a new <DrawCompositeImage> skinning command. This addition will be very useful...

Fantastic.

I just guessed at how it would be done. It was more of an expression of the concept vs. actual method to be used.

[reboot]

Beginning with the core features, we will create new xml files for Blue. We will begin each feature by polling the community to identify the best existing implementation of the feature. We will use that implementation as a starting point. Note that what we are most concerned with in our poll is the text presentation; the organization, placement, and fonts.

By the time we have finished the core features, we will probably have a good definition of the BaseSkin.xml, especially text styles.

This was what I was trying to convey with a Baseskin.xml controlling the look, instead of individual skin.xml files.

The next phase of the project focuses on plug-in features. We will select each plug-in one at a time by polling the community. Once we have selected a plug-in, we will poll for the best implementation. We will create the two xml files for each plug-in.

This is where it get's complicated. Some plugins will easily skin using BaseSkin.xml. Others are impossible.

If we (the skinners) can get the Base sorted, with 2 xml's, one with graphics, one without, that will be half the battle won.
If we can then adopt the plugins that allow themselves to be skinned in this method, by working in parallel, we will have a contiguous skin, with a definitive list of plugins that will work.
We should, at this point, be able to easily make a new skin, with a minimum of extra effort.
Other plugins that do not allow themselves to be skinned will have to be rewritten, or dropped from the project.

Any input on all this from any plugin developers?

[McBainUK]

I've already added something like that in the next release, but not quite in the same way you've asked for. In the next release there will be a new <DrawCompositeImage> skinning command. This addition will be very useful...

In what way? How do you see this being used? :confused:

[sub]

I'll try and give a reply to this later today. Its not a reply that I can knock up in a hurry, and unfortunately I'm in the middle of moving my home office to another room and a couple of things. If my wife sees me sitting at the keyboard for more than a few minutes, then it will be treated as 'slacking'.

[McBainUK]

I'll try and give a reply to this later today. Its not a reply that I can knock up in a hurry, and unfortunately I'm in the middle of moving my home office to another room and a couple of things. If my wife sees me sitting at the keyboard for more than a few minutes, then it will be treated as 'slacking'.

No trouble sub, wouldn't want to get you into trouble

[Fatman_do]

No trouble sub, wouldn't want to get you into trouble

From "She who must not be Ignored" no less.