incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filip Maj <>
Subject Re: [Android] CordovaWebView: Moving the CallbackServer and PluginManager out of DroidGap
Date Wed, 28 Mar 2012 23:17:02 GMT
Sorry for late reply Joe!

Looks great! As for outstanding issues as per your wiki article [1], I
would say move everything WebView related, as well as Cordova-specific
such as the plugin manager, into My thinking here is
that, none of scaffolding necessary to enable device APIs in the web view
should be a burden on the user - the CordovaWebView class should handle
all of that.

It separates the cordova-y bits as something the WEbView needs to manage
on its own, as well, and cleans up the final Activity-extending class to
be simpler. Our end users should not have to worry about that stuff, nor
do they need to see it in their own activities, or the generated
activities the baseline tooling within cordova-android provides.

IMO: history, plugin manager, whitelisting, authentication, should all be
handled by CordovaWebView.


On 3/28/12 4:06 PM, "Joe Bowser" <> wrote:

>BUMP! Are we all on board with doing this?
>On Tue, Mar 27, 2012 at 1:15 PM, Joe Bowser <> wrote:
>> Hey
>> I've been working on the CordovaWebView branch, and I think we need to
>> discuss where to put the CallbackServer and PluginManager in the new
>> implementation.  I'm OK with it being in the view, but I did have it in
>> Client before, and I'm wondering what people's thoughts are on that.
>> since these are core pieces of Cordova on Android, this may break the
>> branch, which is fine, but it'd be good if more people looked at this
>> branch, and discussed how this should work.
>> Joe

View raw message