Thanks for the fast answer Jim, you've convinced me to go with v3. I'm not that comfortable with javascript, but I'm an expert googler so I'll work it out :)
On Nov 18, 8:23 pm, arclyte <[email protected]> wrote: > Hey Daniel, > > I'd say most of the basic functionality is there now... markers, > infowindows, polylines, polygons, directions. There is definitely > some missing functionality in the way of methods for those functions > as compared to v2. You can probably fill in anything that's missing > yourself, depending on your comfort with javascript (or skills at > googling). I've done some work with both versions and so far I'd > highly recommend v3. It really just comes down to what functionality > you need and when you need it. If you need something that's not in v3 > yet but is in v2 and you can't wait, go with v2. If the you just need > the basics and it's all covered in the documentation you're better off > learning v3 now so you don't have to go back and redo your app once it > becomes the standard. > > - Jim > > On Nov 18, 1:42 pm, Daniel <[email protected]> wrote: > > > Hi, > > I'm trying to learn the Google Maps API so I can build an application. > > Which API version should I concentrate on learning, v2 or v3? The web > > app will be kinda simple to start with, users should be able to add > > markers with descriptions to the map and I should be able to edit and > > delete them. How unfinished are v3 of the API? -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
