Always use a context for GML parsing

The context is at the bottom of the object stack. All entry
points to parsing (#readGeometryFromNode(),
#readFeaturesFromNode()) set up the context now, and parsers
always access the context at index 0 of the objectStack.
Merge pull request #5 from ahocevar/gml-context

Always use a context for GML parsing
Merge pull request #1756 from twpayne/clean-up-preload

Move preload default value to where it is used
Use ol.xml.pushParseAndPop instead
Add feature id (fid) parsing
Do not create parsers in wfs namespace if not needed
Handle that ol.xml.pushParseAndPop can return undefined
Handle undefined value at readGeometryFromNode instead
Use goog.isDef where possible
Make sure function naming convention is consistent
Remove unused ol.format.GML.NAMESPACE_URIS_
Merge pull request #1752 from bartvde/gml-rewrite

Add format for reading GML v3 (r=@ahocevar)
Get rid of unneccessary if else statements in the GML format
Merge pull request #1760 from bartvde/gmlfix2

Get rid of unneccessary if else statements in the GML format (r=@ahocevar)
Update to the latest version of pake
Remove reference to stale build/src/external/src/types.js target
Merge pull request #1749 from twpayne/windows-newlines

Generate proper line endings on Windows
Merge pull request #1748 from tschaub/roughly

Fix test failures on Chrome 33.  The trig functions in V8 have changed, and are may change again (see https://code.google.com/p/v8/issues/detail?id=3006 for the full story).  As a result, we no longer rely on Vincenty for antipodal distance calculations (not recommended anyway), and we use a very low precision match for testing cosine distance on a sphere.
Add an example that renders a simple fractal

This works at resolutions where simplification is significantly reducing the number of points in the line.  At high resolutions, navigation becomes unresponsive.  Limiting draw instructions to a replay group's extent will fix this.
Keep track of max extent for replay