I have similar sentiments, but I think that as we modularize more classes, the process gets better and we make the modularization more seamless for developers. Hopefully. :)
On Sep 1, 12:41 pm, Garthan <[EMAIL PROTECTED]> wrote: > I always like hearing and dread hearing about modulariization changes. > > I like them because the ideal of a core google maps that only has the > tiling system (logo and attributions) should be a very small > beast..could be reached by this route in a way that is painless > to endusers... > in the mean time they result in timing issues where classes you expect > to be available arent till later. > > pamela (Google Employee) wrote: > > Hey folks, > > > Last night we pushed 2.126 as 2.x and 2.125 as 2. We modularized more > > controls, as well as the KeyboardHandler class. The changelog is here: > > >http://code.google.com/p/gmaps-api-issues/wiki/JavascriptMapsAPIChang... > > > Note that there was a slight change in our numbering scheme, and 2.126 > > is actually 2.126d. Since we really don't want folks to have to look > > up the exact letter of a release when they hard code to it, we'll be > > putting in a change so that 2.126 aliases to the released letter > > version. > > > As usual, please post regression bugs in the Issue Tracker after > > verifying here that they're bugs in our code. > > > Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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-API?hl=en -~----------~----~----~----~------~----~------~--~---
