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 392971073E for ; Mon, 10 Jun 2013 20:24:17 +0000 (UTC) Received: (qmail 5656 invoked by uid 500); 10 Jun 2013 20:24:17 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 5636 invoked by uid 500); 10 Jun 2013 20:24:17 -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 5628 invoked by uid 99); 10 Jun 2013 20:24:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Jun 2013 20:24:16 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FRT_ADOBE2,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mmocny@google.com designates 209.85.214.51 as permitted sender) Received: from [209.85.214.51] (HELO mail-bk0-f51.google.com) (209.85.214.51) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Jun 2013 20:24:13 +0000 Received: by mail-bk0-f51.google.com with SMTP id ji1so2790319bkc.38 for ; Mon, 10 Jun 2013 13:23:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=FVLZqyWiIAWFaKb4+5pLEFYHkfUpvln3xLYAA769Ut4=; b=COuSNAHx8fAM0ASxT9JqNk2QWBjaE7ybkiuraq38N3m7u8n3kbLC5+6rfBMYjfxraU frwnhYjRoV/Aa2Oam11zk8/hpZQMdG8OMoT+aHsELz9CnOwaO6NxpLDLHSUde8DNAY4A JebPVhK6ef6PPwcca953Pd4qSnyhZIzXQ2SW4771Cq3O/rAnFo3HGmv+9I115G7yTtLi ik1CxzWZXjkJYUAwm4zZ7wUQ0lLHLayOrpDhXSQ7Dr52Td+MEAIj/ThAI6dFqlXRDlpR LlX0SvJDtxkfTmYlJYwlobFhgqe6w2cg5oQ3FWsHSyDdfE60OHSatr3mVQNiccRj4igR eUcQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=FVLZqyWiIAWFaKb4+5pLEFYHkfUpvln3xLYAA769Ut4=; b=OQRFMwusIXXZ/ruMbwgNk+qNUybeDPjDk3w14NeyFoB/YRZb3LuShZZCgCF+DLumZ3 QcDh1ao2cpXa2jIOXa06s13GmtRxkmy6UdQ/Lip9BUTknsTY8d1tMUZ4UMIO8RzW1niE gD3vg9PBbmZc98jpfVRYIJ+cLR624Ie9NXcOk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :x-gm-message-state; bh=FVLZqyWiIAWFaKb4+5pLEFYHkfUpvln3xLYAA769Ut4=; b=TLSBkDd9fJlyWqpfyXCpiiQtNybg7oH6XDMxLX1tf0tCZQ9Ls/SEF6ndcDmzKl7mSb 8ORe4BamnmUqMWdY+HBX1VapckgBTKZ3gr3Cc6BBaOUpCDz20IJhfe86DwRkW9LlPRZn mTtZeP010F8dJqMP0JJX7iStFdMXYoDnqSId95qLYG8lvlyaEVmDpxbiID9SVgHkh/4p 8XVyAPqEPMK/kQPlyrnVkS0DiHgy294NGlHIW7qYkCmgzW5+RAdVL98EPq6PAuNoqs9a V3//W/SRejAlVqKEZGNl82PHGZemjU0I/pcDLD8gIxj+oS2qjNfc/kBUBUWwscyX1ORj TKyw== X-Received: by 10.205.13.194 with SMTP id pn2mr1810542bkb.76.1370895831535; Mon, 10 Jun 2013 13:23:51 -0700 (PDT) MIME-Version: 1.0 Sender: mmocny@google.com Received: by 10.204.50.78 with HTTP; Mon, 10 Jun 2013 13:23:31 -0700 (PDT) In-Reply-To: References: From: Michal Mocny Date: Mon, 10 Jun 2013 16:23:31 -0400 X-Google-Sender-Auth: HqAskP5ILItQU3KFVodzylfFGzY Message-ID: Subject: Re: [cordova-cli] ripple instead of serve To: dev Content-Type: multipart/alternative; boundary=20cf302237eb106d2b04ded28f9e X-Gm-Message-State: ALoCoQl/GY5zh/IivFV6Bc9wMKNv5BPRRv2wdevHdE4nTVHUItMZxhuCS+Dfd6ktcMqDXyFLXGDoLOxMj4mH8+aWDAxIvDnpiBGVKVexJqT9fVyMu+fdmzMizFuKNwkNCDjZw4v638YpffdYyDkAdUJ7nybrtxPvvJgQrk/oksSpwlQApk54Mj3IIu5OK0/lAxOEpb9a0Gje X-Virus-Checked: Checked by ClamAV on apache.org --20cf302237eb106d2b04ded28f9e Content-Type: text/plain; charset=ISO-8859-1 If the current 'serve' implementation needs axing, thats fine. However, curious if you are implying that 'ripple' will be the only way to do repid edit-refresh without rebuilding native components? We need a way to get app updates to a device running e.g. app-harness right? I thought that was the point of 'serve'. Is the proposal to remove the current implementation and re-add something functional later, or is the argument that we don't need a serve feature at all? -Michal On Mon, Jun 10, 2013 at 4:12 PM, Gord Tanner wrote: > +1 > > Currently the ripple command runs on top of serve [1] but should be really > easy to refactor. > > Once the integration is a bit more solid we need to start routing emulate > commands for unsupported platforms to ripple. > > [1] - > > https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;a=blob_plain;f=src/ripple.js;hb=HEAD > > > On Mon, Jun 10, 2013 at 4:03 PM, Braden Shepherdson >wrote: > > > +1 > > > > I hacked serve together in a couple of hours, and it is not in active > use. > > Corporate network environments are generally not open to your phone > > connecting directly to a serve running on your laptop or desktop, making > > 'serve' not very useful. > > > > Braden > > > > > > On Mon, Jun 10, 2013 at 2:25 PM, Filip Maj wrote: > > > > > HI GUYS! > > > > > > I'm reviving this thread :) > > > > > > There are a couple of issues filed for both CLI commands `ripple` and > > > `serve`. We've spoke in the past about axing `serve` in favor of > `ripple` > > > (see below in this thread). > > > > > > My suggestion: remove `serve` altogether in 3.0. There was consensus > for > > > this before but just wanted to loop back with folks to make sure this > > > sounded alright. > > > > > > Serve seems to be completely abandoned: the tests are currently > disabled > > > (and not passing), so I am in favor of closing the serve-related issues > > as > > > won't fix and suggesting people employ `cordova ripple` instead. > > > > > > On 3/23/13 7:15 AM, "Andrew Grieve" wrote: > > > > > > > > > https://uwaterloo.ca/engineering/events/first-robotics-waterloo-regional > > > > > > > >I was a score keeper last year (two years ago?) and it was super cool. > > > > > > > > > > > >On Fri, Mar 22, 2013 at 10:03 PM, Michal Mocny > > > >wrote: > > > > > > > >> Dan, my brother showed me this (he is mechatronics student at UW). > Is > > > >>it > > > >> still on tomorrow? > > > >> > > > >> > > > >> On Fri, Mar 22, 2013 at 6:41 PM, Dan Silivestru > > > >> > > >> >wrote: > > > >> > > > >> > +1 > > > >> > > > > >> > Sorry I'm late to the game, I was judging frisbee throwing, > pyramid > > > >> > climbing robots all day :-) > > > >> > > > > >> > https://twitter.com/confusement/status/315162754619162625 > > > >> > > > > >> > > > > >> > On Fri, Mar 22, 2013 at 6:35 PM, Filip Maj wrote: > > > >> > > > > >> > > K lets try to land it in 2.6.0rc1. There is still time Gord! > > > >> Blackberry + > > > >> > > iOS not tagged yet so we can land some more commits in > cordova-cli > > > >> > > > > > >> > > On 3/22/13 3:02 PM, "Brian LeRoux" wrote: > > > >> > > > > > >> > > >Like that plan. Say we proceed and land it in 2.6 to feel out. > > > >> > > > > > > >> > > >On Fri, Mar 22, 2013 at 2:50 PM, Filip Maj > > wrote: > > > >> > > >> I'm fine with removing server. In my mind ripple is just a > > serve > > > >> > command > > > >> > > >> on steroids. At this morning's meeting I believe some of the > > > >> Googlers > > > >> > > >> expressed concerns about axing out serve, so perhaps a > prudent > > > >>first > > > >> > > >>step > > > >> > > >> would be to add Ripple as an `emulate` command and then we > can > > > >>take > > > >> > baby > > > >> > > >> steps to extract out serve over the coming weeks. > > > >> > > >> > > > >> > > >> On 3/22/13 2:45 PM, "Gord Tanner" wrote: > > > >> > > >> > > > >> > > >>>Ripple is now ready to be integrated, currently I have it > added > > > >>as a > > > >> > > >>>seperate ripple command in a personal branch [1] > > > >> > > >>> > > > >> > > >>>Most of the work on Ripple was a much needed feature we knew > we > > > >> needed > > > >> > > >>>(Device Selection via query string [2]) as well as adding the > > > >> ability > > > >> > to > > > >> > > >>>serve content from multiple directories [3] (to support www/ > > > >>merged > > > >> > with > > > >> > > >>>platform/www/). > > > >> > > >>> > > > >> > > >>>Should I do the full remove serve and add this to emulate or > > > >>merge > > > >> > this > > > >> > > >>>in > > > >> > > >>>as is? (maybe remove serve in the meantime) > > > >> > > >>> > > > >> > > >>>[1] - https://github.com/gtanner/cordova-cli/tree/ripple > > > >> > > >>>[2] - > > > >> > > >>> > > > >> > > > > > >> > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-ripple.git;a=commitd > > > >> > > >>>if > > > >> > > >>>f;h=b36213d426700a3cc62b4701bc75806ff8539528 > > > >> > > >>>[3] - > > > >> > > >>> > > > >> > > > > > >> > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-ripple.git;a=commitd > > > >> > > >>>if > > > >> > > >>>f;h=2e483836bc5a24397ed002556f4209fac9508438 > > > >> > > >>> > > > >> > > >>> > > > >> > > >>>On Fri, Mar 22, 2013 at 3:54 PM, Michal Mocny > > > >> > > > >> > > >>>wrote: > > > >> > > >>> > > > >> > > >>>> Thats awesome ;) > > > >> > > >>>> > > > >> > > >>>> > > > >> > > >>>> On Fri, Mar 22, 2013 at 3:51 PM, Gord Tanner > > > >> > > > >> > > >>>>wrote: > > > >> > > >>>> > > > >> > > >>>> > Yeah Michal, > > > >> > > >>>> > > > > >> > > >>>> > That is the exact use case I had in mind. When we were a > > > >> startup > > > >> > we > > > >> > > >>>> > couldn't afford mac's so just used linux and ripple for > all > > > >>our > > > >> > > >>>>contract > > > >> > > >>>> > work and borrowed a friends macbook when we needed to > > > >>compile. > > > >> > > >>>> > > > > >> > > >>>> > > > > >> > > >>>> > On Fri, Mar 22, 2013 at 3:12 PM, Michal Mocny < > > > >> > mmocny@chromium.org> > > > >> > > >>>> wrote: > > > >> > > >>>> > > > > >> > > >>>> > > Very interesting. Combined with Bradens proposal to > > > >>support > > > >> > > >>>>pointing > > > >> > > >>>> to > > > >> > > >>>> > a > > > >> > > >>>> > > local platform, looks very good. > > > >> > > >>>> > > > > > >> > > >>>> > > Also note, offline isn't the only reason, platform > > support > > > >>on > > > >> a > > > >> > > >>>>given > > > >> > > >>>> > > machine as well: ie, can "test" iPhone (sorta) on a > linux > > > >>box > > > >> > > >>>>through > > > >> > > >>>> > > Ripple. > > > >> > > >>>> > > > > > >> > > >>>> > > > > > >> > > >>>> > > On Fri, Mar 22, 2013 at 2:15 PM, Brian LeRoux < > > b@brian.io> > > > >> > wrote: > > > >> > > >>>> > > > > > >> > > >>>> > > > omg I just realized this would fulfill offline use > case > > > >>vs > > > >> > lazy > > > >> > > >>>>load > > > >> > > >>>> > > > vendoring > > > >> > > >>>> > > > > > > >> > > >>>> > > > caching could be a future thing > > > >> > > >>>> > > > > > > >> > > >>>> > > > might be a really nice path > > > >> > > >>>> > > > > > > >> > > >>>> > > > On Fri, Mar 22, 2013 at 11:06 AM, Gord Tanner > > > >> > > >>>> > > > >> > > >>>> > wrote: > > > >> > > >>>> > > > > +1 > > > >> > > >>>> > > > > > > > >> > > >>>> > > > > With this I would want to add the ability to add a > > > >> platform > > > >> > > >>>>to a > > > >> > > >>>> > > project > > > >> > > >>>> > > > even if we don't have the build dependencies. > > > >> > > >>>> > > > > > > > >> > > >>>> > > > > Emulate would just default to ripple so is still > > > >>usable if > > > >> > we > > > >> > > >>>>can't > > > >> > > >>>> > > > build/deploy > > > >> > > >>>> > > > > > > > >> > > >>>> > > > > Sent from my iPhone > > > >> > > >>>> > > > > > > > >> > > >>>> > > > > On 2013-03-22, at 1:55 PM, Brian LeRoux < > b@brian.io> > > > >> wrote: > > > >> > > >>>> > > > > > > > >> > > >>>> > > > >> I think this bleeds back into other discussions. > It > > > >>was > > > >> > > >>>>mentioned > > > >> > > >>>> in > > > >> > > >>>> > > > >> the call earlier. I think some tacit agreement > that > > > >> ./serve > > > >> > > >>>>goes > > > >> > > >>>> > away > > > >> > > >>>> > > > >> and Ripple is the default ./emulate command. But > > lets > > > >> > > >>>>discuss. > > > >> > > >>>> (Just > > > >> > > >>>> > > > >> this. Lets keep thread focused.) > > > >> > > >>>> > > > > > > >> > > >>>> > > > > > >> > > >>>> > > > > >> > > >>>> > > > >> > > >> > > > >> > > > > > >> > > > > > >> > > > > >> > > > > >> > -- > > > >> > Dan Silivestru > > > >> > +1 (519) 589-3624 > > > >> > > > > >> > > > > > > > > > --20cf302237eb106d2b04ded28f9e--