Give me a working URL and I can test for Android phones.
On Tue, Jul 21, 2009 at 10:46:53PM +1000, Simon Rumble wrote:
David Cantrell wrote:
This patch to the output of search.cgi adds a "find stuff within x metres of my current location" form if you are using a browser which supports the navigator.geolocation object.
Only tested on an iPhone.
Give me a working URL and I can test for Android phones.
http://www.cantrell.org.uk/david/private/
Incidentally, if you just type a distance into the box and hit enter it doesn't work, you need to click the Go link. That's because I didn't know how to create a form button that didn't just submit the form - it needs to do some Javascript magic first.
2009/7/22 David Cantrell david@cantrell.org.uk
http://www.cantrell.org.uk/david/private/
Incidentally, if you just type a distance into the box and hit enter it doesn't work, you need to click the Go link. That's because I didn't know how to create a form button that didn't just submit the form - it needs to do some Javascript magic first.
The fixed-width renders badly, and clicking [Go] gives me a 404 on /david/private/search.cgi
2009/7/22 Simon Rumble simon@rumble.net
2009/7/22 David Cantrell david@cantrell.org.uk
http://www.cantrell.org.uk/david/private/
Incidentally, if you just type a distance into the box and hit enter it doesn't work, you need to click the Go link. That's because I didn't know how to create a form button that didn't just submit the form - it needs to do some Javascript magic first.
The fixed-width renders badly, and clicking [Go] gives me a 404 on /david/private/search.cgi
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.
http://groups.google.com/group/android-discuss/browse_thread/thread/37ffb092...
Looks at the sample app, it doesn't look difficult and would be pretty easy to handle both methods: http://code.google.com/apis/gears/samples/hello_world_geolocation.html
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-a...
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-a...
I added a <script src=geometa.js></script> to my version, see if that works for you now.
On Wed, Jul 22, 2009 at 10:02:16AM +1000, Simon Rumble wrote:
2009/7/22 David Cantrell david@cantrell.org.uk
The fixed-width renders badly
I didn't make any layout-ish changes. I wouldn't know how to :-)
and clicking [Go] gives me a 404 on/david/private/search.cgi
Did you use the button for the top form, or the link that I used instead of a button for the form I added? You need to use the lower form.
David Cantrell david@cantrell.org.uk writes:
Incidentally, if you just type a distance into the box and hit enter it doesn't work, you need to click the Go link. That's because I didn't know how to create a form button that didn't just submit the form - it needs to do some Javascript magic first.
<form onsubmit="latlongform()"> and drop the .submit() call from your latlongform function.
openguides-dev@lists.openguides.org
-
David Cantrell -
ilmari＠ilmari.org -
Simon Rumble