Hi Joe, > > Ningxin wrote: > > > > From crosswalk webview plugin perspective, several questions: > > 1. will the plugin be maintained by ASF/Apache > > (github.com/apache/cordova- > > crosswalk-engine) or Crosswalk team (github.com/crosswalk-project/ > > cordova-crosswalk-engine)? It will be a core cordova plugin maintained > > by ASF/Apache? > > > Joe wrote: > The ASF currently can't release this due to the complex licensing of > Chromium. Even though the MozillaView licensing story is a lot more > simplified, ideally it would be Intel and Mozilla who would maintain these > plugins, and not the ASF. Right now we're in PoC/Get two WebViews > working before releasing the feature stage! >
Understood. And I confirmed with Crosswalk team and the license process, it was cleared to host Crosswalk webview Cordova plugin under Crosswalk project. > > > 2. what the tests and criteria are expected for release? And by > > whom/infrastructure these tests are executed, ASF/Apache or Crosswalk > team? > > BTW, can someone point me the existing tests and infrastructure used > > in Cordova project? > > > > That's something that I want to talk about more on this list. Currently we > have only some JUnit tests for Cordova and MobileSpec, which has frankly > proven competely inadequate when testing even Cordova with the new > refactor there. It'd be good if we can figure out why they don't work on > Android > 2.3 at all. It makes it really hard to vote on releases when one the > platforms > we support can't run the tests we need. We REALLY need to talk about > testing a lot more, because we're severely lacking. > As you know, Crosswalk currently hosts a forked cordova-android and use Crosswalk webview inside that. For that one, we run Junit tests (but with some flaky tests) and mobile-spec tests for every crosswalk releases. When going to Crosswalk webview Cordova plugin, I think we should investigate and fix the flaky tests and run mobile-spec tests against cordova-android with the Crosswalk webview plugin. As our experience, some Cordova plugins assume the webview on Android is system webview, e.g. in-app-browser, it might break once using 3rd party webview. We might need some compatilibty tests for this. > > > 3. what is the release cycle of the plugin? Crosswalk itself has three > > release channels (canary, beta, stable) and 6 week release cadence. > > How to match the cordova plugin release cycles to them? > > > > > It's better if the crosswalk plugin matched the Crosswalk release channels > once it's ramped up. This is only possible if it's not bogged down by the ASF > release process of voting on everything. Choice is good, bureaucracy is bad. > I think it makes sense to release the crosswalk plugin against Crosswalk stable channel every 6 weeks. Any thoughts on above items? Thanks, -ningxin > > > Best regards, > > -ningxin > > > > > -----Original Message----- > > > From: Carlos Santana [mailto:csantan...@gmail.com] > > > Sent: Thursday, November 27, 2014 11:30 AM > > > To: dev@cordova.apache.org > > > Subject: Re: [Android] MozillaView Update: PoC is working > > > > > > Great news Joe. I agree with the time statement, post vacation time. > > > Allows time for doc, test, and logistics for release. > > > > > > Documenting some guides on what these two plugins means for > > > developer in terms of features, support and handling a single > > > project that wants to target Android 2.3 + Android 4.x. > > > Instrumenting test framework to test integration between > > > cordova-andoird and plugins. > > > Also discuss how the release cycle will work. Who owns what? > > > From what I little understand is that cordova-android remains ASF > > > and owned by Apache Cordova. But this cordova-android is a new > > > version that has an API to support plugins that replace the OS web view. > > > > > > The plugins are not owned by ASF/Apache Cordova, we just need to > > > document and support a stable API. And the gecko view plugin will be > > owned > > > by Mozilla outside ASF, and crosswalk owned by Intel outside ASF? > > > > > > > > > On Wed, Nov 26, 2014 at 7:58 PM, Ally Ogilvie <aogil...@wizcorp.jp> > > wrote: > > > > > > > >Thoughts? > > > > > > > > That. Is. Awesome. > > > > > > > > How far back can you target Android? > > > > > > > > > > > > On Thu, Nov 27, 2014 at 9:08 AM, Joe Bowser <bows...@gmail.com> > wrote: > > > > > > > > > Hey > > > > > > > > > > Just an update, I have a working PoC of the GeckoView-based > > > > > WebView ready for people to look at here: > > > > > > > > > > https://github.com/infil00p/cordova-mozillaview-engine > > > > > > > > > > This is definitely a very different webview than what we have > > > > > had currently, and I've had to re-think a lot of how we do > > > > > things with > > > > Cordova > > > > > because of it. The asynchronous bridge that uses promises is > > > > > very interesting on GeckoView, as well as how this is properly > sandboxed. > > > > > I like it a lot better than how Chrome based web-views are > > > > > currently > > > > working > > > > > with just bolting on an synchronous object. However, due to > > > > > time, and because I didn't want to repaint the bike shed again, > > > > > I kept the basic bridge architecture mostly intact. > > > > > > > > > > At any rate, from the initial tests, the bridge works and the > > > > > plugins are mostly intact. I override the exec with clobbers, > > > > > and while I haven't > > > > run > > > > > Mobile-Spec against the plugin version, the fact that it fires > > > > > tells me that the clobbers probably will work. > > > > > > > > > > I am really worried about the Splashscreen and how we show and > > > > > hide the webviews, since this was found to be very brittle when > > > > > I started to work > > > > on > > > > > this. We should consider having more proper refactoring of Cordova. > > > > > > > > > > At this point, now that we have two webviews, I think we should > > > > > ramp up > > > > for > > > > > a 4.0 final release in January 2015. I don't want to do it now > > > > > because I can see people getting pissed off that we released 4.0 > > > > > and then go on vacation. That said, I'm glad that this exists, > > > > > since it feels like > > > > we're > > > > > finally at the finish line with this feature. > > > > > > > > > > Thoughts? > > > > > > > > > > Joe > > > > > > > > > > > > > > > > > > > > > -- > > > > <http://www.wizcorp.jp/>Ally Ogilvie Lead Developer - MobDev. | > > > > Wizcorp Inc. <http://www.wizcorp.jp/> > > > > ------------------------------ > > > > TECH . GAMING . OPEN-SOURCE WIZARDS+ 81 (0)3-4550-1448 | > Website > > > > <http://www.wizcorp.jp/> | Twitter <https://twitter.com/Wizcorp> | > > > > Facebook <http://www.facebook.com/Wizcorp> | LinkedIn > > > > <http://www.linkedin.com/company/wizcorp> > > > > > > > > > > > > > > > > -- > > > Carlos Santana > > > <csantan...@gmail.com> > >
