My patch is backwards compartible. Now, it maps the new specification to the old one. This isn't a good solution. I have only done the work to mapping the old specification to the new or the other way around. For the future it would be better to support the new specification and support only one format that's back compatible. I tested the solution on Vbox 2.0.4 and VBox 2.10 and in both cases the patch worked. My second patch fixes all my newbie faults with gnome-do plugins.
PS: There is an problem in my mapping list. I have "netware" twice in the Dictionary. This will give you an error during initialization of the VMItem object. I haven't tested my code before i sent the bug report. I had to figure out who to add a additional self compiled component to the plugin system. I'd like revers engineering. BTW: Is there an specification of the plugin interface? I also made the fault, that I choose the "lp:~cszikszoy/do-plugins/vbox" branch and not the official one. My patch is of little value. The only thing you can use is the Dictionary and the optimization with Path.Combine (no need of hacky string converting and replacement). ** Attachment added: "VirtualBox_second.bundle" http://launchpadlibrarian.net/21888894/VirtualBox_second.bundle -- Virtualbox Icon in 2.10 are broken because of an new specification https://bugs.launchpad.net/bugs/323902 You received this bug notification because you are a member of GNOME Do Plugins Team, which is subscribed to GNOME Do Plugins. _______________________________________________ Mailing list: https://launchpad.net/~do-plugins Post to : [email protected] Unsubscribe : https://launchpad.net/~do-plugins More help : https://help.launchpad.net/ListHelp
