add palette-datatypes.png

Signed-off-by: aradermache <ansgar.radermacher@cea.fr>

modular.adoc

@@ -6,7 +6,7 @@
 
 A component definition diagram models the internal structure and external interface of a component. The former includes parameters, activities and functions, the latter ports that provide or require services
 
-[[Image:Papyrus-robotics-palette-component.png]]
+[[Image:compdef/figs/comp-palette.png]]
 
 == Service definition ==
 
@@ -20,16 +20,14 @@ This diagram is used to define data types, including those with variable element
 
 The Palette it shown below.
 
-[[Image:Papyrus-robotics-palette-datatypes.png]]
+[[Image:servicedef/figs/palette-datatypes.png]]
 
 The UML realisation is based on datatype definitions.
 
 Not all data types are communication objects. In order to avoid duplicates, the palette of the diagram only enables the creation of the different data-type variants. At any moment, a data-type can be converted into a communication object and vice versa, as shown in the following dialog.
 
-<center>
-[[Image:Papyrus-customizations-robotics-ToggleCommunicationObject.png]]<br/>
+[[Image:figs/ToggleCommunicationObject.png]]<br/>
 Toggle between data-type and communication object
-</center>
 
 
 
@@ -37,7 +35,7 @@ Toggle between data-type and communication object
 
 A set of component instances that are ''wired'' together via their ports. At this level, it is also possible to configure component instances.
 
-[[Image:Papyrus-robotics-palette-system.png]]
+[[Image:systemdes/figs/palette-system.png]]
 
 The palette shown above enables the user to declare new component instances (besides the possibility to declare comments and constraints). After an instance is added, use the property view to assign a component type.
 Once the type is assigned, parameter settings can be updated via the property view as well (provided that the component definition has assignable attributes).