On Saturday, May 19, 2012, RICHARD Didier wrote: > > > On Saturday, May 19, 2012, Andreas Hocevar wrote: > > > >> On Sat, May 19, 2012 at 5:36 PM, RICHARD Didier > >> <[email protected] <javascript:;><javascript:;>> > >> wrote: > >> > btw, using the Canvas renderer won't work for IE, will it ? > >> > >> No, but the VML renderer also shouldn't have this issue. > > > > > > > > Right. So to use Canvas in capable browsers and VML in others you'd use > > `renderers: ['VML', 'Canvas']` in the layer config. > > > > In that case, why not changing : > > /** > * Property: renderers > * {Array(String)} List of supported Renderer classes. Add to this > list to > * add support for additional renderers. This list is ordered: > * the first renderer which returns true for the 'supported()' > * method will be used, if not defined in the 'renderer' option. > */ > renderers: ['SVG', 'VML', 'Canvas'], > > into : > > /** > * Property: renderers > * {Array(String)} List of supported Renderer classes. Add to this > list to > * add support for additional renderers. This list is ordered: > * the first renderer which returns true for the 'supported()' > * method will be used, if not defined in the 'renderer' option. > */ > renderers: ['VML', 'Canvas', 'SVG'], > > in OpenLayers.Layer.Vector as most of modern browser would support Canvas > ? (even if old browser will have to check for the two first before chosing > SVG !) Is there a speed issue behind that order of renderers ?
As far as I know the Canvas renderer re-renders features on each map move. This may have performance implications. It also has an impact on user experience – features disappear and reappear. -- Eric Lemoine Camptocamp France SAS Savoie Technolac, BP 352 73377 Le Bourget du Lac, Cedex Tel : 00 33 4 79 44 44 96 Mail : [email protected] http://www.camptocamp.com
_______________________________________________ Dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-dev
