I've used jmap2 a bit. It's really nice to have a jQuery-like way of playing with maps (as well as geocoding, etc) - but as was said before, hard to say if it is worth it for the added overhead and restrictions it places on your code.
That said, I think there is room for a more extensive jQuery solution that handles directions, map manipulation, complex polygons and overlays in an easier way. On Jan 30, 6:59 am, Dave Stewart <[EMAIL PROTECTED]> wrote: > Hi Chris, > > The trick to Google Maps (for me at least) was getting to know the > basics of the OOPness of it all. > > EVERYTHING (just about) is an object. You rarely pass values, you > normally instantiate objects, then pass them. > > For example, in the example Bohdan gave, you would have to 1) create > the Point, then instantiate a 2) new Marker with it, then 3) add the > Marker to the map. (From memory, but you get the idea) > > You only need to know a few basic objects, and you're away, although > the size of the API can be overwhelming the basics are easy to get. > > Hope that helps. > > :D
