We no longer need this compatibility layer for the compilers we support.
Use the following commands to switch to standard header and namespace:

 git grep -l vtksys/ios/ | xargs sed -i 's|vtksys/ios/||'
 git grep -l vtksys_ios | xargs sed -i 's|vtksys_ios|std|g'

In the early days of VTK, support for stl was not portable. vtksys_stl
and vtksys_ios provided a portable implementation of the stl. Now, all
of the VTK supported compilers have portable stl implementations.

This patch:
  1) Replaces the vtksys_ios:: with std::.
  2) Replaces the vtksys_stl:: with std::.
  3) Removes "using" statements for stl

This is a patch that fixes issues with
'vtk-kamino-osx-shared-release+mpi+python+tbb' builder.

OpenGL 3.2 does not support line width greater than 1 although
many drivers do support it. This adds valid images for cases
where line width is greater than 1.0

Also minor VisualStudio error check

If you find each qt5 component directly, you have to specifiy the path
to Qt5 config files for each component. If you use
find_package(Qt5 COMPONENT component), then you can specify one Qt5
config directory and all the components will be found.

This is not supported by the new OpenGL2 backend, and doesn't support
new text features, like MathText, FontConfig, or custom font files.

It only implements vtkTextMapper, which now will use a texture-based
implementation, similar to vtkTextActor and friends.

Also removed some dead code as a consequence,
like setting the deallocated pointer to null
then to a new address.

Also removed setting some ivars to null in dtors.

A few good fixes in here that are all related. The biggest is a
fix to OpenGLActor to use the more comprehensive GetIsOpaque
method in determining if an actor is opaque. The old code only
looked at the property's opacity. This is why you would see folks
setting somethings opacity to 0.99 to get it treated as translucent
because the actor code wasn't handling it correctly. This change
resulted in 3 new valid images for tests that were rendering
translucent items as if they were opaque. I removed these tests
from the old backend as I did not want to change the behavior
for that backend.

Next up is depth peeling. OpenGL2 depth peeling would render
a number of peels up to the limit and then just stop. Any geometry
left between the opaque layer and the last translucent layer was
just thrown out.  This created very noticable artifacts and was bad.
This change makes it so that when it gets to the last pass, it will
render all remaining geometry using alpha blending. This is much
better. Fix example if you get the limit to 20 layers and 20 was
not enough to render all the geometry, this change renders 19
layers using depth peeling, then in the 20th render it would add
in all the remaining geometry as last layer. That last layer may
have overlapping geometry which is rendered using alpha blending.

Finally some changes to the PointGaussianMapper. It turns out that
the point gaussian mapper is an translucent mapper which means it
needs the first change, and it is a very tough case for depth peeling
resulting in the second change. While at it I modified this mapper
to render far fewer fragments, resulting is far fewer overlapping
layers and fewer artifacts. Really when using PointGaussian you
should turn off depthpeeling as it is not needed and actually makes
it worse, but these changes will make it better if you happen to have
it on.  Also cleaned up the mapper so that the radius is equal to
the standard devisation of the gaussian, previously it was four
standard deviations.

Change-Id: I62d90b6e424ac0e939033387ed10ba8caac66095

Change-Id: I5adee5e4e29ae03aa4363550a11a044d447ae74b

1. Fixed TimerId type. vtkRenderWindowInteractor defines the TimerId
type as int. vtkContextInteractorStyle now uses the same type.

2. Fixed timer creation. OnSceneModifed() was repeatedly creating new
timers even when previous one hadn't timed out yet. Fixed that. Also,
RenderNow() ensures that old timers are destroyed.

3. RenderNow() now uses Interactor->Render() rather than
Interactor->GetRenderWindow()->Render(). vtkRenderWindowInteractor has
API to control how and if an interaction should trigger a render on the
window. Calling RenderWindow->Render() bypasses all that logic resulting
is mismatch between how interactions work in Render views and Chart views.
This fixes that issue.

Change-Id: I58798615070d97ba9a00ccc21919a5d518bdac22

Thanks to Maarten Beek for pointing this out on the VTK users list.

Change-Id: Ic964ff5bb3b8c69560ff7c80a1a0eee976ff5be3

Used the following command:

find . \( -iname *.h -and -type f \) -exec perl -pi -w -e 's/__vtk(.*)_h/vtk$1_h/g;' {} \;

Fixes many, but not all, clang -Wreserved-id-macro warnings.

Change-Id: I694ff053cb204c70e37b261296f496064d91fc07

The one shot timer could still be fired after the interactor style
was removed.

Change-Id: I7425293ecf78745504c247169848df0958287be9

Change-Id: I76848acf2f0939f63df6c3194b302eebd6a68009

This change makes more modules dynamically switch between the
rendering backends if they have no OpenGL code, or introduces some
ifdefs in the case of RenderingParallel (which may not be functional
at this stage). Added RenderingFreeTypeOpenGL2 which will also need
some additional work before it is properly integrated with the new
rendering backend, but it surprisingly seems to render on the
desktop.

This commit contains everything needed to get a minimal ParaView
build using the new rendering backend for polygonal rendering.

Change-Id: If8676d41d263b046a54060965fc760b5d4bd64a1

Did this for cxx files where another vtk include was already
using the "" style.  I find this is more correct, especially
for implementation files.

Change-Id: I632178a9af13991ccba96bfaabf5ccc4bfea3c18

This resolves PGI ~ 600 warnings "#111-D: statement is unreachable"

Change-Id: I9937c4f22eec4e9f56b6b770e35a6a1ca7390974

Lots of places where we pass floating point values as integers; make the
loss of precision more explicit.

Change-Id: Icafde395f0463421b5f36d1e4e855fa25cab5ab4

Storing these as integers truncates the actual value when restoring.

Change-Id: I5fd5eee053db12a1c96c51dd359cd9410d0f68a6

The main kits are:

    vtkCommon
    vtkFilters
    vtkIO
    vtkImaging
    vtkInteraction
    vtkOpenGL (required due to a dependency cycle from
               vtkRenderingOpenGL on vtkImagingHybrid)
    vtkParallel
    vtkRendering
    vtkViews
    vtkWrapping

Modules which deal with a specialization of another module belong to the
kit related to the specialization (i.e., FiltersParallel and
IOParallelXML both belong to the vtkParallel kit) to avoid circular
dependencies that arise when put into the same kit as the "lesser"
module.

Change-Id: Icae0baa78d62cc0dcce84546541df600d4f311dd

This adds dependencies to tests that were missed in the initial move
for vtkRenderingContext2D.

Change-Id: If816a2a15ca02bca8c5f736872d4166b90f73bcf

This enables us to compile the Geovis module without depending on
the OpenGL implementation, after discussing it with Aashish this
class may be deprecated and removed in the future.

Change-Id: Idecf270f2d71e884a89d2b90836a6e6fbea9807c

These can only build with the OpenGL backend.

Change-Id: I7f95de24b0ad064a7ebe04b028cd9808857b35e4

This will enable us to switch the backend at will, the OpenGL works
whereas the OpenGL2 needs some additional improvements mainly to
use point sprites (where most of the tests are failing.

Change-Id: I648c18ca33b4c6796c4b7a829a2902f7e91ff412

The Mesa Gallium 'swrast' driver combines pixel-wide overlapping lines
differently, but validly.  Add a baseline representing its result.

Change-Id: I31973e8a6b6776fdb322f6efa8c09b3ac9446525

Qt5 packages provide libraries to VTK in the form of imported targets.
VTK libraries that link to them get exported with dependencies on the
imported targets.  We must make them available to applications that link
to these VTK libraries too.

Teach each module that depends on Qt5 to export code that runs when
an application loads the module as part of its build process.  Find
the needed Qt5 package on behalf of the application to satisfy the
module's dependency on it.

Change-Id: Ib638ccafa084fbb06c20eb09464265501ccafc80

Change-Id: I10a54acbd076e055d8071414f2fff1ebafe1653d

Change-Id: Ibd1956b5e76f47e39f08fd787f57e0688312f6fd

As of this commit, we no longer assume that the 1st column of
the input table specifies the names of the table's rows.  Instead,
we search by default for a column named "name".  The user can
change the name of this array by calling vtkHeatmapItem::
SetNameColumn(vtkStdString).  We fallback to using the 1st column
only if no such array can be found by name.

Change-Id: I2494ff21f3efa4a379dce82e159715dc023d8995

Apparently functions whose signatures contain vtkSmartPointer
are not wrapped into python.  Change such methods of
vtkTreeHeatmapItem to contain ordinary pointers instead.

Change-Id: Ic98311c10f1e7a99fb4ad071d3981e4febb0604e

Various places used abs(), which takes int, when dealing with
floating point numbers.  Use fabs instead.

Change-Id: If6f2f3784f199a3a60dcf0d1e8e96bf5ee4deb92

Also made some const correctness improvements,
which cascaded to clients of this class.

Other misc cleanup too.

Change-Id: Ic7688a12949a9b8cc752afb957e13317e50ba085

vtkParallelCoordinatesView was not tested. The lack of a test
resulted in low coverage for vtkParallelCoordinatesView,
vtkParallelCoordinatesRepresentation and SCurveSpline.

This patch also repairs a memory leak in
ParallelCoordinatesRepresentation that was uncovered when the test was
added.

Also, since vtkSCurveSpline is only used in
vtkParallelCoordinatesRepresentation and vtkSCurveSpline did not have a unit
test, this path moves vtkSCurveSpline is moved into Views/Infovis.

NOTE: vtkParallelCoordinatesView has a lot of interactive content. To
improve the coverage, future tests must exercise the interactive parts
of this class. This patch is a minimal effort at improving the
coverage.

Change-Id: I1dfe93ecb1db85edfc5a887c4576c6274e8284ea

vtkDendrogramItem now displays a vtkColorLegend after SetColorArray()
has been called.  This allows the consumers of this visualization to
see the scalar values associated with the colored edges of the tree.

This commit also contains a bug fix.  When SetColorArray() is called
with an array that only contains a single value, the edges of the tree
should be drawn in grey.  This bug previously caused such edges to be
drawn in either red or blue.

Change-Id: Ia897109b119029e57e053b368dc910fb87266a76

The previous commit (9c5d6061) changed the orientation of the
collapsed subtree label in this test.  While the prior orientation
also looked nice, it was a side-effect of the orientation of the
heatmap's column label.  Thus, it was subject to change based on
what order the items in the scene were rendered.  It also did not
look correct for all possible dendrogram orientations.  This new
baseline depicts the label where its orientation is determined
by that of the dendrogram.

Change-Id: Ia6ef68ff573234f1e189a3124bc92295ac85ba6a

This commit fixes a bug that affected the labels that indicate how
many vertices are hidden within a collapsed subtree.  The size and
orientation of these labels would potentially change based on whether
or not a vtkToolTipItem was currently displayed.

The problem was that vtkToolTipItem modified the vtkPen, vtkBrush, and
vtkTextProperty used by the painter.  This commit changes this behavior,
so that the original painter settings are restored after the tooltip is
drawn.  This makes the appearance of the rendered scene less dependent
on the order in which the items are painted.

Change-Id: I48acba6313a63539a2116cd8d2929fe8ab162de8