[DEV] Progress

[Fatman_do]

Where can we host the (10mb) installer?

We have previous location for SkinPlugin we could use. I have to see if I still have a copy of the login information.

[McBainUK]

Yep just built and installed within the hour. For me everything I've tried in between mainmenu overlay and Taskimages didn't actually load.

I've just committed a change to (probably) fix this. I think before we go beta we should all spend time (not much, but some) testing/playing with the skin and plugin ourselves. I think we're close though

I've also just updated the SkinPluginConfig.xml to fix a couple of Task Image references (slight typo - Library vs libary and a couple of missing references)

EDIT: really minor: I also altered the theme descriptions CS Blue - Dark I think should be the default theme install, CS Blue is just a lighter variation on it for those who might prefer.

Great, these kind of things really bring the quality up.

[Hairy]

Looks good on this end

I've had a real good go on this, for the last few minutes and the only slight thing I found was that the screen header graphics listed in the theme.xml isn't updated when that theme is loaded, but it does update from the graphics option of the plugin. Everything else that I've tried loaded no problems.

There are so many options, I think the only way we'll catch any slight variances is with community testing.

Great work McBainUK, I definitely think we're at the beta stage.

[McBainUK]

I've had a real good go on this, for the last few minutes and the only slight thing I found was that the screen header graphics listed in the theme.xml isn't updated when that theme is loaded, but it does update from the graphics option of the plugin.

Is the ScreenHeader entry in the theme.xml pointing to the right option? It looks like both themes are using the same option?

There are so many options, I think the only way we'll catch any slight variances is with community testing.
Great work McBainUK, I definitely think we're at the beta stage.

Agree. Esp with this bit lol

[Hairy]

For me it appears that when a theme is loaded and the currenttheme.xml is rewritten, the screenheader reference isn't included. I noticed that it wasn't referenced in the currenttheme.xml, so I copied the CS Blue - Dark theme and renamed it. Then I changed the screenheader graphic (via the plugin) and reloaded the default CS Blue - Dark theme and sure enough the screenheader reference went missing.

[McBainUK]

For me it appears that when a theme is loaded and the currenttheme.xml is rewritten, the screenheader reference isn't included. I noticed that it wasn't referenced in the currenttheme.xml, so I copied the CS Blue - Dark theme and renamed it. Then I changed the screenheader graphic (via the plugin) and reloaded the default CS Blue - Dark theme and sure enough the screenheader reference went missing.

If you rename

resources\Graphics\ScreenHeader\CS Blue\ScreenHeader.PNG

to

Resources\Graphics\ScreenHeader\CS Blue\ScreenHeader.png

does that fix it?

[Hairy]

Yep, spot on!

If you gave me one hundred guesses, I don't think I would have come up with that

[McBainUK]

Yep, spot on!

Great. I've fixed it on the SVN also.

[McBainUK]

I've nearly finished working on adding the ability to directly edit an tag in an XML skin file.

Current applications I've thought of are mostly text based - font size and colour of a small set of textstyles in baseskin.xml. Can you guys think of any other applications of this?

[Fatman_do]

Anything else may get "messy" as location tampering could domino into have to tweak every location.

If you move screen name, then you may have to move buttons, you move buttons, so now you have to move lists....I think with smart layout control, and any overscan feedback we recieve, the locations should be pretty much "locked down".

Keep in mind the legacy baseskin.xml file with these changes as well.