Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of bowserj@gmail.com designates
 209.85.220.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAK_TSX+NThD-tpS_iRikNoAYG53RrH+XVCbk3wQusiaepbALeA@mail.gmail.com>
References: <-8004901042939693325@unknownmsgid>
	<CA+h2+t2f22Bo2TXe2pJ9gWX5BCYqO0Si8AvLeC4rpEX2yVZ0Lw@mail.gmail.com>
	<CAK_TSX+NThD-tpS_iRikNoAYG53RrH+XVCbk3wQusiaepbALeA@mail.gmail.com>
Date: Thu, 22 Aug 2013 10:49:44 -0700
Message-ID: 
 <CAOBL_k4C5-VA5G0C2E6n=yTO99kEPfFCRnCsk2o_G3390rEdHA@mail.gmail.com>
Subject: Re: Extending CordovaWebView
From: Joe Bowser <bowserj@gmail.com>
To: dev <dev@cordova.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Aug 22, 2013 at 10:43 AM, Ian Clelland <iclelland@chromium.org> wrote:
> After thinking about this for a couple of days, and discussing with Andrew
> and Michal here, it seem that there are definitely (at least) two different
> issues here.
>
>
> First is that there is no way to use a custom WebView / WebViewClient /
> ChromeClient class within the CLI system, without writing custom native
> code after your project has been created. This may be acceptable for
> individual project authors, but it's a pain for framework authors.
>

Can you explain why this is a pain? Also, what do you mean by
framework author? Do you mean us?

> Thinking some more, it is apparent that overriding templates is strictly
> more powerful, although it is only accessible to people who create lots of
> apps, and who would therefore have the incentive to create their own
> templates. I think I'm going to move forward with this path.
>

That makes sense. I think this is the better way to go, since the
Android modifications would probably need to be shared across apps
anyway.

> The second issue is how to allow plugins to listen for the (rather large)
> set of possible callbacks from these three classes. There are now a couple
> of cases where this has been asked: for gesture recognition, and now for
> basic auth. I have a couple of ideas as to how to let plugins register for
> these, without slowing down the WebView horribly, but I'm going to break
> that out into a separate thread for discussion.

Sounds good.