bratliff, awesome work! Canvas is great for really big polylines and polygons with lots of points, but mapping libraries usually use SVG because you can add listeners on mouse events (click, mouseover/out/move) for the elements, and in Canvas you can't do that so you can only use it for visual purposes, without interaction. But it's true that SVG is considerably slower, taking into account that the lib needs to perform clip rect for polylines and polygons manually (with a separate algorithm for each) on every drag/zoom.
On Jan 6, 2:41 pm, bratliff <[email protected]> wrote: > Opera supports both SVG and CANVAS except for the > "globalCompositeOperation" which behaves differently in Opera than in > other browsers. Opera cannot do "cut outs" easily like the other > browsers without analyzing the "winding" direction (clockwise / > counterclockwise) for every poly. > > I have some examples working in Opera located at: > > http://www.polyarc.us/polycluster > > By default, CANVAS is used by browsers supporting both. CANVAS > requires fewer DOM elements which improves performance during > dragging, panning & zooming. > > Internet Explorer support is in the works but waiting on an > incompatability with the API to be resolved. I suspect it is a naming > conflict which I am happy to change if I know what to change. It only > occurs in Internet Explorer. It always occurs at line 397 in the API > (v 3.24).
-- 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.
