Plugin Conversion - Leg-up Please!

[JohnHind]

Any plugin developers give me a leg-up to get started on converting my Girder 3 plugins to Girder 4? I know there are lots of exciting new possibilities like the DUI, but what's the minimum necessary and can a plugin work in both G3 and G4 or do we need a code fork?

I loaded my Mouse plugin in Alpha 20 - it seems to start up OK and the Settings dialog seems to work fine. Also its events show up in the new built-in logger. However there the good news ends! The plugin does not appear on the Actions expando, so I can see no way of adding its action to the tree, or presenting its Action UI. Also, it does not appear on the Event Properties editor as an Event Device and nor are its events recognised by the Learn function.

Anyone who's been this way already give me a quick helping hand?

[birty]

the minimum conversion needed is the dui, see the sticky at the top for examples. girder 3 plugins are completely incompatible and need sepearte code, however this could be achieved using conditional compiler directives rather than having two completly different sets of code

[JohnHind]

Thanks for speedy, if not very encouraging, response. I kind of had the impression that basic compatability would be OK, but maybe integration would be sub-optimal (i.e. Action Editor appearing in its own window rather than inside G4). The very short list of incompatible plugins above definitely suggests this.

[Promixis]

John,


Action plugins will work without change. But if you had any menu stuff (apart from the setup) you will need to use the DUI.

Ron or I can get you some source if the examples here aren't enough.

[JohnHind]

Thanks Mike - I'll dive into the two examples above and see how far I can get. I'll contact you directly if I need anything further.

[birty]

to clarify what i meant in my post, most girder 3plugins will work in girder 4 but once you have converted your plugin to work fully with girder 4 it probably wont still work with girder 3