Full list of standard skin tags and attributes?

[Jeff]

It is good to see them all listed. I didn't know that some of them were available, which wil lhelp with skinning. What does the Element name tag do? What is the right way to use that if you are a plug-in?

Jeff

[sub]

- It looks like elements don't affect the display at all - they just define "hotspots" for the plugin?

Yes, there typically use for hotspots, but can also be used for positioning information for drawing some complexe element that cant described using a composite image (like OSD timeline).

- Is capitalization and camelCase required (or should it be)?

It is case sensitive.

- Can any "color" attribute in any tag take a named color, hex color or gradient?

A "color" in composite images and text styles needs to be a recognized System.Drawing.Color or # code. NamedColors are slightly different, and usually represent a brush loaded by the plugin to drawing (ie like gradients of show times in the tv guide.

- Are <Buttons> a special case, or are they supported natively?

It varies depending how old the screen is. The oldest screens, just used a SpecialElement to describe where buttons should be. On the new screens (some of the popups etc), I'm describing the button as an 'Element' in the CompositeImage.

- For <DrawPoly>, I assume the points need to connect to form a complete polygon?

I dont know what happens if you dont close the polygon.

- I assume <TextStyle> "name" attributes have to match up with something in the plugin?

They either match something defined in one of the composite images, or match name expected by the plugin.

- Did I misunderstand the use of anything else?

I dont know. This project well be difficult though. I only added the CompositeImage stuff about half way through the life of the GB-PVR project, so much of the older stuff, and old plugins dont use it much. I suspect you'll end up having to code explicit logic for most screens.

[gruskada]

Thanks for your responses, Sub.

I suspect you'll end up having to code explicit logic for most screens.

It's definitely looking more and more that way. I'm reading up on XSD now to see if that technology might be able to help map things out a bit (i.e. a certain CompositeImage tag belongs to a cerain SpecialElement tag), but I'm not sure if that will work or not yet.

This project well be difficult though.

Yep. Only I thought the difficult part would be the WYSIWYG designer. Now that I've got that part pretty much functioning, I'm seeing that this was the easy part

gruskada