On Thu, Aug 22, 2013 at 10:43 AM, Ian Clelland <[email protected]> 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.
