You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ripple.apache.org by Brian LeRoux <b...@brian.io> on 2014/06/05 22:57:53 UTC
Cordova <3 for Ripple
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?)
Re: Cordova <3 for Ripple
Posted by Brian LeRoux <b...@brian.io>.
Ya good point Ray…there would be small tweaks to the platform thing. We'd
really only want to rebuild Ripple itself if a plugin as added/removed.
Ideally the reload is transparent.
On Thu, Jun 5, 2014 at 2:04 PM, Raymond Camden <ra...@gmail.com>
wrote:
> "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 <b...@brian.io> 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 : raymondcamden@gmail.com
> Blog : www.raymondcamden.com
> Twitter: raymondcamden
>
Re: Cordova <3 for Ripple
Posted by Raymond Camden <ra...@gmail.com>.
"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 <b...@brian.io> 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 : raymondcamden@gmail.com
Blog : www.raymondcamden.com
Twitter: raymondcamden
Re: Cordova <3 for Ripple
Posted by Christian Grobmeier <gr...@gmail.com>.
Hi Brian,
I'm participating as asf mentor to this project. As you can see on the
lack of responses,
this project isn't very active. If Cordova actually has lot of love for
Ripple,
it should maybe consider to adopt it as sub project. Or, if preferred,
Cordova
committers can join this project as well. In any case, this email reads
as it
would be benefitial for Cordova committers to have direct access to the
Ripple source base as well.
And in my opinion, this is at the moment the only solution i can imagine
to prevent Ripple for being retired - its simply no activity here (or
almost).
That being said, I think Ripple becoming more integrated into Cordova
could
be benefitial for both projects.
Please be aware that there some issues to solve before the Ripple code
base can be
released, be it as sub project or on its own. In example, a few images
need to be
re-created.
I haven't looked into recent discussions on Cordova lists, but what are
the Cordova
guys feeling about helping/adopting this project?
Regards,
Christian
On 5 Jun 2014, at 22:57, Brian LeRoux 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?)