Appearance Manager

[Old Dog]

I did find one small problem with the zip file. It would cause a problem for post Christmas users when selecting a main background.

I created a new zip and uploaded it to the wiki.

I may need to leave shortly, so if I break off abruptly...

You may want to delete your existing Collection directory,
...GBPVR\skin\Collection.

Download the latest zip from the wiki into your GBPVR.exe directory. Unzip using a tool that supports pathnames (don't they all?).

When finished you should find StartGBPVR.exe in the GBPVR.exe directory, AppearanceManager.dll in the ...GBPVR\Plugin directory, and the collection directory tree at ...GBPVR\skin\Collection.

You should now take the time to get the skin to work. All you should have to do is select it in the GBPVR Config program.

After getting the skin to work, install the Appearance button. Restart GBPVR and select Appearance. As a test, only change your main background then select SAVE.

At this point, all instances of GBPVR.exe should terminate. If you are on an MVP, a new instance of GBPVR will automatically startup. If not an MVP, you should see a box on your screen saying "Restarting GBPVR", then a new instance of GBPVR. In either case, you should now see the changes.

Let me know where it doesn't work.

[Old Dog]

Dottore,

Teaser Back!

-David

[Old Dog]

Dottore's new skin has forced me to rub my two little brain cells together...

For example, buttons used by the collection's main menu wouldn't work with olbia and vice-versa.

Instead of simple compatability switches, the appearance.xml file for a given skin might list resource directory paths. Some elements might be common with other skins, other's might be unique to one skin. The paths will direct appearance manager appropriatly.

[KingArgyle]

Old Dog,

If you want an XML Schemas for the Appearance.xml file, let me know. I day job is as an XML Data Architect and work every day with XML Schemas. The advantage is that it makes sure that your XML files are valid and contain all the elements that you expect them too.

[Old Dog]

Old Dog,

If you want an XML Schemas for the Appearance.xml file, let me know. I day job is as an XML Data Architect and work every day with XML Schemas. The advantage is that it makes sure that your XML files are valid and contain all the elements that you expect them too.

You're hired.

[KingArgyle]

Sent you a PM with my email address.

[Old Dog]

The current plan for supporting Olbia requires a skin.xml file for appearance manager. The xml will be a modfied version of the skin's main menu xml. Instead of hard-coding image file names as in the original, the modified xml will used arguments passed in from AM.

This will make the system more generic and allow a better representation of the skin designers layout.

The skin designer will need to keep the two skins in sync.

-David

[Old Dog]

The skin designer will need to keep the two skins in sync.

The skin designer will need to keep the two XMLs in sync.

[KingArgyle]

You could with an XSLT automate the creation of the Skin.xml that Appearance Manager requires based off the Skins.xml. If you want, I can write a quick XSLT that could be used to translate to what AM needs or vice versa.

[Old Dog]

You could with an XSLT automate the creation of the Skin.xml that Appearance Manager requires based off the Skins.xml. If you want, I can write a quick XSLT that could be used to translate to what AM needs or vice versa.

Where did all this new modern stuff come from?

Sounds good to me King, but l need awhile to get something implemented first. Then I'll have a better idea of what's needed.