From dev-return-88-apmail-ripple-dev-archive=ripple.apache.org@ripple.incubator.apache.org Thu Jan 3 22:16:04 2013 Return-Path: X-Original-To: apmail-ripple-dev-archive@minotaur.apache.org Delivered-To: apmail-ripple-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4A18DE94A for ; Thu, 3 Jan 2013 22:16:04 +0000 (UTC) Received: (qmail 73621 invoked by uid 500); 3 Jan 2013 22:16:01 -0000 Delivered-To: apmail-ripple-dev-archive@ripple.apache.org Received: (qmail 73596 invoked by uid 500); 3 Jan 2013 22:16:01 -0000 Mailing-List: contact dev-help@ripple.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ripple.incubator.apache.org Delivered-To: mailing list dev@ripple.incubator.apache.org Received: (qmail 73552 invoked by uid 99); 3 Jan 2013 22:16:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jan 2013 22:16:01 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of brent.lintner@gmail.com designates 209.85.220.178 as permitted sender) Received: from [209.85.220.178] (HELO mail-vc0-f178.google.com) (209.85.220.178) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jan 2013 22:15:54 +0000 Received: by mail-vc0-f178.google.com with SMTP id l6so2076675vcl.23 for ; Thu, 03 Jan 2013 14:15:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WtWWxkpW/SEbsr6v+6QGVw3th7l+YxVsJbAdtv8BGLY=; b=x91P3SELbD89fL56TL26iZIRxhhMxfCSYrQTj72A3ISM+nayBeHo58rqhvHOJ5SXoI r2HaQ/lMcBVyibo+T5zz4EUC24LGi0Mc5cLbmJzQP2mvnn4Woka9W/lyWOgQA0itTXL4 JQoFym4/2CuVH8FkyCeI3LFyAiobqjnTUQTL3tT6aJpq6/9tH9UYDHkFmRl309HARLYR VKygjY4m+hrzxFRLJyMnl2MUacEyimS4jurvnP2GCiYOho5afF+tqmYJXqWU/JEyZm7H w2jLesGNHV5aHAwvuzJWudMl9ohzvefTB04zv56Gg6+Ib4toYWFN9VX4L67Sm3/aTje0 VP9g== MIME-Version: 1.0 Received: by 10.52.20.238 with SMTP id q14mr65413217vde.120.1357251333603; Thu, 03 Jan 2013 14:15:33 -0800 (PST) Received: by 10.58.4.170 with HTTP; Thu, 3 Jan 2013 14:15:33 -0800 (PST) In-Reply-To: References: Date: Thu, 3 Jan 2013 17:15:33 -0500 Message-ID: Subject: Re: Looking for feedback from the group From: Brent Lintner To: dev@ripple.incubator.apache.org Cc: "callback-dev@incubator.apache.org" Content-Type: multipart/alternative; boundary=20cf307c9b2a9c431d04d269b376 X-Virus-Checked: Checked by ClamAV on apache.org --20cf307c9b2a9c431d04d269b376 Content-Type: text/plain; charset=UTF-8 Hey All, Just a quick update not that some of the commit messages referenced directly (from the Pull Request) may have changed (i.e. been rebased), in case you are wondering why they do not work anymore (if anyone is still checking out this thread, that is). :-) (pull request link again) -> https://github.com/blackberry/Ripple-UI/pull/650 On Mon, Dec 17, 2012 at 3:45 PM, Dan Silivestru wrote: > Hi Cordova and Ripple communites, > > As some of you might know, we had a great hack session with some of the > good folks at Adobe this past week in Whistler. I wanted to email the group > here to update everyone on the progress made and to ask for comments / > feedback. > > Please keep in mind that this is still in prototype stage and things will > likely change based on feedback and future work. > > The work was primarily done on Ripple and geared towards the > Cordovadeveloper crowd. The two features implemented are as follows: > > *Device Proxy*: > > Allowing both Ripple and a device running a new Ripple companion app to > connect to a socket server (part of Ripple CLI). This will result in all > api calls (such as the accelerometer api) made by the mobile app inside > ripple to be proxied directly to the connected device running the companion > app. Basically making it such that your application is running in ripple, > but all data will be coming from the connected device. Here are links to > the repos and branches involved. > > Ripple device proxy branch: > https://github.com/tinyhippos/Ripple-UI/tree/device.proxy > Ripple companion app: https://github.com/gtanner/ripple-companion > > *How to get this stuff running?* > > Pretty straight forward. > > - Get ripple setup > > git clone git@github.com:tinyhippos/Ripple-UI.git > cd Ripple-UI > git checkout device.proxy > ./configure > jake > > - install the CLI (from the Ripple-UI dir) > > npm install -g . > ripple > > OR > > ./bin/ripple > > - load ripple as unpacked extension into Chrome (if not using Hosted > Ripple), more details here: > > https://github.com/tinyhippos/Ripple-UI/blob/next/README.md#running-as-a-chrome-extension > - compile and install the companion app (if you want to play with Ripple > Device Proxy) > - Run the following command over a directory that contains your app > > ripple emulate --path > > - Open http://localhost:4400 and enable Ripple (probably still best to > use Chrome for now) > - Open the Device Proxy ui panel > - Pair the Ripple companion app with the socket serve > > > *Hosted Ripple:* > > The feature removes Ripple's dependency on the Chrome Extension mechanism. > It gets kicked off from the CLI and essentially acts as a > man-in-the-middle. Allowing Ripple to run in most modern browsers (only > tested on Firefox and Chrome so far). > > Ripple hosted branch: > https://github.com/tinyhippos/Ripple-UI/tree/hosted.ripple > > > *How to run?* > > To run a local app, just read this commit message: > > https://github.com/tinyhippos/Ripple-UI/commit/81ed4ef7770e22f411bae9fc69bf2d4efe547a14 > * > * > To run a remobe app, just read this commit message: > > https://github.com/tinyhippos/Ripple-UI/commit/6961052a01aa2550b2f5a4c234cc746ddc88d876 > * > * > Also, we spoof the userAgent header with hosted ripple to ensure we get > proper mobile content from loaded sites. Commit with comments here: > > https://github.com/tinyhippos/Ripple-UI/commit/9a10a8833706bcdb54663b70bb5dbf7d7b887c8e > > > * > * > Last by not least, Brian Higgins spent quite a bit of time on the Mobile > Spec app for BB10 and managed to kill about 80+ failing specs. Figured this > was a good time to introduce Brian to the group (cc'd here) :-) > > Really looking forward to people's comments / thoughts on these features > and our approach. > > Thanks in advance, > > -- > Dan Silivestru > -- Brent --20cf307c9b2a9c431d04d269b376--