Add skeleton for SLD parser
Add scale to/from resolution calculations
Add initial pass of write support, always write out ol.style.Stroke as  LineSymbolizer
write out string concatenation in the more common way
Add more changes to the  halo functionality, introduce SLD defaults for symbolizers conform the SLD spec
add name and title to ol.style.Rule
get rid of the readers we don't support in ol3 symbology as yet
better write support for PointSymbolizer
deal with elseFilter, some cleanup
Add a separate test case for write
do not hard-code the namespaceURIs multiple times
Add MapGuide untiled map support to ol3.

This adds a new ol.source.MapGuide class that is initialized with an options object that can contain the following values:
 - projection: The projection of the Map Definition in EPSG format
 - url: The mapagent URL
 - useOverlay: Determines whether the GETMAPIMAGE (false) or GETDYNAMICMAPOVERLAYIMAGE (true) will be used for requesting the map image. When using GETMAPIMAGE, you must include a valid MAPDEFINITION parameter in the 'params' option property. When using GETDYNAMICMAPOVERLAYIMAGE, you must include a valid SESSION and MAPNAME parameters in the 'params' option property.
 - metersPerUnit: A required value used for calculating the map scale needed by the image request. This value can be calculated using the MapGuide Web API or obtained through the new CREATERUNTIMEMAP operation in MapGuide Open Source 2.6
 - params: A set of key-value pairs to append to the mapagent request
 - extent: The bounds of the layer

An example is included to demonstrate this new layer source. Like ol2, this example uses the MapGuide Server on data.mapguide.com
override URL parameter values in the GetFeatureInfo request if someone provides a param in getFeatureInfoOptions with the same name
make sure parameter name lookups are case-insensitive
have the GML parser read and write out multiple geometry attributes with their correct name
Segment distance calculation fails when modifying points

By providing a segment even for points, we have less distinction
points between points and other geometry types, and are able to
do the segment distance calculation also for points.
Avoid clearing canvas twice
Merge pull request #1294 from bartvde/gmlgeom

GML parser should write out all geometry attributes and respect their names (r=@ahocevar)
Merge pull request #1127 from bartvde/gfi

STYLES parameter duplicated on getFeatureInfo (r=@tschaub,@ahocevar)
change simple type values to undefined instead of null