Initial commit for public, open source repo
Finalize packaging settings for initial public installer release

Also, added build rules for EventMonitor example and made it one
of the pre-installed examples.

Cleaned up a few comments and incremented the "artifical svn
revision" version number, too.
Add Save/Restore camera functionality.

And also, an ErrorEvent handler for the vtkOutputWindow.
Example code for demonstration purposes only.
Exclude class vtkProcessingUnitResource from wrapping.
Exclude class vtkColor4ub from wrapping.
Exclude class vtkContourRepresentationNode from wrapping.
Relax naming restriction in the test parsing code

Previously, the VTK source directory had to be named "VTK"
in order for all the tests to be added correctly. Now it
can be named anything you want. The universe is yours.
Increment ActiViz .NET manual version number component

For the VTK 5.8.0 release
Add a definitive ActiViz .NET SuperBuild

Make it easy to build all the prerequisites, with all the
right settings, in both 32-bit and 64-bit flavors, and have
installers pop out at the end of the build. Bam!
Run python scripts from binary dir, avoiding source tree clashes

Previously, multiple simultaneous builds using the same source tree
could clobber each other's generated python scripts because they were
generated in the source tree. Now all python scripts are copied to
the build tree before running, and generated files are written only
in the build tree. Multiple simultaneous builds should not be a problem
now...
Add an exemplar script for building ActiViz releases on Windows

The default installation paths for CMake and git on a Windows x64
machine are assumed. The script may be run on any Windows machine
after simply tuning the "set ...=" lines near the top for any
machine specific differences.
Allow override of VTK and VTKData versions or tags

Set environment variables before running the SuperBuild script
to use different-than-default git tags for the VTK and VTKData
checkouts.

Either set AVSB_VTK_VERSION if there are v${version} and
v${version}-data tags...

Or set the tags individually with AVSB_VTK_GIT_TAG and
AVSB_VTKDATA_GIT_TAG.

(That way, you can build against specific commits in VTK and
VTKData, or against origin/master, ...)
Exclude newly introduced, non-vtkObject-derived classes from wrapping
Remove pause calls from the SuperBuild driver batch file

Some scenarios require automated running of this batch file,
so pause is an inappropriate batch file construct. Users who
would like a "pause" call at the end, to keep a double-clicked
batch file's cmd prompt alive, may write a simple wrapper batch
file that calls this one, and then does the pause.
Add a new way to parse vtkCommand.h...

...since the list of events in there completely changed form and
could not be parsed using the same regular expression that used
to pick out enum value names. Allow for both forms so this same
ActiViz code can be used to build against older VTK's and also
this new style.

First, we try to parse lines like this:
  AnyEvent,
  DeleteEvent,
  ...

Then, if none match, we parse lines like this:
    _vtk_add_event(AnyEvent)\
    _vtk_add_event(DeleteEvent)\
    ...

Both styles of parsing are limited to sections between matching
"begin" and "end" lines as well.
Add new utility libraries required by new VTK code