- This calls `VTKRenderer::setRenderWindow`. Needed to use a
vtkRenderWindow from another instance (example : for a QT
application, use QVTKWidget renderwindow)
- Rename `VTKViewer::getRenderWindow` to `getVtkRenderWindow`
- Use internal functions in `getVtkCamera` and `getVtkRenderer`

Allows for the following workflow :
1) Create a `VRPNDeviceClient` by specifying its URL (name@ipadress)
and its type (see `DeviceType` class). The subclass `VRPNForceDevice`
is setting the style to `PHANTOM_OMNI` by default for now.
2) Create a `VRPNDeviceServer`
3) Call `VRPNDeviceServer::addDeviceClient()` to add the client created
on step 1). This will analyse the IP, name, and type of the device
client to instantiate a VRPN device connection. The added devices are
then stored in three `std:map` so the `mainloop()` can be called during
the execution.

Updated their use in `FEMSimulator` and `LaparoscopicCamera` examples.

Many are formating changes and others are
bug fixes as well as some refactoring.

from SimMedTK to iMSTK.

Modify the license notice in each file.
Add LICENSE file.

from SimMedTK to iMSTK.

Modify the license notice in each file.
Add LICENSE file.

by examples and unit tests.

Revert some changes and make it build, run FEMSimulator example

CollisionContext/CMakeLists.txt was contributed by Sreekanth.

iMSTK time stepping method.

classes.

and their tests. Streamline and refactor
time integrators and their tests.

Refactor ObjectSimulator.

classes. Also create a SimulationManager in charge of
running the simulation.

module.

- Migration of the camera update by external device
from VTKViewer to LaparoscopicCameraController.
- Removal of obsolete cameraConfigurationData struct
- Cleaning of unused variables and of style
- Simplification of the cameraController feature
in the LaparoscopicCamera example.

In the LaparoscopicCamera example the mouse interaction
was supposed to be disabled, but by setting the new
interactor style after the viewer initialization, the
observers rules on the vtkViewer interactor were
overridden. Placing the interactorStyle beforehand
resolves the issue.

In the future it would be convenient to have wrapped
functions in IMSTK to make changes to the interactor
without the need to go through VTK.

- Also replace GL/glew by vtk_glew in Core/RenderDetail
- Remove empty first line in those

All examples should follow the same conventions.
Name of the application should match the directory name containing it.

AVMNidus was used to test the shaders, but
was not showcasing its main usage anymore.

This commit divides the example by migrating
the Shaders test into another example (Shaders)

Also incorporated the data for this new example
in MIDAS to download it during the build.

Also fixed some shaders errors.

Removing RenderDelegates, OpenGLRenderer, OpenGLViewer

- need glew.h in Core/RenderDetail for GLint
- need to link against Geometry in AVMNidus
- remove duplicated library in Rendering

- Remove RenderDetail::setTextureFilename() and co.
- Remove MeshModel::addTexture()
- Remove SurfaceMesh::assignTexture() and co.
- Use RenderDetail::addTexture()

Still need to assign texture in model?

The 3ds file loading and attachment  of VAO for the tangents
for 3DS file are working fine now.

The renderdetail has been changed to accommodate these modifications.
The wet shader shader code is a bit modified.

Clean-up of the code is needed

Needed for custom shader attribute declarations such as tangents.

The resource CameraNavAppData has been updated on midas3 to remove
the unused block.vtk and correct the architecture of the directories.

New SHA1 : 405ac1c0c2bb5a7ef5395887ae2b8fcc620493f5

This commit adresses issue #55

1) Define values to automate the creation of the blocks
2) Use a texture to display the targets
3) Create a 2D overlay using a 2d actor image instead of charts
4) Rename ScreenCaptureKeyPressEvent to ScreenCaptureInteractorStyle
5) Restructure scene creation and viewer initialisation

of the vtk's windowToImageFilter