cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leo Yang <leoyang.web...@gmail.com>
Subject Re: [Android] Not so fast....API changes in Cordova-Android for Pluggable WebView
Date Fri, 02 May 2014 15:17:04 GMT
Since you talked about plugin so do you plan to introduce/merge xwalk
extension mechanism to Cordova plugin mechanism?

Thanks,
Leo


On Wed, Apr 30, 2014 at 12:23 PM, Joe Bowser <bowserj@gmail.com> wrote:

> Hey
>
> So, once again, we're dealing with some major API changes once we
> introduce pluggable webview.  The first change that was done for
> sanity was finally deprecating setProperty.  This was slated to be
> removed by 3.5 or in six months from the deprecation date, but we kept
> it in too long.   While I would like to assume that everyone has moved
> over to setting their preferences in config.xml, which is the much
> more sane way of doing things, we can't do that.  We need to publicize
> this in some blog posts, as well as in our documentation somehow.
> There will obviously be some pissed off users, as we've seen in past
> posts, but I think having the ability to use a WebView other than
> Chrome 30 is worth these changes.
>
> The other change, which says more about our design is adding a getter
> method for pluginManager.  We need to access the pluginManager to get
> plugins, and it's expected that everyone who implements a
> CordovaWebView will have this method produce a pluginManager.  In the
> past, it was just publicly exposed, which was not the greatest idea
> and was kinda sloppy.
>
> So, how do people want to handle these changes?  We constantly get
> shit for changing our API when we do development, but I do think these
> improvements are extremely important, especially given how much flak
> we get for relying on Android's WebView.
>
> Thoughts?
>
> Joe
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message