CommunitySkin 4 Open development thread.

[Hairy]

As I've said I really like the ideas so far, for clarity - the way I see it is:

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
  

Community Skin [HD]

• Carbon copy of above but with the emphasis on HD graphics (I suggest 1920x1080 resolution) and xml layout to maximize the added real estate.
  

The questions I have:

How do we tackle the newly added skinning elements, specifically the metadata layouts. I "think" we can handle the new slick main menu layout with the existing skin plugin?
How do we deploy the additional themes and graphics packs? Can they be hosted on the wiki? Will they need an installer?

My musings

[McBainUK]

I "think" we can handle the new slick main menu layout with the existing skin plugin?

Haven't looked closely into it but I think it should be ok. Just add it as a main menu option.

How do we tackle the newly added skinning elements, specifically the metadata layouts.

Again, I haven't looked into it. Fatman? But it's probably just a case of knocking up a 1st attempt and then build on it.

How do we deploy the additional themes and graphics packs? Can they be hosted on the wiki? Will they need an installer?

I think an installer would be best - follows the "just works" principle. You'll be surprised how many people have trouble with extracting zip files.

[Hairy]

Again, I haven't looked into it. Fatman? But it's probably just a case of knocking up a 1st attempt and then build on it.

Again this falls under code so you guys will have to talk slowly

As I see it the two different layouts, the old and the new meta, are pretty different and will require different xml layouts for the basic plugins (video, music and the like). These are static and not changeable in via the plugin (?), so I was wondering how/if this will be a selectable option?

[McBainUK]

If there was a need for it be optional then it could be done quite simply, with an xml for each style and then a plugin option to swap between them. But as i saidit's a case of trial and assor.

[Fatman_do]

Hairy, I have created a simple installer script that can be used to create theme installers.

Within the file there are instructions on how to use.

Code:

; CommunitySkin SD (Beta) update installer script.
;
; Requirements:
; NSIS installer program. May be download from
;        http://nsis.sourceforge.net/Main_Page
;
; Instructions:
; Step1 : Create a folder to contain files to install (Example: \CS-UPDATE).
; Step2 : Create sub folders
;        \SKIN\COMMUNITY-SD
;        \SKIN2\COMMUNITY-SD
;        \PLUGINS\SKINPLUGIN
;        --Note, any skin name or plugin folder name can be used
;          for other projects.
; Step4 : Create an empty PLACEHOLDER.TXT file in each of those three folders.
;           This prevents compiling errors if no files found.
; Step5 : Copy files you wish to include with this installer in the correct
;         subfolder, keeping proper path structure.
;        --Example: \CS-UPDATE\SKIN2\COMMUNITY-SD\MUSIC LIBRARY\SKIN.XML
; Step6 : Place this file and a file called UPDATE-CHANGELOG.TXT into the folder
;         created on STEP1.
;        --Note, contents of UPDATE-CHANGELOG.TXT will be displayed when installer
;          is ran, so include any notes or license info in it.
; Step7 : Modify line number 31 & 32 of this file with correct information.
;         This will name the installer .EXE file.
; Step8:  Compile script using NSIS program, or Right click on this file
;         and select "Compile NSIS Script" in windows explorer.
;
;         ***************Change these two lines below**************
;
!define PLUGIN_NAME "Plugin-x" ; Change this line to describe the update or name of plugin
!define SKIN_RATIO "4x3" ; Change this line to describe screen ratio as "4x3" , "16x9",  or "Update" version

;
;         ***************No changes are required below this point**************

[ATTACHMENT NOT FOUND]

Edit: Changed name to Community-SD

[Hairy]

Thanks, I'll check it out.

As always an education gents, an education!

Cheers

[McBainUK]

You select through the start menu TortoiseSVN>Settings...

Thanks for the wlakthrough. Turned out my work firewall was blocking the https connection - which caused lots of strange SVN errors I didn't understand. All setup from home now

[McBainUK]

Hairy, what's this new (default) theme called? CS-Blue?

I'm trying to create a SkinPlugin resources directory structure and theme.xml file for it - I am working on the SVN setup and installer testing.

[Hairy]

CS Blue is what I named it while working on it, because it's for the CS and it's blue

Yep, yet another helpful post! . I don't really mind what we call it. I think CS Blue is okay, but I'm open to suggestions.

[McBainUK]

CS Blue it is then.