W3C home > Mailing lists > Public > public-geolocation@w3.org > June 2008

Re: skeleton Geolocation API

From: Doug Turner <doug.turner@gmail.com>
Date: Fri, 20 Jun 2008 20:34:26 -0700
Cc: "Ryan Sarver" <rsarver@skyhookwireless.com>, "Andrei Popescu" <andreip@google.com>, "public-geolocation@w3c.org" <public-geolocation@w3c.org>
Message-Id: <007B5FD2-6ACC-40EB-B797-B0C335E60130@gmail.com>
To: Aaron Boodman <aa@google.com> 

On Jun 20, 2008, at 8:13 PM, Aaron Boodman wrote:

> On Fri, Jun 20, 2008 at 8:09 PM, Doug Turner <doug.turner@gmail.com>  
> wrote:
>> nsIDOMNavigatorGeolocator would be implemented by the navigator  
>> object.
>>
>> nsIDOMNavigatorGeolocator provides access to an attribute called
>> 'geolocator' which implements a nsIDOMGeolocator.
>>
>> From here, you can do something like:
>>
>> navigator.geolocator.
>
> Isn't this the same as the draft, save the name "geolocator" instead
> of "geolocation"?
>
> - a

Right, no differences other than naming.

To me, geolocation == position.  Something that gives me a geolocation  
is a geolocator.

Doug
Received on Saturday, 21 June 2008 03:36:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 18:13:29 GMT