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?)
