[mapserver-dev] RFC 113: Layer Compositing Modes

[thomas bonfort]

Steve,
This is what is already implemented. You would get undefined behaviour
only if you happened to mix the old and new syntax inside a single
layer (i.e. OPACITY and COMPOSITE...END inside LAYER).

regards,
thomas

On 10 February 2015 at 22:03, Stephen Woodbridge
<woodbri at swoodbridge.com> wrote:
> Hi Thomas,
>
> +1, this looks like a great addition.
>
> Would it make sense to leave LAYER->OPACITY but just map that to the
> equivalent COMPOSITE ... END block?
>
> I'm not opposed to dropping it because it is a major release, just wondering
> if it would be a trivial thing to remap the keyword to the new
> implementation.
>
> -Steve W
>
>
> On 2/10/2015 4:10 PM, thomas bonfort wrote:
>>
>> Hi Devs,
>>
>> Please have a look at RFC 113 (
>> http://mapserver.org/development/rfc/ms-rfc-113.html ) that adds layer
>> compositing modes and opens up future implementations of layer pixel
>> filter pipelines (blurring comes immediately to mind, others might
>> make sense too). Given that this RFC deprecates the LAYER->OPACITY
>> keyword, 7.0 would be a good time to have this integrated, further
>> developments can continue in a second phase without needing to change
>> the mapfile syntax itself.
>> Given the short timeframe we have before the 7.0 release, I'd like to
>> call for a vote on this one right away (allowing us to respect the 48h
>> delay before the end of the code sprint).
>>
>> I'll open with my +1
>>
>> regards,
>>
>> thomas
>> _______________________________________________
>> mapserver-dev mailing list
>> mapserver-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>>
>
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev