Google Maps API classes are definitely not meant to be extended with your own methods and properties. As you said, Google may later add a method or property of the same name. Or there may be an internal method or property you don't know about that conflicts with yours.
You are completely correct that you should write your own classes or objects to wrap Google's instead of extending theirs. -Mike On Thu, Feb 17, 2011 at 7:58 AM, Fran <[email protected]> wrote: > Hi Loic, > > I'm starting a project with Google Map, and for our necessities I'm > thinking about implementing a API that wraps Google Map API. I'm not sure > about extending Google Map classes because I'm afraid that if I implement a > method, let's call it methodA, and later on Google decides to implement > methodA, I'd be overriding this one... > > would be it be safe extend Google Map classes ? In my opinion this type of > APIs should be wrapped, what do you reckon ? > > Thanks > -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
