Change-Id: Ifc76340e581c5cf07b6c40b7ecd77f292b96962b

In commit 4a8b64c5, the lex rule for std::string was changed to avoid
conflicts with std::stringstream.  Unfortunately, the new rule contained
an error, causing std::string to be ignored.

Change-Id: I38781b2f4e4b2be67818c2b05c4677a3eea91d02

Mainly
lying -> laying
loose -> lose

Change-Id: Iaa639ebcf5262ea6dfeb25cf21d6c49b5020458b

This fixes a number of misspellings in the comments of
the source files in VTK/Wrapping. The misspellings were
found using the codespell tool.

Change-Id: I118d654d6e93caefd0541586416aa0d77690be33

The API has been deprecated for quite some time, and has now been
removed.

Change-Id: Ibe74e6f4f9cd9bed3dfeced59ba1d1e50a822cbe

We missed one variable required by the Python wrapping, which must be
defined to 0 if the kit is not being built.

Change-Id: Iba44f3c1af27bcd22ab97d1f9d4ec2fab7414bf5

Change-Id: I0ae4289d6547667527791f8a70b68be97ba06a65

We may use only one thread library at a time.  Instead of presenting a
separate option for each one just choose the preferred library for the
current platform automatically.

Change-Id: I279057b968990b71163eeb90ce080fec83254cb3

Enable python wrapping for AMR kit iff VTK_USE_PARALLEL is defined.

Change-Id: I2dac22e46171e7322cb8c5a3eafb62f5635707c2

In C++, the vtkTuple class and its subclasses no longer initialize
their contents in the default constructor.  In order to maintain
backwards compatibility within VTK/Python and to make the behavior
more pythonic, the wrappers now perform the initialization.

The behavior is not completely backwards-compatibile, because the
vtkColor4ub class used to initialize to [0,0,0,255] and now it
initializes to [0,0,0,0], ditto for vtkColor4v and vtkColor4d.

Change-Id: I056992dfb47b8ea1c0927c7ecc621a3e0649932b

Change-Id: I56df087532aa1071cae12aefff47a819275c6a6c

In Python 2.7, the inspect.isclass() method became more restrictive,
and the python documentation system stopped recognizing VTK classes
as true Python classes, since VTK classes still use a mechanism from
the days of Python 1.5.  This patch makes PyVTKClass into a subclass
of PyClass, and now the inspect module recognizes VTK classes as true
Python classes.

Change-Id: I83fa6b5adb7fdef53036069a83a2dae64dffd4ae

Change-Id: I9da81d39f25807c01fc01ad5a584a5c8923c93d7

Change-Id: I755286dda63769566962bf2532b84b5c36cd77ce

The new vtkAtom and vtkBond types did not define a default
constructor, and as a result, wrapper code that used these
types would not compile.  This new wrapper code needs only
a copy constructor and assignment operator, it no longer
requires classes to define a default constructor.

Change-Id: Id0d06787fc8798eb5fa1e343059ad07079332cf2

The python str and repr methods could recursively reference each
other if special-wrapped types did not define a str method, which
occurred when the C++ header didn't define operator<< for streaming.

Change-Id: I29ba591ac933a37401674ad40d94d60e88d06a70

Change-Id: I90237d2244b020afdf9f6d2597847fea0df07885

Change-Id: I0d3d879a44cfd20b2b3fc0af627ec9bdd056f475

Fix a compile error with Paraview.  Subclasses of the templated
vtkSIVectorPropertyTemplate class failed to wrap, due to expansion
of the vtkSIVectorProperty macro.  For now, I've disabled expansion
of macros that aren't function-like macros.

Change-Id: Iaf19efa2e31c823f4f3d2a82c7be00b43b44679b

Allow the wrapper's preprocessor to perform macro expansion.  Prior
to this change, only a few function macros that were hard-coded into
the wrappers could be used in the VTK headers.  Custom macros would
previously cause the wrapper generation to fail.

Some macros are not expanded for the sake of backwards compatibility:
1) VTK_* macro constants are not expanded, since these are recognized
by some of the later stages of the wrapper processing.
2) vtkDataArray, if defined as a macro, is not expanded in order to
allow the vtkDataArrayTemplate superclass trick work as before.
3) All previously hard-coded macros such as the vtkSet/Get macros are
still hard-coded for now, to ensure backwards compatiblity

Change-Id: I96deec4b9c98badfed88831027011904d197840f

In VTK, the name "tuple" seems to be preferred for this sort of
entity, e.g. the GetTuple() methods in vtkDataArray.  Another
reason to change the name is to further assert that a color is not
a vector, which is why vtkColor is no longer a vtkVector subclass.

Change-Id: I37fa2b9c797d34dd0dbcbd7640ced9450d7f3aba

Only one VTK class is impacted by this change: a vtkIdType reference
was returned by vtkDataSetEdgeSubdivisionCriterion::GetCellId().

Change-Id: I31432d68b7732030b9b10e4a53f1fdd9a4df6174

This reverts commit 318624b0.

Only one VTK class is impacted by this change: a vtkIdType reference
was returned by vtkDataSetEdgeSubdivisionCriterion::GetCellId().

Change-Id: I39e6faab346c3457c7f3a45e55fb9aa8fc65cccc

It isn't clear, but I suspect these lines could be removed entirely.
There is another wrapper file with some references that should likely
also be fixed.

Change-Id: Ibaaa36648f55da0d7c229d4cfd47f8705fb9e7a6

The vtkstd forwarding headers are deprecated, move to using the STL
headers directly.

Change-Id: Iaeb5ea0c10d40b8e934b6a8ca18f28c3b022b924

isprint() was asserting for accented characters on VS 2010. Fixed that by
detecting extended ASCII characters explicitly.

The vtkVectorBase class must be in its own header file or else
it cannot be subclassed by the python wrappers.

Change-Id: Ibf70505ea17fe10a962ce54eb2af5f640a028450

Classes that use vtkTimeStamp as an interface type would be incorrectly
wrapped, if wrapped via a third-party package.  This was due to a typo
in vtkWrapPython.c which caused "#include <vtkTimeStap.h>" to be written
into the wrapper file.

Change-Id: Ief6507a8eb67a217a5e63c8ce3804054b45f7a46

Change-Id: I29a3dc3d942eab89453a433692899a66fdf7d4a3

Change-Id: I8ea03dd6bcad307ac52ca9d64fe67a20c8a8e5cd

SetImageConnection(a) is the same as SetInputConnection(1,a)
where, a=vtkAlgorithmOutput*

vtkImageDifference changes:
Use GetInputConnection(0,0) instead of GetInput()
Use GetInputConnection(1,0) instead of GetImage()

For a filter to do GetWholeExtent,
instead of,
   extent = filter.GetOutput().GetWholeExtent()
new method is,
   extent = filter.GetExecutive().GetWholeExtent(filter.GetOutputInformation(0))

For a vtkImageData object, SetWholeExtent and SetUpdateExtent methods are not required.

vtkType.h defines data types that can be used by vtk classes. One cannot access these datatypes in tcl.
We have to declare an environment variable based on type defined in vtkType.h. Example in Graphics/Testing/Tcl/blankgrid.tcl

Added an entry in the Wrapping/hints file to give its signature to the wrapping mechanism. The method gets wrapped now.

When there are multiple include directories for MPI,
as happens on Ubuntu with openmpi, quoting the argument
to INCLUDE_DIRECTORIES causes both to be treated as
one path, and MPI includes cannot be found.

Also adding some API to vtkDataReader/Writer to take advantage
of the new functionality.

Change-Id: Ice2d7ce8d772ac7a0409e021799263acfbe21204