[mapguide-internals] RFC 132: Fusion OpenLayers upgrade
jumpinjackie at gmail.com
Mon Mar 25 21:48:26 PDT 2013
Part of this RFC is that our custom modifications to OpenLayers are also kept
and tracked separately, so that a rebuild of OpenLayers.js is just a case of
copying our modifications into the standard OpenLayers distribution
(overwriting any existing files) and rebuilding the new combined
OpenLayers.js from that.
So if there's a fix for the IE10 issue, we can just check in a patched set
of the affected files in question.
As it stands, the issue you linked is still open, and I see no
diffs/patchsets indicating the affected files.
Upgrading to OpenLayers 2.13 will only be a consideration if we have a solid
release date for it (I see nothing about it in any roadmaps or discussions).
Currently, 2.13 is just this mythical future stable release that doesn't
View this message in context: http://osgeo-org.1560.n6.nabble.com/RFC-132-Fusion-OpenLayers-upgrade-tp5042379p5042888.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.
More information about the mapguide-internals