Re: Position Heading Questions?

On Nov 17, 2008, at 5:32 AM, Andrei Popescu wrote:

> You are right, the definition is ambiguous and it needs clarifying.
> Right now, heading denotes the direction of travel so it is a property
> of the movement of the device.

Thanks.

> I completely agree that orientation would be useful but I have the
> following problem with exposing it in this API: orientation is
> completely orthogonal to position. So far, the spec is only concerned
> with the where on Earth a device is. How that device is oriented
> doesn't fit the current abstraction and, if we were to add it, it
> would break the API in subtle ways. For instance, it would no longer
> be clear when the watchPosition() callbacks would be invoked, so we'd
> probably need new methods (watchOrientation() ?), etc. This is the
> reason why most other APIs I've seen cleanly separate the two
> concepts:

Well, lat and long are completely orthogonal too! ;) I'm open to  
additional orientation callbacks, as I think that's how I'd implement  
it.

Thanks,
-- Greg