Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of dave.c.johnson@gmail.com
 designates 209.85.215.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CABaSBazA-YNeAX_ELBe8unHYiCfrGTK=vMAuD16gJg-q6HSw7g@mail.gmail.com>
References: 
 <CAOR1Ze9sNa4TMA5vVCEzFkdfoQLzzA_aOVRhM_0Sih2HMeBi5g@mail.gmail.com>
 <CACAoQH2Ei2K-L9UZKr3JS1gpkjEmLDjBUW-KMz6QSQoQ80ckng@mail.gmail.com>
 <CAOR1Ze-3fGavrMEC7EnBMd_yZGZw-sM1qjgbrnnrUBbvj+SKbQ@mail.gmail.com>
 <CABaSBazA-YNeAX_ELBe8unHYiCfrGTK=vMAuD16gJg-q6HSw7g@mail.gmail.com>
From: Dave Johnson <dave.c.johnson@gmail.com>
Date: Tue, 22 May 2012 08:12:06 +1000
Message-ID: 
 <CADq=2H7T9re-CO_CSy3uDNjF7zSaXRgrm1P0VbE+UVYymKnL6g@mail.gmail.com>
Subject: Re: remote platform
To: callback-dev@incubator.apache.org
Cc: Julien Bouquillon <julien@revolunet.com>
Content-Type: text/plain; charset=ISO-8859-1

Hi Julien, I agree this sort of thing is needed - I also made a POC
doing the exact same thing with sockets so that I can write and debug
a phonegap app in chrome using desktop developer tools but getting the
actual device data so that I don't need to stub any data nor interact
with a simulator UI to control various stubbed data. I got stuck with
some issues around taking pictures and how the paths on the device map
to paths in the desktop browser, but it's not insurmountable.

I think it makes the most sense to have it work with ripple. For some
APIs like accelerometer it makes sense to get the data from the device
(it's easier to shake the device than simulate shake accelerometer
data) but things like geolocation make sense to be able to use the
actual geo data from the phone as well as stub data like a route or
something that you can't do easily with the actual device.

-dave

On Sat, May 19, 2012 at 3:25 AM, Bryan Bishop <kanzure@gmail.com> wrote:
> On Fri, May 18, 2012 at 11:49 AM, Julien Bouquillon
> <julien@revolunet.com> wrote:
>> I have to look at dnode as Bryan pointed out. I may learn a lot from this
>> project and it looks to fit quite well : remote exec, calls serialization...
>
> I encountered dnode when I was doing some work with phantomjs
> (headless webkit for scraping and ui testing). Unfortunately,
> PhantomJS doesn't have many ways to get data in/out of its process,
> because there are no compiled bindings yet.
>
> So, as a consequence, one way to get information out is through
> javascript on an open WebPage object. In particular, dnode is how the
> phantomjs-node people use this. See here:
>
> https://github.com/sgentle/phantomjs-node#no-really-how-does-it-work
>
> Both javascript debugging environments are equally painful :-). I
> haven't been able to get the phantomjs remote debugging bridge to work
> yet (I'm pretty sure it does, though), and weinre doesn't.
>
> - Bryan
> http://heybryan.org/
> 1 512 203 0507