Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1C43111C63 for ; Thu, 24 Apr 2014 14:23:22 +0000 (UTC) Received: (qmail 60253 invoked by uid 500); 24 Apr 2014 14:23:16 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 60213 invoked by uid 500); 24 Apr 2014 14:23:15 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 60200 invoked by uid 99); 24 Apr 2014 14:23:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Apr 2014 14:23:15 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rgerbasi@gmail.com designates 209.85.212.176 as permitted sender) Received: from [209.85.212.176] (HELO mail-wi0-f176.google.com) (209.85.212.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Apr 2014 14:23:09 +0000 Received: by mail-wi0-f176.google.com with SMTP id r20so1153424wiv.15 for ; Thu, 24 Apr 2014 07:22:48 -0700 (PDT) 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 :content-type; bh=2kwOj5kjYV4SOPWP4fgXTNWLtxeEkimZ4V23DiWGao0=; b=ss8NLc+ktTZcrHIt3Gitp2sCJqhQpxTVMxk01TuWkgCkIxSJwJaR4yvfACeTLmmF3c gaMbVVLW0LywIUus8XTLXRtESGjVHn9bRdE3fqXMkgJijAh4p6XXbIio2n2QK1sXxbyF yVPT/hA6kBhq/lsZ5s2r8qV0lIziDMbyiEyzcPryX11P17jfwLVI5mj2fQ/IzX9nm/sG uEL8G4BZKZrStqETQURSvab6LHrvlP+K//4FalqUGPMB9OaPPC4+CQ+kE9kuFK0iCY1m xoX8LKwQsj05uE7xv07ivsWHrvXGXNvJf/Enp7gCsRITBAmKNSRXDs5gXwBM8W36oPCT xbfA== MIME-Version: 1.0 X-Received: by 10.194.87.163 with SMTP id az3mr1912569wjb.63.1398349368616; Thu, 24 Apr 2014 07:22:48 -0700 (PDT) Received: by 10.194.216.170 with HTTP; Thu, 24 Apr 2014 07:22:48 -0700 (PDT) In-Reply-To: References: Date: Thu, 24 Apr 2014 07:22:48 -0700 Message-ID: Subject: Re: [Discuss] The Future of Ripple as a Top Level ASF Project From: Ross Gerbasi To: dev Content-Type: multipart/alternative; boundary=089e010d8814636f9604f7ca954a X-Virus-Checked: Checked by ClamAV on apache.org --089e010d8814636f9604f7ca954a Content-Type: text/plain; charset=UTF-8 I am also into this idea and would totally be into working on code to make that happen. Seems like we could just come up with a simple structure a plugin could follow to provide emulation in the browser? This could be through some UI panel or just simple dummy data being returned from calls. The plugin could really make that call. If we do go this route maybe we could rethink how ripple is integrated into the workflow? Is it possible to just make it another platform? Lastly now that Chrome has much stronger emulation support could we lean on it for Device, Screen, User Agent and basic sensor emulation then just have ripple (or this new platform) deal with cordova specific calls and plugins? On Wed, Apr 23, 2014 at 6:58 PM, Anis KADRI wrote: > On Wed, Apr 23, 2014 at 8:41 AM, Parashuram Narasimhan (MS OPEN TECH) < > panarasi@microsoft.com> wrote: > > > On a side note, does it make sense to make Ripple another platform, just > > like iOS, Android or Windows? Given that a lot of people use Ripple in > > projects that also have plugins, it may make sense for plugins to atleast > > provide some sort of mock data for Ripple, making Ripple useful with > > plugins that are not already supported. > > > I like this idea. I like the idea of folding it into Cordova. > --089e010d8814636f9604f7ca954a--