Add a pose to the SceneElement
Add constant accessor getSceneElement to Component
Representation's pose dependant on the SceneElement

Calling getPose on a Representation now returns the combined pose of the
Representation (get/setLocalPose) and the SceneElement's pose. The local
pose is the pose of the representation with respect to the SceneElement.

Also, now physics representations can 'drive' the scene element. Using a
DriveElementBehavior the pose of the physic representation will provide
the pose of the element. So other representations' poses will be updated
as the physics representation updates the element pose. There is
similarly now a DriveElementFromInputBehariour that allows an input
component to drive an element. These two behaviors remove the need for
the TransformPoseBehaviors.

Removed MockObjects from Blocks since the only place these MockObjects
were being used was actually in the Framework Unitests. So moved the
objects from blocks MockObjects in the MockObjects in Framework.

Updated all unit tests and examples to reflect these changes.
Add Camera to View Element

Add a camera to the ViewElement so it can be posed more intuitively.
Since Representation (which a Camera is) can be posed by there elements,
this provides a SceneElement for Camera's to live in.  This should be
easier than the default camera (that does not live in a SceneElement).
Since the ViewElement (which is a SceneElement) has a pose, you can set
the ViewElement's pose, and this will move the camera. Instead of using
the less intuitive setLocalPose of the camera, and assuming that it
isn't accidently in another SceneElement that could get posed.
Cleanup Bouncing Balls Example
Fix VisualizeContactsBehavior not respecting element pose

VisualizeContacts get the contact position in the global coordinates.
However, the vector field representation lives in an element that could
have a pose. So we need to put the vertices of the vector field in
element coordinates.
OsgMeshRepresentation was not calling its parents update

OsgMeshRepresentation overrided the update call instead of implementing
the doUpdate call. This resulted in the m_transform not getting updated,
and moved according to the global pose of the representation. This
change just implements the doUpdate, so the OsgRepresentation::update
will get called.
Fix whitespace and comment issues from pose changes

Fixed some long line lenght, trailing whitespace, and missing explicit
in a constructor.
Add a PoseComponent

Instead of SceneElements holding a rigid transform, they now contain a
pose component that Representations use as their base pose.
PoseComponent is now discovered by Representations

Instead of setting the PoseComponent when you set the SceneElement of a
Representation, Representations "discover" the PoseComponent on wakeUp.
Move PoseComponent discovery to Component

Move the PoseComponennt discrovery from the Representation to the
Component. This allows for the wakeUp to be returned to non-virtual.
Since PoseComponent is a Component, it now has a PoseComponent. To
address this, it overrides getPoseComponent to return nullptr.
Make DriveElement behaviors serializable

Add the needed functionality to serialize DriveElementBehavior and
DriveElementFromInputBehavior.
Cleaned up changes from adding a local pose

* removed unneeded forward references and includes
* fixed types and improved comments in Component, SceneElement
* consistently call getLocalPose in Representation
* ensure ViewElements have a camera and view on initialization
Remove DriveElementBehavior

Instead of using a behavior that drives the SceneElement with a Physics
Representations instead just have the Physiscs Representations drive the
SceneElement directly. Also, added a flag to PhysicsRepresentation so
you can turn off this ability. But the default behavior, is that if a
PhysiscRepresentation is added to a SceneElement in will be changeing
the SceneElement pose in afterUpdate.
Removed unneed includes and forward references in PoseComponent
Rename isDrivingElement to isDrivingSceneElementPose

Rename isDrivingElement to isDrivingSceneElementPose in the
Physics::Representantation. This makes it more clear as to what is being
driven.
Require that SceneElements have a PoseComponent

Before we were just checking that there are no more than one
PoseComponent in a SceneElement. Now we check that there is one and only
one PoseComponent.
Fix all doxygen warnings
Fix newly created cpplint warnings
Osg"Keyboard/Mouse"Handler: rename "_2" parameter