This will make it easy for external applications to find and use
paraview web content in a consistent manner.

Change-Id: Id6616046fad40821fdecb6cbf3acf74616fa8a07

To make it easier to develop adaptors externally, as well as add ability to
enable/disable Python capabilities in Catalyst, we refactored the CoProcessing
modules.

Two new modules were added vtkPVCatalyst and vtkPVPythonCatalyst. These two
libraries/module provide the Catalyst components necessary for coprocessing.
These also provide a C/Fortran API (through CAdaptorAPI/FortranAdaptorAPI or
the Python enabled CPythonAdaptorAPI/FortranPythonAdaptorAPI headers) that can
be used within C/Fortran simulation codes.

Adaptors are now moved to CoProcessing/Adaptors. They have now been updated to
be able to built outside of ParaView build directory i.e. users can directly
point CMake to ParaView/CoProcessing/Adaptors/CTHAdaptor as the source directory
to build the CTH-Adaptor. They will have to point to an existing ParaView build,
of course, like any other ParaView dependent project.

ParaView-build builds these adaptors as a separate project (similar to the way
we build examples). This can be disabled by using the advanced cmake variable
PARAVIEW_BUILD_CATALYST_ADAPTORS.

Also, fix static Python modules initialization. Added a new module in
Utilities/PythonInitializer which exposes a C function to
initialize Python modules for static executables. All executables now simply
link against this one and call the initialization function to init Python.

Change-Id: Icaacdf8a0d32e03742fbc302008c4ab45c40a22a

This are simple examples that are not installed
with ParaView.

Change-Id: Id2365d50d7e1c6c167fd12cdd2aa1c0115ada4d5

When appending ParaView_BINARY_DIR to VTK_INCLUDE_DIRS the property
must be quoted. Build directories with spaces in path will cause issues
otherwise!

These (along with some pending VTK changes) address issues that pop up when
building ParaView's Examples with an installed version of ParaView (installed
using PARAVIEW_INSTALL_DEVELOPMENT_FILES to ON) on Unix machines.

Change-Id: I8c9fc97da01b7988c55539ec7b8b837a28b0ea4f

Exposing some ParaView options and adding a new variable PARAVIEW_INCLUDE_DIRS
(same as VTK_INCLUDE_DIRS) just to make it easier for applications.

Change-Id: I4e0390df2a8761d0f30c4a6a2b6959ca9acd6aaa

This avoids having to overwrite VTK's targets file. Also will make it easier
when we start supporting external VTK.

Change-Id: I6f564c6c28ee4842f5572724139dad982f8a2686

Change-Id: I6227e461150eb9e958a8580ec665a671b99247ce

Change-Id: I88b573c06142aeea10566ad36d4a64fb92a09418

Change-Id: Ia8c3e192abea75019e3af6a8430be523a74b196c

We now use "git describe" to determine the version for ParaView. Thus we no
longer have to use minor/major version number trick for releases. "git describe"
returns a string such as "v3.10.1-1701-g427f283". The version is then set as
follows:
Major: 3
Minor: 10
Patch: 1
Full : 3.10.1-1701-g427f283

If Full=="Major.Minor.Patch", then it's treated as a release.

Release candidates can be tagged as "x.y.z-rcN" and the version will be set
correctly.

If git cannot determine the source version correctly, then
"CMake/.paraview.version" file is searched for and we try to parse the version
string from this file. It's a fatal error is both these approaches fail.

Fix conflicts with collaboration branch.

COMP: Changes so that if coprocessing is enabled in paraview that the coprocessing libraries and include directories will be loaded in too.

defaults are used when none are specified.

ENH: Fixed shared forwarding to work correctly with custom apps when not
building custom apps with rpaths enabled. Now when running from build directory,
it finds paraview correctly even without rpaths.

just the names and not full paths making it easier to use/understand.

This commit makes it possible to make custom clients based on ParaView. There
are a host of changes in this commit that restucture the Qt client level
classes.

For more details refer to the following links:

http://www.paraview.org/ParaView3/index.php/ParaView-based_Applications

http://www.paraview.org/Wiki/Writing_Custom_Applications

shaders etc.

BUG: Quote paths.

ENH: Added development files to make install.

ENH: Export Qt and GUI settings.