Hehe, when I first saw "reverse geocoding" I read "reverse geolocation", as in you point to a spot on a Google map and you get teleported there.
Now *there's* a browser feature I'd pay for! jk On Thu, Jun 18, 2009 at 06:46:59PM +0300, Jesse Kivialho wrote: > Well I don't need that much events. The dragging doesn't have to emit an > event, just the final dragend (which already exists in the gmap2 project). > So the runtime would be more like: > > The end of dragging a marker should emit events (which it does) > The GCG should pick these up and reverse geocode the lat-long. (which I'm > atm doing with the server-side-geocoder) > The result should be shown in the browser (which I can do with the > server-side-geocoder, and I guess with the client-side-geocoder the > showing in the browser could be an update of a label in the method which > is fired when the dragging is ended). > > So the problem is how the GCG should notice the end of dragging and do the > reverse geocoding. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
