[DEV] Additional themes for CS4

[Hairy]

Guys, is it okay if we add any additional themes to the existing SVN and would it be possible to mirror the current set-up. By that I mean, currently I just place any graphics/formatting in their relevant folders and compile the installer scripts. Could we do the same for additional themes?

A folder structure like:
[INDENT][Additional Themes] => Theme name (eg Reflect) => CS-SD => install
-----------------------------------------------------------=> plugin
-----------------------------------------------------------=> skin

------------------------------------------------=> CS-WS => install
-----------------------------------------------------------=> plugin
-----------------------------------------------------------=> skin[/INDENT]
with some sort of reusable generic installer script that compiles each version (SD+WS).

That way I could just add the relevant files and compile the scripts.

Thoughts?

[McBainUK]

For these new themes, would there be xml differences or only graphics differences?

[Hairy]

Currently everything will go into the "...plugin\Resources folder", but it would be good to have the option to include theme specific xml's for the community skin. But it's not really essential, I'm just looking to replicate the current set-up - add files and compile.

[McBainUK]

The themes should be created from files in the resources folder. If new XMLs are required then they should be an editable skin item and again, in the resources folder. This way all themes and all elements are accessible from the SkinPlugin and people can swap and change.

A theme file in resources\Themes\New Wizzy Theme\ is what brings it all together to create a theme.

Does this make sense?

[McBainUK]

Reading your 1st post again is the idea to have separate them downloads? I think it might be nice (like with CS3) to have all the themes and files ready for use without extra downloads...

[McBainUK]

I think it might be nice (like with CS3) to have all the themes and files ready for use without extra downloads...

Although I'm not that sure on this...

[Fatman_do]

If we go with the built in method, it would require a complete install. If we added themes as a separate item, that would be an easier install option and keep the install package from growing in size.

By having the themes separated out, it would, in theory, make maintaining/updating them easier.

[Graham]

Here's one lazy punters view .. for what it's worth.

I would like to be able to see a gallery of Themes and select one for download.

A snazzy solution would let me browse a gallery and then pick downloads from within the skin plugin.

That was easy and only took me ten seconds to type ... if only I could dream up a way to implement it without you guys having to work for ten months.

[Hairy]

Reading your 1st post again is the idea to have separate them downloads?

Back when we were discussing where to go with the CS project, the general consensus was to have one default theme in the package and make additional themes available as separate downloads. So users could just select the themes they wanted and we didn't have one large theme repository that needed to be updated every time one thing changed.

The themes should be created from files in the resources folder.

I'm okay with that.

As I said I don't really mind exactly how, it would just be easier for me if we could replicate how I can build a CS installer now, and apply it to these further themes.

[McBainUK]

Hmm, re-reading my posts it's seems answered questions with too few answers. Here's my attempt at being a bit more verbose about it....

1. Where to store the theme files on the SVN?
I think a new 'Theme Install' installer script will need to be created (quite a small task).

The folder structure in your 1st post I don't understand. The plugin and skin folders would mean the files would go straight into the skin, whereas we want it to be installed into the resources folder, for later browsing and application.

So the folder structure would match that of the resources folders on the SVN. Like:

[Additional Themes] => Theme name (eg Reflect) => Resources => Graphics
-----------------------------------------------------------=> Layout
-----------------------------------------------------------=> Text
-----------------------------------------------------------=> Themes

------------------------------------------------=> ResourcesWS => Graphics
-----------------------------------------------------------=> Layout
-----------------------------------------------------------=> Text
-----------------------------------------------------------=> Themes

A installer script in the theme name folder would be the installer for that theme. All that would be different really would be the theme name variable in the script - would have to try it out to be sure.

2. How to distribute themes?
A theme 'gallery page on the wiki which has installer exes for themes. This keeps down the size and complexity of the main installer package (which was one of the goals of CS4 if I remember correctly).

3. Where to put the theme files on the end users machine?
A theme installer will:
* copy the theme.xml file (and previews) into Resources(WS)\Themes\. This makes the theme selectable from the SkinPugin.
* copy the graphics and XML files that make up the theme into Graphics\Layout\Text resource folders. This makes the theme 'applyable' and allows elements to be browsable from the SkinPugin and allows people to mix and match.