Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of curtis.bryce@gmail.com
 designates 209.85.220.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CB98E8D5.31A9%fil@adobe.com>
References: 
 <CAOBL_k6tuCsHO+dnzqxfJsDzKpo6erVVReofmiaCa_ivptSWjA@mail.gmail.com>
	<CB98E8D5.31A9%fil@adobe.com>
Date: Wed, 28 Mar 2012 23:09:18 -0500
Message-ID: 
 <CAMT1KGO5PqLKEqRO1nZoTFkqefDeZTA0KtuoupD7UfQeWeTa+w@mail.gmail.com>
Subject: Re: [Android] CordovaWebView: Moving the CallbackServer and
 PluginManager out of DroidGap
From: Bryce Curtis <curtis.bryce@gmail.com>
To: callback-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=20cf3079bc9e48318404bc59e32b

--20cf3079bc9e48318404bc59e32b
Content-Type: text/plain; charset=ISO-8859-1

I really haven't had time to look at this in detail, but agree that
anything related to the webview should be in CordovaWebView.  As Fil
mentioned, that includes the history, plugin manager, whitelisting, &
authentication + callback server.

I assume that overriding chrome/view clients so the user can specify their
own will still work.

On Wed, Mar 28, 2012 at 6:17 PM, Filip Maj <fil@adobe.com> wrote:

> 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 CordovaWebView.java. 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.
>
> [1] http://wiki.apache.org/cordova/CordovaWebView
>
> On 3/28/12 4:06 PM, "Joe Bowser" <bowserj@gmail.com> wrote:
>
> >BUMP! Are we all on board with doing this?
> >
> >Joe
> >
> >On Tue, Mar 27, 2012 at 1:15 PM, Joe Bowser <bowserj@gmail.com> 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
> >>the
> >> Client before, and I'm wondering what people's thoughts are on that.
> >>Also,
> >> 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.
> >>
> >>
> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-android.git;a
> >>=shortlog;h=refs/heads/CordovaWebView
> >>
> >> http://wiki.apache.org/cordova/CordovaWebView
> >>
> >> Joe
> >>
>
>

--20cf3079bc9e48318404bc59e32b--