84a8d8d1f6
The WMSDescribeLayer format currently differs from other formats that inhreit from VersionedOGC by having an array instead of an object as return type. This especially bad since the VersionedOGC superclass sets a version property on the array. With this change, the WMSDescribeLayer format will also be compatible with GeoServer's new JSON response type for DescribeLayer - see http://sourceforge.net/mailarchive/message.php?msg_id=29912776. Another change included here is the removal of the WMSDescribeLayer format's getVersion hack, which was replaced by a generic fallback to less generic parsers, e.g. from a v1_1_1 parser to a v1_1 parser if v1_1_1 is not implemented.
51 lines
2.2 KiB
Markdown
51 lines
2.2 KiB
Markdown
# Enhancements and Additions
|
|
|
|
## Dotless identifiers
|
|
|
|
Previously, objects generated by the library were given id properties with values that contained dots (e.g. "OpenLayers.Control.Navigation_2"). These same identifiers are also used for DOM elements in some case. Though uncommon, a developer may want to access these elements with a CSS selector. To facilitate this, we now always generate ids with underscore instead of dot.
|
|
|
|
Corresponding issues/pull requests:
|
|
|
|
* https://github.com/openlayers/openlayers/pull/416
|
|
|
|
## Better support for analog scroll wheel
|
|
|
|
Removed rounding of zoom level for maps with fractionalZoom == true. So users with an OS and interface device with analog scroll support will now get smooth zooming.
|
|
|
|
Corresponding issues/pull requests:
|
|
|
|
* https://github.com/openlayers/openlayers/pull/483
|
|
|
|
# Behavior Changes from Past Releases
|
|
|
|
## window.$ is no longer an alias for OpenLayers.Util.getElement
|
|
|
|
We do no longer create a global variable '$' when such a symbol isn't already
|
|
defined. Previous versions of OpenLayers would define '$' to be an alias for
|
|
OpenLayers.Util.getElement. If your application requires window.$ to be defined
|
|
in such a way you can either
|
|
|
|
* include deprecated.js in your custom build or as additional ressource in your
|
|
HTML-file
|
|
* or you do the aliasing in your application code yourself:
|
|
|
|
window.$ = OpenLayers.Util.getElement;
|
|
|
|
Corresponding issue/pull requests:
|
|
|
|
* https://github.com/openlayers/openlayers/pull/423
|
|
|
|
# New Options for Build Script
|
|
|
|
* add the contents of a file as a comment at the front of the build, for example, the output of 'git describe --tags' could be saved as a file and then included
|
|
* create build file as an AMD module
|
|
|
|
run 'build.py -h' for more details
|
|
|
|
Corresponding issue/pull requests:
|
|
|
|
* https://github.com/openlayers/openlayers/pull/528
|
|
|
|
# Different return type for OpenLayers.Format.WMSDescribeLayer
|
|
|
|
The return type of WMSDescribeLayer format's `read` method was different from the one of the VersionedOGC format superclass. So it was changed from an array to an object with a layerDescriptions property that holds the array. For backwards compatibility, the object still has a length property and 0, ..., n properties with the previous array values. |