Thread: VisualDesigner for creating other skins

Great - now I have no excuse for making my own skins . Zorro, this is truly fantastic - thanks so much for doing this.

Skin on Garth

Forgot to put the link for the Skin.xml (which contains all elements to generate a skin.ini - the main skin of FP). Here it's: Skin.zip

And please don't forget to register VDFrodoPlayer.dll (with regsvr32 VDFrodoPlayer.dll) .

Here's a short instruction what you gotta do to get this VD version:

• Download and install the latest version of PhoneControl.NET if you didn't already (it's because there isn't a separate installer for VD available)
• Get the VD Update here http://phoco.net/tmp/__Bin/VDesigner.zip and copy it over the installed files.
• Unpack at least the FrodoPlayer or RoadRunner Export Provider and register the DLL with regsvr32 VDFrodoPLayer.dll / VDRoadRunner.dll (see post above)

Don't forget appliying the -Other{=FrodoPlayer/RoadRunner} option in the CommandLine to make a new skin other than for PhoneControl.NET.

Got the export-provider code to work
Instead of going through "real" xml code, I'm just replacing the syntax of the ini

erm... I had to change the Providers Interace for Initalize... now there is one additional array containing some user settings.

Please dowlnload the latest version and have a look... it's not complicated just the binary compatibility broke up.

Originally Posted by zorro

erm... I had to change the Providers Interace for Initalize... now there is one additional array containing some user settings.

Please dowlnload the latest version and have a look... it's not complicated just the binary compatibility broke up.

Well, I'm using the latest one, I think. The one that had the Frodo export code. That's the one I'm modifying.

Something quick I whipped up...

Well done, son.

Two things you have to care for:
1. Rename the FrodoPlayer Class to FrodoPlayerXML. Because these are COM objects that'll be address through their ProgId, you would cause malfunctions on computers with both Providers installed.
2. Also, if the output is another, rename the output file to something like "xx.ini.xml"

<edit>
You forgot to place a sourrounding root tag enclosing all other tags. Without your XML code will fail when loading in a DOM.
</edit>