Interface related criteria can be handled in the MeetsCriteria in the
BaseComponent as well as the iterator over criteria, other (developer-user) specific Criteria are deligated to
MeetsCriterum per iteration.

Interface related criteria can be handled in the MeetsCriteria in the
BaseComponent as well as the iterator over criteria, other (developer-user) specific Criteria are deligated to
MeetsCriterum per iteration.

All example components have the propertie ClassName as selection
criterium.

Moved ComponentSelector classes to ComponentInterface, moved Examples to
ComponentExamples. Made all Examples adhere to ITK factory functionality.

- Changed to namespace selx
- Combined componentbase classes and based it on itkLightObject
- Initial combination of example components
- Made templated ComponentFactory to replace all specific factories

project

casts for the handshape are put in the acceptor generalized.

The functionality lives outside of the elastix project and serves as
toy example / prototype, without being complicated by ITK compatibility.

ENH: ELASTIX-9 Only access connections via component indexes; BUG: ELASTIX-9 ComponentExist() did not work

The ENH: We deliberately avoid using connection indexes, but instead
force the user to think in terms of components which is conceptually
simpler and results in less pointers being thrown around while
constructing the blueprint.

The BUG: Temporarily disable functionality for deleting component until
we find a god way of asserting that vertex exist before it is accessed.

vs elxRequiredITKModules