[DEV] Progress

[Fatman_do]

I think so.

[Fatman_do]

Some SVN instructions here.

http://gbpvr.com/pmwiki/pmwiki.php/Devel...tySkin-SVN

[Hairy]

Cheers Fatman_do,

I got to step 6 no probs, other than me forgetting my bloody password for the google account , haven't pulled the trigger on the making changes step yet

Could I make a noobie suggestion? As I understand it the CS-HD and CS-SD folders are for the installer package when they get to release level and the other folders (DevGraphics, plugin, shared) are being used to get it to that level. Would it make any sense to rename the folders to Community-HD and Community-SD and Development, to make it clearer?

[Fatman_do]

Cheers Fatman_do,

I got to step 6 no probs, other than me forgetting my bloody password for the google account , haven't pulled the trigger on the making changes step yet

Could I make a noobie suggestion? As I understand it the CS-HD and CS-SD folders are for the installer package when they get to release level and the other folders (DevGraphics, plugin, shared) are being used to get it to that level. Would it make any sense to rename the folders to Community-HD and Community-SD and Development, to make it clearer?

Not a problem with renaming them Hairy.

The CS-HD and CS-SD are actually only used IF there are separate xml's for HD and SD versions. Otherwise all xml's are pulled from the Shared folder. For example, if we have a HD music library, we pull the SD version of the xml's and place them in the CS-SD folder, place the HD version of the xml's in the CS-HD folder, and remove them from the Shared folder.

That at least is the plan for now.

[Hairy]

The CS-HD and CS-SD are actually only used IF there are separate xml's for HD and SD versions. Otherwise all xml's are pulled from the Shared folder. For example, if we have a HD music library, we pull the SD version of the xml's and place them in the CS-SD folder, place the HD version of the xml's in the CS-HD folder, and remove them from the Shared folder.

Do you know what that makes perfect sense, I was stuck in "keep SD and HD seperate so I don't mix anything up" thinking mode :o

I'm gonna be quiet now until I've got something intelligent to contribute........that may be some time


Disclaimer: I'm a little bit buzzed from inhaling wood varnish fumes all day and I'm enjoying rocking my head from side to side a little too much right now.......... I think I can feel colours

[McBainUK]

As I understand it the CS-HD and CS-SD folders are for the installer package when they get to release level and the other folders (DevGraphics, plugin, shared) are being used to get it to that level.

CS-SD\install\ and CS-HD\install\ are the "release level" folders.

Note that I wrote some details on the SVN structure (explaining why and how it was made this way) in the readme.rtf file in the SVN root.

[Fatman_do]

Note that I wrote some details on the SVN structure (explaining why and how it was made this way) in the readme.rtf file in the SVN root.

For giggles, here is the contents of that file:

SVN Directory Structure
These are the top level folders. Within each are the INSTALL, PLUGIN and SKIN folders. The installers will grab files from the shared AND ONE OF the CS-SD/CS-HD derivatives.
For now, most of the files will be in the SHARED folder. In the near future, when SD/HD differences are required then a copy of the file will be made in CS-SD and CS-HD (and the original deleted from SHARED). This file will now therefore follow 2 paths.
* CS-HD
* CS-SD
* SHARED
INSTALL
All files related to the creating the installer setup.exe.
* NSI script
* icons, images and logos
* readme/license/contributors & acknowledgments files
PLUGIN
All files that would go into gbpvr/plugins/SkinPlugin
* plugin dll
* helper dll
* helper exes
* config dlls
* plugin images
* current theme xml file
RESOURCES
All images, XMLs and themes that will be distributed with the default install. Other themes and images will be handled and stored seperatly due to licensing and file size considerations.
SKIN
All XML files for the plugins and default GB-PVR screens.
GBPVR
* All files that would go into gbpvr/skin/CommunityX
PVRX2
All files that would go into gbpvr/skin2/CommunityX
* CoreImages
* TaskImages
* SpecialImages
All these folders will have the default theme files.
PLUGIN
* source code for the SkinPlugin
note: CAPITALS = folder names

[McBainUK]

How are you guys getting on?

I'm slowly making progress, nothing to show yet tho.

[Fatman_do]

Updated to SVN last night. Added some elements to the baseskin.xml file and added PopupList_Normal.png, _Selected.png, _SelectedInactive.png

I need to go through all plugin popups and check for usage ect.

Also removed several plugins from the install folders.

[McBainUK]

How are you guys getting on?

Plugin is coming along micely won't be long before I tackle the tricky part - dynamic previews of editable skin item options.

System shark has kindly offered to help so if I can figre out how to split up some of the coding tasks this might speed things up.

ps Hapy Christmas for next week = reckon we deserve a bit of a break - if lots of kids running around, eating and drinking can be considered a break...