Fix precision input change in mouse-position example
Correct docs for map.getTarget
Merge pull request #1215 from probins/target

Correct docs for map.getTarget
Merge pull request #1193 from fredj/mouseposition_precision_input

MousePosition example issues
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
Make ol.Object#getKeys about 10x faster
Moving squaredDistanceToSegment to the coordinate package
Merge pull request #1224 from twpayne/faster-object-getkeys

Make ol.Object#getKeys about 10x faster
Let closestOnSegment return nothing more than a coordinate

Since we do not use the 'along' property anywhere, and the
resulting array returned by closestOnSegment could cause trouble
when working with 3d coodinates, now only the closest point is
returned, and the squared distance to the segment is calculated
by squaredDistanceToSegment instead.
Function to buffer an extent