[OpenLayers-Dev] [Polygon Rendering] Inverse fill

[RICHARD Didier]

> On Saturday, May 19, 2012, Andreas Hocevar wrote:
>
>> On Sat, May 19, 2012 at 5:36 PM, RICHARD Didier
>> <didier.richard at ign.fr<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 ?

didier

>
> --
> Eric Lemoine
>
> Camptocamp France SAS
> Savoie Technolac, BP 352
> 73377 Le Bourget du Lac, Cedex
>
> Tel : 00 33 4 79 44 44 96
> Mail : eric.lemoine at camptocamp.com
> http://www.camptocamp.com
>


-- 
RICHARD Didier - Chef du pôle technique du Géoportail
2/4, avenue Pasteur - 94165 Saint Mandé Cedex
Tél : +33 (0) 1 43 98 83 23