Right, it doesn't exist yet (no one's picked up working on it). +Brian made the original pitch for it, but my understanding is that it is meant to be adding first-class support for testing Cordova apps in the browser, but do so by being a fully-supported cordova platform.
Another way to look at this is to say that there's already a place for Ripple to go within Cordova. The core logic should go into cordova-browser. Plugin logic should go into each plugin repo under the "browser" platform. And the bridge interception piece should go into cordova-js. If there is still need for a ripple server after all of this, then that belongs inside of cordova-cli. On Sat, Apr 26, 2014 at 11:17 AM, Ray Camden <[email protected]> wrote: > I am naturally inclined to *not* leave Ripple as I think it is a great > tool, but I'll check out cordova-browser. You say it is very similar to > Ripple, but where exactly is it? The github repo is mostly empty now. > > ________________________________________ > From: [email protected] <[email protected]> on behalf of Andrew Grieve < > [email protected]> > Sent: Thursday, April 24, 2014 3:17 PM > To: dev > Subject: Re: [Discuss] The Future of Ripple as a Top Level ASF Project > > For those passionate about Ripple, I'd like to try and woo you to two > other avenues, as I don't see Ripple in the Cordova workflow in the > future. > > cordova-app-harness for on-device testing (this is essentially the > same as PhoneGap Developer App) > cordova-browser CLI platform for local in-browser testing (very > similar to Ripple, but fully supported by CLI & works with plugins in > a generic way) > >
