Great pointers, thanks a bunch!
Michael Bolin mentions that in his book (which I strongly recommend by the way, if anyone else is interested). Apparently, the Closure Compiler will consider a literal property name (declared with an array-like notation) as something the developer doesn't want to have optimized/obfuscated. There are indeed cases in which I need to append properties to GM objects, particularly when __gm_id doesn't cut it or when I need to create in the GM object an awareness of the soundings (the wrapper for instance), so shape = new CustomShape( /* constructor provides a CustomShape.id*/ ); shape.poly = new google.maps.Polygon(...); shape.poly['parentId'] = shape.id; or something in this line. Of course the second and third lines happen within the constructor, but I'm lazy to fix that now. Do you think using the __gm_id property has any serious disadvantages other than not having the guarantee that it'll the same the next time 'round, when I F5 the app? Also, what's the deal with the messed up events? Why are some events simple objects with just lat/long, and others are more complex dom events, with a long property chain and stuff like event.responseValue, yadda yadda? Why aren't all events triggered in the map following the same pattern? Should I move this question to a different (perhaps a new) post? Thank you!!! -- 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.
