Sorry Mike Williams that I did not notice your answer until now. I experienced a performance gain by narrowing the scope before I saw the video.
It was a page where a polygon with about 100 vertices is moved (removed/reconstructed) by dragging a marker. I packaged all the functions and variables that used to be global, to an object. I did not measure but I felt some performance gain. The modification was made just to minimize global namespace pollution. I realized that maybe the current fashion of packaging things like jQuery in a single object comes from performance point of view. Google Maps API is also available in object google.maps and v3 is not available in global scope at all. I agree that most of the Google Maps pages will not gain anything significant by those rules but if 'mousemove' or 'drag' are used for triggering loops, you should optimize. About reflow. I don't know either if it concerns decent browsers at all. However playing with CSS3 round corners and shadows with hover: stylechange has assured me that there is some reflow aspects to be considered. (CSS3 has nothing to do with IE). I have to study more. Offtopic. I ended up using v=2.153 with the draggable polygon. That removes/recreates polygons much faster than current versions. Haven't checked if the issue is recorded. @Mike w/o Williams. Yes, those Douglas Crockford's videos are classics. A must for anyone serious with JavaScript. Both of those video stars are from Yahoo!. Is that the reason why MS is so interested in the company? I managed to find just one JavaScript lesson from MS http://www.youtube.com/watch?v=wvsboPUjrGc&NR=1 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
