From david@cantrell.org.uk Wed Jul 22 13:43:06 2009
From: David Cantrell <david@cantrell.org.uk>
To: openguides-dev@lists.openguides.org
Subject: Re: [OGDev] Geolocation search patch
Date: Wed, 22 Jul 2009 13:43:01 +0100
Message-ID: <20090722124301.GG11997@bytemark.barnyard.co.uk>
In-Reply-To: <1234ca4a0907211708p6e59c2dbg421b0efa2612408e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1633840106182017913=="

--===============1633840106182017913==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Jul 22, 2009 at 10:08:31AM +1000, Simon Rumble wrote:

> Got myself a little more informed now and read the source.  Looks like this
> means navigator.geolocation doesn't work in Android's browser, and you have
> to do some Google Gears-specific nastiness to get the geolocation.

Yay, lets make up our own standard!  Thanks google!

> And it looks like someone has already done the legwork to make it work both
> ways:
> http://ajaxian.com/archives/navigatorgeolocation-using-the-w3c-geolocation-=
api-today

I added a <script src=3Dgeometa.js></script> to my version, see if that
works for you now.

--=20
David Cantrell | Minister for Arbitrary Justice

    "There's a hole in my bucket, dear Liza, dear Liza."
    "WHAT MAKES YOU SAY THERE IS A HOLE IN YOUR BUCKET?"


--===============1633840106182017913==--