ashatora/openlayers
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

remove duplications in the 2.12 notes

Browse Source
This commit is contained in:
Éric Lemoine
2012-01-03 08:29:40 +01:00
parent 4f4a7e9c0a
commit d4249960e3
1 changed files with 0 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
notes/2.12.md
View File

@@ -49,41 +49,6 @@ Looking at the tests is a good way to understand what the requires changes are.
* GitHub issue: https://github.com/openlayers/openlayers/pull/40
## Rico deprecation
We are deprecating the Rico classes/objects in OpenLayers. This has the following implications:
}
# Behavior Changes from Past Releases
## Function return values
[Previously][prev] a few functions in the library displayed error messages and returned `undefined`, `null` or `false` if the parameters passed in were bad. In 2.12 these functions now just throw an error/exception. People relying on return values to know if a function call is successful may need to change their code. Here are the modified functions:
* `OpenLayers.Bounds.add` throws a `TypeError` exception if `x` or `y` is null
* `OpenLayers.LonLat.add` throws a `TypeError` exception if `lon` or `lat` is null
* `OpenLayers.Pixel.add` throws a `TypeError` exception if `x` or `y` is null
* `OpenLayers.Filter.Comparison.value2regex` throws an `Error` exception if `wildcard` equals to `"."`
* `OpenLayers.Layer.PointTrack.addNodes` throws a `TypeError` exception if `endPoint` isn't actually a point
* `OpenLayers.Layer.Vector.getFeatureFromEvent` throws an `Error` exception if the layer has no renderer
[prev]: https://github.com/openlayers/openlayers/commit/6e9a3e4c13e00c29daf28efd92b63c2390e69231
## Changes in formats WMTSCapabilities and SOSCapabilities
The structure of the object returned by `Format.WMTSCapabilities:read` and `Format.SOSCapabilities:read` has slightly changed.
For `WMTSCapabilities` the GET href used to be made available at `operationsMetadata.GetCapabilities.dcp.http.get`, the latter is now an array of objects with two properties: `url` and `constrains`. People using `operationsMetadata.GetCapabilities.dcp.http.get` in their applications should certainly use `operationsMetadata.GetCapabilities.dcp.http.get[0].url`.
Likewise for `SOSCapabilities`.
Looking at the tests is a good way to understand what the requires changes are. See [SOSCapabilities/v1_0_0.html](https://github.com/openlayers/openlayers/blob/master/tests/Format/SOSCapabilities/v1_0_0.html) and [WMTSCapabilities/v1_0_0.html](https://github.com/openlayers/openlayers/blob/master/tests/Format/WMTSCapabilities/v1_0_0.html).
* Trac ticket: http://trac.osgeo.org/openlayers/ticket/3568
* GitHub issue: https://github.com/openlayers/openlayers/pull/40
## Rico deprecation
We are deprecating the Rico classes/objects in OpenLayers. This has the following implications: