incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leutwyler, Markus" <>
Subject RE: cordova-js webOS compass
Date Wed, 08 Aug 2012 14:34:37 GMT
I already do it similar to how the win8metro implementation is using,  basically overriding
getHeading with my own implementations. The problem is the following:

The way to get compass data on webOS is to add an event listener window.addEventListener("compass",...)
but that also means that I have to start and stop
the listener myself if I don't want it to keep running. The common plugin for accelerometer
keeps track of listeners and starting and stopping but the common
plugin for compass does not .. any ideas?


-----Original Message-----
From: [] On Behalf Of Gord Tanner
Sent: Mittwoch, 8. August 2012 16:01
Subject: Re: cordova-js webOS compass

The same is done on the playbook as we just use the device motion event:

On Wed, Aug 8, 2012 at 9:42 AM, Jesse MacFadyen <>wrote:

> Can you do something like this :?
> win8metro
> The pre-exec Accelerometer code is unchanged, and the results mapped back.
>  All overriding is done inside the 'proxy'.
> Cheers,
>   Jesse
> On 2012-08-08, at 5:14 AM, "Leutwyler, Markus" 
> <>
> wrote:
> Probably a question for Jesse
> I'm having a bit of trouble implementing the Compass functionality for 
> cordova.js webOS port
> The common plugins for Accelerometer and Compass differ in how the 
> call the native side.
> For webOS, the compass implementation is very close to what the 
> playbook implementation uses: window.addEventListener("compass",...)
> Can I overwrite/add to the functionality of the common plugin to make 
> this work?
> Markus

Gord Tanner
Senior Developer / Code Poet
tinyHippos Inc.

View raw message