[DEV] Skinplugin Resources

[McBainUK]

I think PluginName_Task was to allow for specific icons for a plugin, although I'll have to check...

The SkinPlugin will copy all the generally named task images to the _TaskImage folder with the correct name

For example:

Code:

<Image name="DVD.png" target="%SKINROOT%\_TaskImages\DVD.png"/>
        <Image name="DVD.png" target="%SKINROOT%\_TaskImages\DVD Ripper.png"/>
        <Image name="DVD.png" target="%SKINROOT%\_TaskImages\BurnDVDX2.png"/>
        <Image name="DVD.png" target="%SKINROOT%\_TaskImages\xdvd.png"/>
        <Image name="DVD.png" target="%SKINROOT%\_TaskImages\DVD to MPEG.png"/>

And then, it if finds a specific task image for a plugin it will copy that to _TaskImages also. This way, a theme can still specify a custom task image for a particular task. Example:

Code:

<Image name="DVD Ripper.png" target="%SKINROOT%\_TaskImages\DVD Ripper.png"/>

Task image mapping document attached. This may need to be updated (and the skinpluginconfig.xml file) for any new plugins.

[McBainUK]

So, in conclusion:

* If the _Task image in the resources folder is the same as the default one for that plugin then it should be dropped. Else it should be renamed to the plugin name (without the _Task suffix)

* If there are task images that are named after plugin that are the same as the default one for that plugin then it might as well be dropped also.

[Hairy]

Could I just check where you guys are leaning with this page

Is the idea that, whatever isn't removed from this list remains in the resource folder of the new default installation. Or will what remains be included in an addition download for those who would like it.

My preference would be, to only include the graphical and formatting options for CS Blue. It would make the download package smaller and easier to maintain. What survives on the list on the wiki page should need no maintenance as it's legacy stuff and could be wrapped up in an installer and placed with the addition themes.

As I said this is only my preference, but it alters my view on what should and shouldn't be removed from the wiki list. If the remaining graphics are to be included with the new default installation package then I'd prefer that all graphics and formatting I've contributed so far be removed. They'll be replaced as I release more themes.

If that makes any sense

[McBainUK]

Is the idea that, whatever isn't removed from this list remains in the resource folder of the new default installation.

This was my original intention but now I think differently.
----------------------------------------------------------------------------------------------------------------------------------
I've been re-reading some of the previous CS4 discussion threads and I think I've missed a point somewhere. Specificity I forgot about what was agreed here:

Communiy Skin [SD]
* Combined installer
* One default theme
* Support for PVRX2 and compatible plugins only
* Area on wiki for plugin xmls and additional theme/graphics

So this means the the CS-SD installer will ship with all XMLs for the all GB-PVR screens and supported plugins. It will also include some alt XMLs for user choices (eg metadata, library screens layout, main menu layout).

The only graphics and XMLs included will be "CS Blue".

Now (and this is the important bit), all current themes and graphics will be packaged up into an installer and placed on the wiki under a new "Graphics Packs, and Addional Themes sections". In time, this will be expanded with more themes and graphical options. This will still require some work as I think that some of the poor and/or duplicated images should be dropped. Note the themes may have to be recompiled due to SkinPlugin changes. So filtering out the poor/duplicated images should be the point of the "CommunitySkinTasksResourcesContents" page.
edit: but then if the idea is to have a Themes download page then just extract the images required for a theme and then drop the others (CS Blue will provide lots of options in future - and ones which will all play and look nice with each other.

CS4 will also hopefully ship with a new SkinPlugin with an improved UI and more options (eg screenheader).

Is this all correct or have I still got the wrong end of the stick...? If it is correct, what, now, are the primary tasks...?

[Fatman_do]

If it is correct, what, now, are the primary tasks...?[/B]

Get Fatman_do to get off his duff?

Seriously, I cannot thank everybody enough for their efforts.

What I am doing:
The installer is tripping me up on checking the skin to see if the skinplugin is a menu task, and then setting as so if not. I can read a value, it is just hard for me to figure out how to do it in a loop with the same tag.
Back burner right now, we may just have the installer run the config.exe as a checkbox option.

I promised to run through plugins...er...um.....er..that is my next task.

• Validate plugins
  
• Add meta-data variants to library skins
  
• Slick equivalent?
  
• New skinning features, different menu backgrounds, ect?
  

So, yeah, we will only package one theme and maybe a few other images. Some of the generic folder icon images and control images we could include.

[Hairy]

Again I'm only suggesting a preference. You guys have been doing this for a lot longer than me and I'm perfectly happy to go along with what you guys see fit

Now (and this is the important bit), all current themes and graphics will be packaged up into an installer and placed on the wiki under a new "Graphics Packs, and Addional Themes sections". In time, this will be expanded with more themes and graphical options. This will still require some work as I think that some of the poor and/or duplicated images should be dropped. Note the themes may have to be recompiled due to SkinPlugin changes. So filtering out the poor/duplicated images should be the point of the "CommunitySkinTasksResourcesContents" page.
edit: but then if the idea is to have a Themes download page then just extract the images required for a theme and then drop the others (CS Blue will provide lots of options in future - and ones which will all play and look nice with each other.

Yeah it was a bit flippant of me to say, simple remove my graphics and formatting and the just package up what's left. I wasn't thinking there at all. I think that we should clean out the resource folder as per your wiki page. Then extract the remaining themes and make them available as separate downloads and if there is anything left, then package that as a legacy addon.

If you guys are happy enough with that direction then I can better understand what I'd suggest be removed from the resource folder.

[McBainUK]

If it is correct, what, now, are the primary tasks...?

Get Fatman_do to get off his duff?

As well as this, I'm working on SkinPlugin4. Got some ideas on the UI, preview coming soon...