Very neat idea. My gut is that it would be useful only to a small set of device-sensor-heavy apps, but probably will be quite useful to them. Also useful would be a way to record & playback calls over the exec() bridge.
How to implement it is a good question though. Seems like it might be enough to have a custom app template that people could use to build their "remote" apps (e.g. cordova create --template=remote-app). The hijacking of exec() could be done as a plugin you add to your project maybe? On Thu, Nov 7, 2013 at 11:55 AM, Julien Bouquillon <jul...@revolunet.com>wrote: > Hi there, > > Ive submitted the idea a while > ago<http://markmail.org/message/cqpy7f5wqba4emed> on > the cordova ML and now that the cordova codebase is much more sane and > promises-based API are on their way we can put the subject back the > discussion table ;) > > Basically, it would be very handy and timesaving for developers to be able > to call the real devices APIs right from their dev environnement (chrome > desktop for me), using a kind of "proxy". > > Both @gordtanner and i have prototyped something related a bit some time > ago : > https://github.com/gtanner/ripple-companion > https://github.com/revolunet/remote-cordova > > Some ideas : > - implement a "remote" platform in cordova that would be configurable > using a custom host:post+password scheme. > - relay requests/responses using socket.io or similar; maybe @substack > dnode project could help here. > - create basic native apps with a webview and a "runner" that just execute > API calls and return responses. > > I'm not sure if it can be done with a custom cordova "platform" only or if > this is more a ripple module. > > This could allow developers to dev the whole app JS code in their desktop > directly. Only the UI will still need to be tested on real devices. > > > Thoughts ? > > > Thanks > > > Julien Bouquillon (@revolunet) >
