[OpenLayers-Dev] OpenLayers 2.11 RC2

[RICHARD Didier]

> Hi Didier,
>

Hi Bart,

> I believe this was reverted after RC2, see also:
>
> http://trac.osgeo.org/openlayers/ticket/3431
>
> Would be good to test with either trunk or the to be released RC3.
>

I'm awaiting for RC3 in that case !

Best regards,

didier

> TIA.
>
> Best regards,
> Bart
>
> --
> Bart van den Eijnden
> OSGIS - http://osgis.nl
>
> On Aug 21, 2011, at 4:07 PM, RICHARD Didier wrote:
>
>>
>>> The full build was also failing (on some systems) due to a missing
>>> requires.
>>> http://trac.osgeo.org/openlayers/ticket/3467
>>>
>>> Please pull this into RC3 as well.
>>>
>>
>> Hi all,
>>
>> I may have another regression between OL 2.10 and OL 2.11 RC2 :
>>
>> * OL 2.10 :
>>
>> OpenLayers.Layer.setOpacity() : the inner divs are changed when
>> modifying
>> the layer's opacity
>>
>> * OL 2.11 :
>>
>> the layer's opacity seems to be now managed at the layer's div directly.
>>
>> If we have a look at OpenLayers.Tile.Image.initImgDiv() method, one can
>> find :
>>
>> if(this.layer.opacity != null) {
>>
>>    OpenLayers.Util.modifyDOMElement(this.imgDiv, null, null, null,
>>                                     null, null, null,
>>                                     this.layer.opacity);
>> }
>>
>> when the tile's div is created.
>>
>> Calling layer.setOpacity() does not change the tile's opacity anymore
>> (in
>> fact, if you start with an opacity of 30%, then you have got 30% on the
>> layer's div and 30% on the tile's opacity ...).
>>
>> I guess the above lines could be removed from initImgDiv(). Don't know
>> whether there are other pitfalls related with the new opacity
>> management.
>>
>> Any thought on that ?
>>
>> didier
>>
>>> Thanks,
>>> Tim
>>>
>>> On Mon, Aug 15, 2011 at 4:16 PM,  <christopher.schmidt at nokia.com>
>>> wrote:
>>>> We have a clear regression that will force an RC3. I'm willing to pull
>>>> this
>>>> into the RC3.
>>>>
>>>> It looks like there's still a few outstanding bugs against RC2. I'll
>>>> leave
>>>> those open for another day or two, but if there's not more done on
>>>> them,
>>>> then I'm likely to proceed without waiting on further fixes, barring
>>>> additional regressions.
>>>>
>>>> -- Chris
>>>>
>>>> On Aug 15, 2011, at 8:33 PM, ext Tim Schaub wrote:
>>>>
>>>>> I committed Volker's patch for
>>>>> http://trac.osgeo.org/openlayers/ticket/3417
>>>>>
>>>>> I've added my thoughts on the ticket.  I'll leave it up to the
>>>>> release
>>>>> manager to decide if this is pulled into another RC.  We have to stop
>>>>> at some point, and I think we'd all agree that only a clear
>>>>> regression
>>>>> should warrant a new RC.
>>>>>
>>>>> Thanks for the patch Volker.  Sorry I didn't pick it up immediately
>>>>> after we talked about it some weeks ago.
>>>>>
>>>>> Tim
>>>>>
>>>>> On 8/14/11 11:07 AM, Volker Mische wrote:
>>>>>> On 08/08/2011 04:20 PM, christopher.schmidt at nokia.com wrote:
>>>>>>> The OpenLayers Development Team is proud to announce the second
>>>>>>> release
>>>>>>> candidate of OpenLayers 2.11!
>>>>>>>
>>>>>>> As of 2.11-RC2, the OpenLayers 2.11 release closes an additional 31
>>>>>>> tickets,
>>>>>>> resolving a number of issues with the previous release candidate.
>>>>>>>
>>>>>>> We invite you to help us test the 2.11 release candidate! To test
>>>>>>> 2.11
>>>>>>> in your applications, include the following tag in your
>>>>>>> OpenLayers-powered page:
>>>>>>>
>>>>>>> <script
>>>>>>> src="http://openlayers.org/api/2.11-rc2/OpenLayers.js"></script>
>>>>>>>
>>>>>>> As always, the source is available at
>>>>>>> http://openlayers.org/download/.
>>>>>>> Bug reports can be filed in Trac, under the 2.11 RC2 version and
>>>>>>> 2.11
>>>>>>> milestone.
>>>>>>>
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I somehow missed this 2.11 RC2 mail. Is there a chance to get the
>>>>>> JSONP
>>>>>> (OpenLayers.Protocol.Script) improvements into 2.11?
>>>>>>
>>>>>> http://trac.osgeo.org/openlayers/ticket/3417
>>>>>>
>>>>>> Is there anything I can do to make it happen?
>>>>>>
>>>>>> The reason why I really want it in is, that also CouchDB uses such
>>>>>> more
>>>>>> restrictive callback name validation and I'd like to make as easy as
>>>>>> possible for people to use OpenLayers/MapQuery with a remote
>>>>>> CouchDB/GeoCouch.
>>>>>>
>>>>>> Cheers,
>>>>>> Volker
>>>>>> _______________________________________________
>>>>>> Dev mailing list
>>>>>> Dev at lists.osgeo.org
>>>>>> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
>>>>>
>>>>> _______________________________________________
>>>>> Dev mailing list
>>>>> Dev at lists.osgeo.org
>>>>> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Tim Schaub
>>> OpenGeo http://opengeo.org/
>>> Expert service straight from the developers.
>>> _______________________________________________
>>> Dev mailing list
>>> Dev at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
>>>
>>
>>
>> --
>> 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
>> _______________________________________________
>> Dev mailing list
>> Dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/openlayers-dev
>>
>
>


-- 
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