postrunner 0.0.10 → 0.0.11

data/misc/openlayers/license.txt

@@ -1,27 +0,0 @@
-Copyright 2005-2013 OpenLayers Contributors. All rights reserved. See
-authors.txt for full list.
-
-Redistribution and use in source and binary forms, with or without modification,
-are permitted provided that the following conditions are met:
-
- 1. Redistributions of source code must retain the above copyright notice, this
-list of conditions and the following disclaimer.
-
- 2. Redistributions in binary form must reproduce the above copyright notice,
-this list of conditions and the following disclaimer in the documentation and/or
-other materials provided with the distribution.
-
-THIS SOFTWARE IS PROVIDED BY OPENLAYERS CONTRIBUTORS ``AS IS'' AND ANY EXPRESS
-OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
-SHALL COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
-PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
-OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
-ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-The views and conclusions contained in the software and documentation are those
-of the authors and should not be interpreted as representing official policies,
-either expressed or implied, of OpenLayers Contributors.

data/misc/openlayers/licenses/APACHE-2.0.txt

@@ -1,202 +0,0 @@
-
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.

data/misc/openlayers/licenses/BSD-LICENSE.txt

@@ -1,28 +0,0 @@
-Redistribution and use of this software in source and binary forms, with or
-without modification, are permitted provided that the following conditions are
-met:
-
-* Redistributions of source code must retain the above
-  copyright notice, this list of conditions and the
-  following disclaimer.
-
-* Redistributions in binary form must reproduce the above
-  copyright notice, this list of conditions and the
-  following disclaimer in the documentation and/or other
-  materials provided with the distribution.
-
-* Neither the name of Yahoo! Inc. nor the names of its
-  contributors may be used to endorse or promote products
-  derived from this software without specific prior
-  written permission of Yahoo! Inc.
-
-THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
-DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
-ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
-ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

data/misc/openlayers/licenses/MIT-LICENSE.txt

@@ -1,18 +0,0 @@
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
-LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
-OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
-WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/misc/openlayers/notes/2.12.md

@@ -1,391 +0,0 @@
-# Major enhancements and additions
-
-## Zoom Control
-
-A simple control to add zoom in/out buttons on the map that can be entirely styled using CSS.
-See it live in this [example](http://openlayers.org/dev/examples/zoom.html).
-
-Corresponding issues/pull requests:
-
- * https://github.com/openlayers/openlayers/pull/291
- * https://github.com/openlayers/openlayers/pull/292
-
-## Builds
-
-This version of OpenLayers ships with three builds:
-
- * `OpenLayers.js`
- * `OpenLayers.light.js`
- * `OpenLayers.mobile.js`
-
-See the README.md file and the docs on docs.openlayers.org for more information.
-
-Corresponding issues/pull requests:
-
- * https://github.com/openlayers/openlayers/pull/254
- * https://github.com/openlayers/openlayers/pull/261
-
-## style.mobile.css
-
-The theme/default directory now includes a mobile-specific CSS file, namely
-style.mobile.css. The OpenLayers mobile examples use this file. To use it
-in your mobile pages use tags like this:
-
-<link rel="stylesheet" href="openlayers/theme/default/style.mobile.css" type="text/css">
-
-(This file used to be in the examples/ directory).
-
-## Sensible projection defaults
-
-The geographic and web mercator projections define default values for the maxExtent, and units. This simplifies the map and layer configuration.
-
-For example, a map that used to be created with this:
-
-    map = new OpenLayers.Map({
-        div: "map",
-        projection: "EPSG:900913",
-        units: "m",
-        maxExtent: new OpenLayers.Bounds(
-            -20037508.34, -20037508.34, 20037508.34, 20037508.34
-        )
-    });
-
-can now be created with this:
-
-    map = new OpenLayers.Map({
-        div: "map",
-        projection: "EPSG:900913"
-    });
-
-Corresponding issues/pull requests:
-
- * https://github.com/openlayers/openlayers/pull/219
-
-## Tile Offline Storage
-
-With the new `OpenLayers.Control.CacheRead` and `OpenLayers.Control.CacheWrite` controls, applications can cache tiles for offline use or for use with slow connections.
-
-Corresponding issues/pull requests:
-
- * https://github.com/openlayers/openlayers/pull/301
-
-## Tile Animation
-
-The displaying of tiles can now be animated, using CSS3 transitions. Transitions operate on the `opacity` property. Here's the CSS rule defined in OpenLayers' default theme:
-
-    .olLayerGrid .olTileImage {
-        -webkit-transition: opacity 0.2s linear;
-        -moz-transition: opacity 0.2s linear;
-        -o-transition: opacity 0.2s linear;
-        transition: opacity 0.2s linear;
-    }
-
-People can override this rule to use other transition settings. To remove tile animation entirely use:
-
-    .olLayerGrid .olTileImage {
-        -webkit-transition: none;
-        -moz-transition: none;
-        -o-transition: all 0 none;
-        transition: none;
-    }
-
-Note that by default tile animation is not enabled for single tile layers.
-
-Corresponding issues/pull requests:
-
- * https://github.com/openlayers/openlayers/pull/127
-
-Note: Issue #511 has reported that tile animation causes flickering/blinking in
-the iOS native browser. Forcing the browser to use hardware-accelerated
-animations fixed the issue, but #542 has reported that it also considerably
-slows down freehand drawing on iOS. If you're experiencing this and want to
-disable hardware-accelerated animations you can use the following rule in your
-CSS:
-
-    @media (-webkit-transform-3d) {
-        img.olTileImage {
-            -webkit-transform: none;
-        }
-    }
-
-## Tile Queue
-
-The tiling code has been overhauled so tile loading in grid layers is now done in a queue.
-The tile queue gives more control on the tile requests sent to the server. Pending requests for tiles that are not needed any more (e.g. after zooming or panning) are avoided, which increases performance and reduces server load.
-
-Corresponding issues/pull requests:
-
- * https://github.com/openlayers/openlayers/pull/179
-
-## Tile Canvas
-
-Image tiles expose a `getCanvasContext` function that can be used for various
-things, like changing the image pixels, save the image using the File API, etc.
-
-See the [osm-grayscale
-example](http://openlayers.org/dev/examples/osm-grayscale.html).
-
-Corresponding issues/pull requests:
-
- * https://github.com/openlayers/openlayers/pull/160
-
-## Tile Interaction Event Improvements
-
-The layer's `tileloaded` event now returns a reference to the loaded tile. The new `tileloaderror` event does the same, and is fired when a tile could not be loaded.
-
-Corresponding issues/pull requests:
-
- * https://github.com/openlayers/openlayers/pull/283
-
-## Tile and Backbuffer Overhaul
-
-The whole image tile and backbuffer code (behind `transitionEffect:resize`) has been redesigned and
-rewritten. This overhaul yields better performance and code simplifications.
-
-Corresponding issues/pull requests:
-
- * https://github.com/openlayers/openlayers/pull/16
-
-## Continuous Zooming
-
-Tile layers can now be displayed at resolutions not supported by their tiling
-services. This works by requesting tiles at higher resolutions and stretching
-the layer div as appropriate. With this change fractionalZoom:true will work
-for single tile layers as well as for tiled layers.
-
-See the [client zoom
-example](http://openlayers.org/dev/examples/clientzoom.html).
-
-Corresponding issues/pull requests:
-
- * http://trac.osgeo.org/openlayers/ticket/3531
- * https://github.com/openlayers/openlayers/pull/5
-
-# Behavior Changes from Past Releases
-
-## MultiMap Layer Removal
-
-The `OpenLayers.Layer.MultiMap` class has been removed entirely, as the MultiMap service was discontinued.
-
-Corresponding issues/pull requests:
-
- * https://github.com/openlayers/openlayers/pull/328
-
-## GPX API change
-
-The `gpxns` API property has been removed. The GPX namespace is now defined in the `namespaces` property but is not intended to be overriden.
-
-GPX also now has a basic write function.
-
-Corresponding issues/pull requests:
-
- * https://github.com/openlayers/openlayers/pull/221
-
-## Function return values
-
-Previously 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
-
-Corresponding issues/pull requests:
-
- * http://trac.osgeo.org/openlayers/ticket/3320
-
-## 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).
-
-Corresponding issues/pull requests:
-
- * http://trac.osgeo.org/openlayers/ticket/3568
- * https://github.com/openlayers/openlayers/pull/40
-
-
-## Rico deprecation
-
-We are deprecating the Rico classes/objects in OpenLayers. This has the following implications:
-
-`Popup.AnchoredBubble` is deprecated. Its constructor now displays a deprecation message on the console. If you want popups with rounded corners either use `Popup.FramedClould`, or use `Popup.Anchored` and round corners using the [border-radius](https://developer.mozilla.org/en/CSS/border-radius) CSS property.
-
-The `roundedCorner` option of `Control.LayerSwitcher` is deprecated, and it now defaults to `false`. Setting it to true results in deprecation messages being output on the console. If you still want to set `roundedCorner` to `true` (you should not!) you need to make sure that the Rico/Corner.js and Rico/Color.js scripts are loaded in the page. This can be ensured by adding Rico/Corner.js in the build profile. The controls.html example demonstrates how to use `border-radius` to round corners of a layer switcher:
-
-
-    .olControlLayerSwitcher .layersDiv {
-        border-radius: 10px 0 0 10px;
-    }
-
-
-In future releases we intend to move the Rico and `AnchoredBubble` code into deprecated.js. You really should consider stop using Rico-based functionalities in your applications.
-
-Corresponding issues/pull requests:
-
- * https://github.com/openlayers/openlayers/pull/99
-
-## Changes in Geometry
-
-The base `OpenLayers.Geometry` class no longer depends on `OpenLayers.Format.WKT` or `OpenLayers.Feature.Vector`.  If you want to make use of the `OpenLayers.Geometry.fromWKT` method, you must explicitly include the OpenLayers/Format/WKT.js file in your build.  
-
-Without the WKT format included (by default), the `OpenLayers.Geometry::toString` method now returns "[object Object]."  Previously, it returned the Well-Known Text representation of the geometry.  To maintain the previous behavior, include the OpenLayers/Format/WKT.js file in your build.
-
-Corresponding issues/pull requests:
-
- * https://github.com/openlayers/openlayers/pull/101
-
-## Google v3 Layer
-
-This release fixes a problem with the clickable elements supplied by Google. `OpenLayers.Layer.Google.v3` is now compatible with the current frozen version of Google's API (3.7) and also with the current release and nightly versions (3.8 and 3.9), but be aware that Google may change these elements in their release and nightly versions at any time, and an interim fix OpenLayers release may be needed.
-
-It's recommended that production servers always load the frozen version of Google's API, but it would help find potential problems if development pages used the latest nightly version.
-
-See the class description in the API docs for `OpenLayers.Layer.Google.v3` for more details.
-
-Good ideas on how to improve this unsatisfactory situation welcome!
-
-Corresponding issues/pull requests:
-
- * https://github.com/openlayers/openlayers/pull/472
-
-## OSM and Bing Layers
-
-`Layer.OSM` is now defined in its own script file, namely `OpenLayers/Layer/OSM.js`. So people using `Layer.OSM` should now include `OpenLayers/Layer/OSM.js`, as opposed to `OpenLayers/Layer/XYZ.js`, in their OpenLayers builds.
-
-Corresponding issues/pull requests:
-
- * https://github.com/openlayers/openlayers/issues/138
- * https://github.com/openlayers/openlayers/pull/144
-
-The `OpenLayers.Tile.Image` class now has a method to get a canvas context for processing tiles. Since both OSM and Bing set Access-Control-Allow-Origin headers for their tiles, it is possible to manipulate a canvas that these tiles were rendered to even if the tiles come from a remote origin. Especially when working with custom OSM tilesets from servers that do not send Access-Control-Allow-Origin headers, it is now necessary to configure the layer with
-
-    tileOptions: {crossOriginKeyword: null}
-
-Both `OpenLayers.Layer.OSM` and `OpenLayers.Layer.Bing` do not have defaults for `maxExtent`, `maxResolutions` and `units` any more. This may break maps that are configured with a `maxResolution` of `156543.0339`, which was used in examples before 2.11, but is incorrect. The correct value is `156543.03390625`, but it is no longer necessary to specify a maxResolution, maxExtent and units if the correct resolution is set. See "Projection and Spherical Mercator" below.
-
-## Projection & SphericalMercator
-
-When working with Web Mercator layers (e.g. Google, Bing, OSM), it was previously necessary to configure the map or the base layer with the correct `projection`, `maxExtent`, `maxResolutions` and `units`. Now OpenLayers has defaults for WGS84 and Web Mercator in `OpenLayers.Projection.defaults`, so it is enough to provide the `projection`.
-
-Old:
-
-    new OpenLayers.Map({
-        div: "map",
-        projection: "EPSG:900913",
-        maxResolution: 156543.03390625,
-        maxExtent: new OpenLayers.Bounds(-20037508.34, -20037508.34, 20037508.34, 20037508.34),
-        units: "m",
-        layers: [
-            new OpenLayers.Layer.Google("Google Streets"),
-            new OpenLayers.Layer.OSM(null, null, {isBaseLayer: false, opacity: 0.7})
-        ],
-        zoom: 1
-    });
-
-New:
-
-    new OpenLayers.Map({
-        div: "map",
-        projection: "EPSG:900913",
-        layers: [
-            new OpenLayers.Layer.Google("Google Streets"),
-            new OpenLayers.Layer.OSM(null, null, {isBaseLayer: false, opacity: 0.7})
-        ],
-        zoom: 1
-    });
-
-In previous releases, coordinate transforms between EPSG:4326 and EPSG:900913 were defined in the SphericalMercator.js script.  In 2.12, these default transforms are included in the Projection.js script.  The Projection.js script is included as a dependency in builds with any layer types, so no special build configuration is necessary to get the web mercator transforms.
-
-Corresponding issues/pull requests:
-
- * https://github.com/openlayers/openlayers/pull/219
-
-If you were previously using the `OpenLayers.Layer.SphericalMercator.forwardMercator` or `inverseMercator` methods, you may have to explicitly include the SphericalMercator.js script in your build.  The Google layer is the only layer that depends on the SphericalMercator mixin.  If you are not using the Google layer but want to use the SphericalMercator methods listed above, you have to explicitly include the SphericalMercator.js script in your build.
-
-Corresponding issues/pull requests:
-
-* https://github.com/openlayers/openlayers/pull/153
-
-## QueryStringFilter
-
-`OpenLayers.Protocol.HTTP` no longer requires `OpenLayers.Format.QueryStringFilter`. It you need this, make sure it is included in your build config file.
-
-Corresponding issues/pull requests:
-
- * https://github.com/openlayers/openlayers/issues/147
- * https://github.com/openlayers/openlayers/pull/148
-
-## Changes in getURLasync
-
-The internal `OpenLayers.Layer.getURLasync` function now take a bound, a callback and a scope. The function no longer needs update the passed property but simply to return to url.
-
-## Changes when base layer configured with wrapDateLine: true
-
-Vector editing across the date line works reliably now. To make this work, OpenLayers won't zoom out to resolutions where more than one world is visible any more. For maps that have base layers with wrapDateLine set to false, no zoom restrictions apply.
-
-## OpenLayers.Util.onImageLoadError no longer exists
-
-To replace a tile that couldn't be loaded with a static image, create a css selector for the `.olImageLoadError` class (e.g. a `background-image`).
-
-For more complex tile loading error handling, register a listener to the layer's `tileerror` event.
-
-Corresponding issues/pull requests:
-
- * https://github.com/openlayers/openlayers/pull/283
-
-## Deprecated Components
-
-A number of properties, methods, and constructors have been marked as deprecated for multiple releases in the 2.x series.  For the 2.12 release this deprecated functionality has been moved to a separate deprecated.js file.  If you use any of the constructors or methods below, you will have to explicitly include the deprecated.js file in your build (or add it in a separate `<script>` tag after OpenLayers.js).
-
- * OpenLayers.Class.isPrototype
- * OpenLayers.Class.create
- * OpenLayers.Class.inherit
- * OpenLayers.Util.clearArray
- * OpenLayers.Util.setOpacity
- * OpenLayers.Util.safeStopPropagation
- * OpenLayers.Util.getArgs
- * OpenLayers.nullHandler
- * OpenLayers.loadURL
- * OpenLayers.parseXMLString
- * OpenLayers.Ajax.* (all methods)
- * OpenLayers.Element.hide
- * OpenLayers.Element.show
- * OpenLayers.Element.getDimensions
- * OpenLayers.Tile.prototype.getBoundsFromBaseLayer
- * OpenLayers.Control.MouseDefaults
- * OpenLayers.Control.MouseToolbar
- * OpenLayers.Layer.Grid.prototype.getGridBounds
- * OpenLayers.Format.XML.prototype.concatChildValues
- * OpenLayers.Layer.WMS.Post
- * OpenLayers.Layer.WMS.Untiled
- * OpenLayers.Layer.MapServer.Untiled
- * OpenLayers.Tile.WFS
- * OpenLayers.Feature.WFS
- * OpenLayers.Layer.WFS
- * OpenLayers.Layer.VirtualEarth
- * OpenLayers.Protocol.SQL
- * OpenLayers.Protocol.SQL.Gears
- * OpenLayers.Layer.Yahoo
- * OpenLayers.Layer.GML
- * OpenLayers.Geometry.Rectangle
- * OpenLayers.Renderer.NG
- * OpenLayers.Renderer.SVG2
-
-In addition, OpenLayers no longer modifies any native prototypes or objects by default.  If you rely on any of the following, you'll need to include deprecated.js explicitly to get the same behavior.
-
- * String.prototype.startsWith
- * String.prototype.contains
- * String.prototype.trim
- * String.prototype.camelize
- * Function.prototype.bind
- * Function.prototype.bindAsEventListener
- * Event.stop
-