Directory structure + Component/modules update

Hello,

I propose a more defined directory structure for Orocos.
As Anthony mentioned before, the components should refer to each other 
through a 'common' include, doc,... directory. So for the code case, the 
include directory should contain the ORWIN wrappers.

Orocos/
|
\-----include/ (--> ORWIN component interfaces)
|
\-----heartbeat/
|
\-----other component/
|
\-----modules/  (--> common modules can be used in all components)
	|
	\-----include/ ( --> ORWIN module interfaces)
	|
	\----------src/
		|
		\----threading/
		|
		\----InterComponentCommunication/
		|
		\---other modules/

since modules should also be non-fixed (different implementations should be 
in-pluggable), they are defined through ORWIN interfaces.  

The class names in the interfaces should be like:
OWMatrix 	// OW == OrocosWrapper
or maybe
OWIMatrix 	// OWI == OrocosWrapperInterface

OW is shorter, but OWI is technically speaking more correct.

Herman suggested to also use an "arch" (-itecture) directory for os specific 
implementations (maybe 'os' directory is more appropriate).  As I see it now, 
this would only be needed in the modules directory (since components are 
``os-agnostic'').

comments / incompatibility issues are wellcome.

My next mail will go deeper into the kind of modules and components that we 
have identified.

Peter