You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Drew Walters <pu...@gmail.com> on 2012/02/06 23:07:44 UTC
Cordova backwards compatibility issues with plugins on BB
I've made the name change from PhoneGap to Cordova in my local sandbox
but am running into issues trying to provide backward compatibility
with existing PhoneGap plugins. The issues are due to the BlackBerry
implementation having to define JSON classes since the BlackBerry
platform does not. This creates a nightmare because the JSON classes
define exceptions, pass back references to themselves and are used in
the IPlugin interface. So, injecting a new inheritance hierarchy that
is backwards compatible is non-trivial (/impossible). I've taken
several stabs at this over the last two days and haven't come up with
anything that actually works without existing plugin code having to be
modified.
Based on the fact that I have contributed the only three plugins
available on http://github.com/phonegap/phonegap-plugins/tree/master/BlackBerry
I'm thinking maybe I should just ignore plugin backward compatibility
for BlackBerry and just provide updates to the plugins I have
contributed.
Thoughts?
Also, do we have plans to have a cordova-plugins repository on github
somewhere or is it expected that the plugins at phonegap-plugins will
eventually be updated to Cordova?
Drew
Re: Cordova backwards compatibility issues with plugins on BB
Posted by Filip Maj <fi...@adobe.com>.
+1
On 12-02-06 11:27 PM, "Brian LeRoux" <b...@brian.io> wrote:
>My opinion is that since we are breaking plugins for sure its better
>to get that pain over with before we drop 2.x than later. In this
>particular case I think the path you describe (fix the plugins) is far
>better long term anyhow.
Re: Cordova backwards compatibility issues with plugins on BB
Posted by Brian LeRoux <b...@brian.io>.
My opinion is that since we are breaking plugins for sure its better
to get that pain over with before we drop 2.x than later. In this
particular case I think the path you describe (fix the plugins) is far
better long term anyhow.
On Mon, Feb 6, 2012 at 2:07 PM, Drew Walters <pu...@gmail.com> wrote:
> I've made the name change from PhoneGap to Cordova in my local sandbox
> but am running into issues trying to provide backward compatibility
> with existing PhoneGap plugins. The issues are due to the BlackBerry
> implementation having to define JSON classes since the BlackBerry
> platform does not. This creates a nightmare because the JSON classes
> define exceptions, pass back references to themselves and are used in
> the IPlugin interface. So, injecting a new inheritance hierarchy that
> is backwards compatible is non-trivial (/impossible). I've taken
> several stabs at this over the last two days and haven't come up with
> anything that actually works without existing plugin code having to be
> modified.
>
> Based on the fact that I have contributed the only three plugins
> available on http://github.com/phonegap/phonegap-plugins/tree/master/BlackBerry
> I'm thinking maybe I should just ignore plugin backward compatibility
> for BlackBerry and just provide updates to the plugins I have
> contributed.
>
> Thoughts?
>
> Also, do we have plans to have a cordova-plugins repository on github
> somewhere or is it expected that the plugins at phonegap-plugins will
> eventually be updated to Cordova?
>
> Drew