Since a single mapper can use multiple shader programs it makes sense to
keep track of uniforms used in the shader program itself as opposed to
the mapper.

This topic fixes an issue where when surface with edges was on
the shaders were rebuilding every time when they did not need to
because the light complexity was shared between all the shaders.

Also when draw edges was on scalar coloring was still happening
wen it shoudl not have been.

Fix and issue with wide edges not showing up properly

This fixes:
   VTK_OPENGL_HAS_OSMESA on
   VTK_USE_X             on
   caused link errors in Rendering/OpenGL as some of the cxx
   files contained code ifdef using VTK_OPENGL_HAS_OSMESA instead of
   VTK_USE_OSMESA

In the past, one could link against both MESA and OSMESA and use OSMESA only
for off-screen rendering. In recent versions of MESA this is not the case anymore.

If a 3rd party creates the window we were not finding a
fbconfig. Also I believe we were leaking some X resources.

In some rare cases the action index may not be a index into
getPointerId.  To workaround this issue do the following

1) Change the semnatics of HandleMotionEvent to use the pointer id
directly rather than looking up from index in C code.

2) Wrap the java code in a try/catch to catch invalid motion events.

Added an event that fires when the shader updsates so that
programs can use it to update any uniforms they want to

Add methods to override the shader code templates.

Fix a minor compile issue

Add a method so that users can modify the existing VTK shaders
if desired. In the future will also need to add a method for
users to set uniforms as well and maybe eventually map data arrays
to attributes.

Fix a case where the polygon offset could be left on

Add PBO support into OpenGL ES 3 builds

Fix a warning on ES 2

Use vtkOpenGL.cmake to decide to use (LINK_PRIVATE) OpenGL or Offscreen Mesa.
OpenGL is now LINK_PRIVATE, so additional libraries and tests need to include OpenGL.
Include the following in your CMakeLists.txt:

include(vtkOpenGL)
vtk_opengl_link(${module})

for every ${module} that uses OpenGL. This takes care of include directories and
linking of proper libraries.

Made vtkFrameBufferObject be built for ES 2 as
ES 2 does support it. This required a few changes.

Made a number of fixes to the Android/IOS super build process. Fixed
the install prefix to be pushed down to the subbuilds. Made a number
of top level setting cached in the sub builds because they are cached
there already and need to be overriden in the superbuild.  Otherwise
top level changes did not propagate down.

Updated correct baseline

* Since now the API is generic
* Will not require downcast
* Also updated the var name to reflect API

We are generating unsigned char for both color and depth
and should use the same for image data as well

Minimum SDK and deployment is now 10.6.

When arrays had really large negative values, table lookup crashed.

This commit also applies the default scale to the point sprite radius
only after the lookup in the table has happened.

This allows the application to manage the memory
allocation/deallocation and the mapper just copies data to it.