ripple-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From JR <jro...@gmail.com>
Subject Re: Can I run ripple as a chrome extension in future?
Date Tue, 05 Nov 2013 08:23:16 GMT
in 3.0 you save a lot of hassle by using ripple and Cordova together as
ripple emulate does Cordova prepare to build the plugins and .json file. If
you're using Cordova 3, you pretty much have to have Cordova CLI.


On Tue, Nov 5, 2013 at 2:40 AM, lmnbeyond <lmnbeyond@gmail.com> wrote:

> Hi,
>
>     Are there any inter-dependencies between ripple cli and cordova cli ?
> If so, I tend to believe that “Running as a chrome extension” still has
> value. In some cases, users probably won’t install cordova cli.
>
> Best Regards!
>
>
>
> On 2013年11月5日, at 上午7:32, Ken Wallis <kwallis@blackberry.com> wrote:
>
> > Apologies for the lack of progress on the Chrome extension. We had a
> > number of hurdles trying to remove the dependency on the Heroku instance.
> > We plan to release an update very soon to remove the Heroku instance and
> > that we free us up to donate the Chrome extension to the Apache project.
> > However, does the community still see value in that given the current
> > direction?
> >
> > --
> > Ken Wallis
> > Senior Product Manager - WebWorks
> > BlackBerry
> > 650-620-2404
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: Gord Tanner <gtanner@gmail.com>
> > Reply-To: "dev@ripple.incubator.apache.org"
> > <dev@ripple.incubator.apache.org>
> > Date: Saturday, November 2, 2013 at 5:35 PM
> > To: dev <dev@ripple.incubator.apache.org>
> > Subject: Re: Can I run ripple as a chrome extension in future?
> >
> >> The main problem is that when BlackBerry acquired tinyHippos and Ripple
> >> they acquired the Chrome Extension as well.
> >>
> >> I don't think BlackBerry is really involved with Ripple anymore (any
> >> BlackBerry people can speak up on the list if this isn't the case) and
> >> they
> >> own the keys to deploying the extension.  We asked them to release a
> >> version a few months ago but didn't get a reply back and didn't release
> >> it.
> >>
> >> We actually get more functionality with the npm package and gain the
> >> ability to load ourselves in other browsers as well, and the injection
> of
> >> ripple and the API's is no longer as hacky as it was with the chrome
> >> extension.
> >>
> >> I actually just removed the chrome extension from the open source
> project
> >> to start simplifying things.
> >>
> >>
> >>
> >>
> >> On Fri, Nov 1, 2013 at 3:20 AM, lmnbeyond <lmnbeyond@gmail.com> wrote:
> >>
> >>> Hi,
> >>>
> >>>    First of all, I would like to express my deepest gratitude for the
> >>> amazing work you guys have done!
> >>>
> >>>
> >>>    I noticed that ripple has moved to Apache, so what's the plan for
> >>> ripple?
> >>>
> >>>    I think it's very thoughtful that we can use ripple via cli, but
> >>> what
> >>> will happen to the chrome extension? Will the both do coexist? Or
> ripple
> >>> can only be invoked by cli, running as a chrome extension will not be
> >>> supported in future?
> >>>
> >>>
> >>> Best Regards!
> >
> > ---------------------------------------------------------------------
> > This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-public
> information. Any use of this information by anyone other than the intended
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be unlawful.
> >
>
>


-- 
Jonathan

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message