There is an interesting nugget here. Maybe there should be things like ./platforms/ripple (and ./platforms/chrome-packaged-app
??? makes sense to me. On Mon, Jun 10, 2013 at 1:42 PM, Michal Mocny <[email protected]> wrote: > - App-harness is 99% just plain serving of files with these constraints: > - The folder to server is the *platform specific* www output "artifact" > (ie, after www/ and merges/ and plugins mush together) > - The final config.xml file is in a special location outside that folder, > and is handled specially right now (the config.xml inside www/ is the wrong > one, its the app manifest, we really do need to rename these two configs) > - Finally, in order to have true edit-refresh, we would like to support > 'grunt watch' like functionality and re-run prepare step, upon modification > of app web assets (and plugin web assets?) > > Also, if Ripple is one client, App-Harness is another client, and > potentially we have more clients (i.e. maybe just your mobile browser), > while I agree to consolidate, perhaps we shouldn't call the command > 'ripple' but something generic, like leaving it 'serve'. > > -Michal > > > On Mon, Jun 10, 2013 at 4:29 PM, Filip Maj <[email protected]> wrote: > >> My view is that both `ripple` and `serve` do essentially the same thing: >> host local assets for viewing/editing/testing in a browser. Essentially >> enabling that fast edit/refresh cycle without have to compile/redeploy to >> a device every time. And as Gord chimed in, current `cordova ripple` >> relies to a degree on `serve`. >> >> Definitely do NOT want to eliminate the ability to do edit/refresh. >> Rather, we have two fairly buggy implementations that I would like to see >> consolidated and fixed. DEFINITELY want to have good integration with the >> app harness. I have yet to play around with it, actually, to my shame. >> Michal are there any specific things necessary for the app-harness other >> than a local server? >> >> On 6/10/13 1:23 PM, "Michal Mocny" <[email protected]> wrote: >> >> >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 <[email protected]> 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 < >> [email protected] >> >> >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 <[email protected]> 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" <[email protected]> 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 >> >><[email protected]> >> >> > > >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 >> >> > > >><[email protected] >> >> > > >> >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 <[email protected]> >> >>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" <[email protected]> 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 <[email protected]> >> >> > 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" <[email protected]> >> >>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 >> >> > > >><[email protected]> >> >> > > >> > > >>>wrote: >> >> > > >> > > >>> >> >> > > >> > > >>>> Thats awesome ;) >> >> > > >> > > >>>> >> >> > > >> > > >>>> >> >> > > >> > > >>>> On Fri, Mar 22, 2013 at 3:51 PM, Gord Tanner >> >> > > >><[email protected]> >> >> > > >> > > >>>>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 < >> >> > > >> > [email protected]> >> >> > > >> > > >>>> 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 < >> >> > [email protected]> >> >> > > >> > 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 >> >> > > >> > > >>>><[email protected]> >> >> > > >> > > >>>> > 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 < >> >> [email protected]> >> >> > > >> 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 >> >> > > >> > >> >> > > >> >> >> > > >> >> > > >> >> > >> >> >> >>
