It SHOULD be its own thing. InAppBrowser should always use the default Chromium present, and having customizable webviews in a plugin in a world where webviews are a plugin sounds like a recipe for disaster. I would be interested in seeing how dependency management could be dealt with in a post 4.0.x future, since someone would probably want to have Crosswalk for their default renderer and for the third-party webview.
On Thu Feb 05 2015 at 3:38:33 PM Brian LeRoux <[email protected]> wrote: > could be its own thing but if it came under the actual inappbrowser that'd > be cool too > > https://github.com/apache/cordova-plugin-inappbrowser > > > On Thu, Feb 5, 2015 at 3:25 PM, Sidney Bofah <[email protected]> > wrote: > > > Hi all, > > > > my company recently required the availability of a high-performance > > Android modal WebView (that is, Chromium-based, disposable, free of > memory > > leaks, etc.) in context of a Crosswalk-based Cordova/Ionic project. My > > research had shown that the widely used InAppBrowser plugin has not made > > any progress or attempts in terms of being extended (or migrated) towards > > using the XWalkView stuff yet. However, as the container app already > > employed Cordova-Crosswalk, this seemed counterintuitive. Solutions such > as > > the Cocoon "WebViewPlus" were too opaque. > > > > As a solution, i devised a version of the plugin that uses Crosswalk > > (13/Canary) as its rendering engine, with a dependency on the > > "cordova-engine-crosswalk" project (the host project is based on Ionic). > In > > this context, it was required to migrate its legacy WebView architecture > to > > Chromium. The results are promising this far, and could possibly benefit > > many Android apps using rendering-intensive, temporary webviews. > > > > Currently, the code lives in a private repository, but is to be open > > sourced. My questions are: Which project, branch, repo etc. would be the > > correct context for contributing? > > > > Cheers, > > Sidney > > ------ > > https://github.com/sidneys > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
