"Ideally, we could treat Ripple just like a platform compile target for Cordova" What worries me here is requiring the user to run a CLI for every change. (Not saying you mean that, but it *sounds* like you may.) Right now I can edit in www, reload in Ripple, and my changes are reflected. If I had to keep doing
cordova build ripple I'd probably not use Ripple. (And yeah, I could do some kind of Grunt task, but I'd still consider this a step back.) "Wherein `./emulate` would contain everything Ripple needs to render a UI and stub out any native calls" I love this idea. On Thu, Jun 5, 2014 at 3:57 PM, Brian LeRoux <[email protected]> wrote: > Hey everyone! It is no secret that Cordova has a lot of love for Ripple. > We're talking about bringing Ripple deeper into the CLI workflows we have > for Cordova. > > Ideally, we could treat Ripple just like a platform compile target for > Cordova. Part of this story is Cordova Plugins. Long ago, we discussed a > Cordova plugin having the following structure: > > ./ > |-doc > |-emulate > |-src > |-test > '-www > > Wherein `./emulate` would contain everything Ripple needs to render a UI > and stub out any native calls. This means that a platform build of Ripple > would be able to emulate the plugins, and only the plugins, that particular > project is utilizing. > > A few questions: > > - How does this sit w/ you as a Ripple community member? > - Is this insane? (Is there a better way?) > -- =========================================================================== Raymond Camden, Web Developer for Adobe Email : [email protected] Blog : www.raymondcamden.com Twitter: raymondcamden
