Flexible, Image and Registration: fixed compilation without openmp and zlib

git-svn-id: svn://scm.gforge.inria.fr/svnroot/sofa/trunk@9717 b7f1a160-662a-0410-a6d8-bea165342f16
Compliant: removed unneeded (?) apply in assembled mapping init

git-svn-id: svn://scm.gforge.inria.fr/svnroot/sofa/trunk@9718 b7f1a160-662a-0410-a6d8-bea165342f16
Compliant: including AssembledMapping.h in project

git-svn-id: svn://scm.gforge.inria.fr/svnroot/sofa/trunk@9719 b7f1a160-662a-0410-a6d8-bea165342f16
fixing a warning

git-svn-id: svn://scm.gforge.inria.fr/svnroot/sofa/trunk@9720 b7f1a160-662a-0410-a6d8-bea165342f16
DAG: fixing Directed Acyclic scene Graph traversal while the graph structure is modified (adding/deleting nodes) during the traversal.

The traversal flags per visitor are now stored as a map on DAGNode* and the scene graph structure (that can change) is now used for the traversal. Rather than performing the traversal on a precomputed, static sub-graph structure that was not considering the scene graph structure changes.

Note: there is still an undetermined case, when a visitor is run from a sub-graph that contains a multi-node linked with a node outside of the sub-graph.

git-svn-id: svn://scm.gforge.inria.fr/svnroot/sofa/trunk@9721 b7f1a160-662a-0410-a6d8-bea165342f16
DAG: fixing the last (?) undefined operation, when running a visitor from a sub-graph containing a multi-node having as parent a node outside of the sub-graph.
A MultiNode is only waiting for its parents in the sub-graph to be visited (and ignore the parents outside of the sub-graph).

The chosen solution to know if a node is in the visitor sub-graph:
- a list of all descendancy nodes is stored in each node. This list is update at each graph topology change (addChild/removeChild....).

other possible solutions:
- building this descendancy list each time a visitor is run, less memory used, but add an overcost at each traversal rather than at each scene graph topology change.
- maintaining an ordered list of descendancy traversal in each node. The ordering test would be done at each scene graph topology change rather than at each multinode during the traversal.

git-svn-id: svn://scm.gforge.inria.fr/svnroot/sofa/trunk@9722 b7f1a160-662a-0410-a6d8-bea165342f16