No I think we'll have to look a bit closer than that. I'll try and get a chance to look at it. Looks pretty simple and will be easy with a browser to test against. I'll get back to you with some code.
Apologies for top posting but watching Le Tour on the couch.
On Wed, Jul 22, 2009 at 11:21:39PM +1000, Simon Rumble wrote:
No I think we'll have to look a bit closer than that. I'll try and get a chance to look at it. Looks pretty simple and will be easy with a browser to test against. I'll get back to you with some code.
All I did was: wget -O index.html http://london.randomness.org.uk/search.cgi and then hack on the resulting page - the important bit to remember being to make the form submit to the right server. I suppose one day I should set OG up on my machine and run it properly ...
On Wed 22 Jul 2009, David Cantrell david@cantrell.org.uk wrote:
All I did was: wget -O index.html http://london.randomness.org.uk/search.cgi and then hack on the resulting page [...]
Small warning - RGL has a custom template for the search page, plus we're one version behind (Bob will upgrade us one day, I'm sure). Probably best to work on the svn versions rather than this.
Kake
Okay I've got a version that works with iPhone, Firefox 3.5, Chrome and the Android browser. A bit primitive, but it works. I've used jQuery because it's what I'm used to using (and it's awesome) and that geolocation shim that's supposed to make the Gears geolocation work in the standard way ( http://ajaxian.com/archives/navigatorgeolocation-using-the-w3c-geolocation-a... )
http://www.rumble.net/stuff/search.html
That shimdoesn't work properly though. For Android/Gears it returns .latitude or .longitude, while the standard is for .coords.latitude etc.
Will tidy up shortly but just want to demonstrate, and hopefully Android will support the standard in the next release, instead of this Gears weirdness.
On Mon, Jul 27, 2009 at 04:56:35PM +1000, Simon Rumble wrote:
Okay I've got a version that works with iPhone, Firefox 3.5, Chrome and the Android browser. A bit primitive, but it works. I've used jQuery because it's what I'm used to using (and it's awesome) and that geolocation shim that's supposed to make the Gears geolocation work in the standard way ( http://ajaxian.com/archives/navigatorgeolocation-using-the-w3c-geolocation-a... )
http://www.rumble.net/stuff/search.html
That shimdoesn't work properly though. For Android/Gears it returns .latitude or .longitude, while the standard is for .coords.latitude etc.
Will tidy up shortly but just want to demonstrate, and hopefully Android will support the standard in the next release, instead of this Gears weirdness.
Got a bit lost in this thread but if David or Simon would like anything merging the best way to get this done is file a ticket, with patch, in http://dev.openguides.org/
Thanks, Dominic.
openguides-dev@lists.openguides.org
-
David Cantrell -
Dominic Hargreaves -
Kake L Pugh -
Simon Rumble