Correctly bind framebuffer for readPixels.
replace functions in code
isEnabled -> enabled
check sandcastle, update CHANGES.md
doc cleanup
Fix ModelNode.matrix doc
Do not use a texture pool for imagery textures.

In current versions of Chrome, at least, using a common texture pool for
both directly-loaded imagery textures (not mipmapped) and for reprojected
imagery (mipmapped) causes mipmapping artifacts.  Higher mip levels of
some textures end up with old data (ie: textures from other parts of the
globe).  Using two texture pools instead of one would solve the problem,
but since we don't seem to be gaining much by the texture pooling anyway, I'm
just ripping it out in the name of simplicity.
isFullscreen -> fullscreen
Update CHANGES.md.
Remove TexturePool entirely.
Fix failing tests.
Clean up tests for OIT and FXAA support.
Remove unnecessary check for texture.destroy.
Merge pull request #1575 from AnalyticalGraphicsInc/noTexturePooling

Do not use a texture pool for imagery textures.
Add comment
Merge pull request #1412 from AnalyticalGraphicsInc/oit

Order Independent Transparency
Merge pull request #1573 from AnalyticalGraphicsInc/replaceGetSetCore

Replace get/set functions with properties : Core
Expose `DataSourceDisplay.defaultVisualizersCallback`.

This allows applications to install new visualizers globally, since Viewer doesn't currently provide a way to customize them on a per-DataSourceDisplay level.
Merge branch 'master' into issue1487
Merge pull request #1576 from AnalyticalGraphicsInc/dataSourceDisplayVisualizers

Expose `DataSourceDisplay.defaultVisualizersCallback`.