Hi Sharath, Your assumption is right for most of the cases, a new API is a better option than a deprecated API most of the times.
You could stick to V2, but for new applications I would personally recommend using V3 unless there is a strong reason to stick to V2 -- e.g. a need to commit with old browsers that are not officially supported in V3. If most of the new application's code would consist on V2-based existing code, you need to asses the cost of developing afresh and the longer development time against the advantages that V3 will bring in, not only right now but also in the future. On the other hand, once you have a new V3-based code base, I guess you can re-use it in all new applications. Cheers, Miguel On May 26, 1:23 am, Sharath Dodda <[email protected]> wrote: > Hi Miguel, > Thanks for your quick response. > > We are going to develop a new application using this API, so we assume > that it is better to use v3, than v2 (as v2 is deprecated and v3 is > recommended). Is our assumption wrong? Please note that we absolutely > don't require the features of v3. We already have an application > developed in v2. So, we would like to use that application's code base > rather than developing afresh. > > Having said that and also your note that it would work for no less > than 3 years, what is your suggestion? is it worthwhile to go for v3 > or stick to v2 itself? > > As before, your quick response is much appreciated, as we are going to > make decisions based on this. > > thanks again for your response. > Sharath. > > On May 25, 6:23 am, Miguel Ángel (Google Employee) <[email protected]> > wrote: > > > > > Hello Sharath, > > > There is specific step-by-step process to migrate from V2 to V3, also > > note the V2 API will keep working for no less than three years. > > > The best you can do is read through the V3 documentation and > > familiarize yourself with how exactly things work now, there are some > > differences but the docs follow pretty much the same structure: > > > The Google Maps Javascript API > > V3http://code.google.com/apis/maps/documentation/javascript/basics.html > > > Only read the following sections to get started: > > Basics > > Tutorial > > Events > > Controls > > Overlays > > Services > > > Then, having a grasp of how things work, re-code your application > > using the new API. > > Whenever you are not sure about the details, check the API Reference > > section > > athttp://code.google.com/apis/maps/documentation/javascript/reference.html > > > Cheers, > > Miguel > > > On May 25, 4:35 am, Sharath Dodda <[email protected]> wrote: > > > > Hi All, > > > > Could you please let me know where I can find the steps for migrating > > > from Google Maps JavaScript API v2 to v3. I searched for the same, but > > > found none. > > > > Your quick help is much appreciated, as we require the response > > > urgently. > > > > Thanks, > > > Sharath. > > > > -- > > > 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 > > > athttp://groups.google.com/group/google-maps-js-api-v3?hl=en. > > > -- > > 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 > > athttp://groups.google.com/group/google-maps-js-api-v3?hl=en. -- 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.
