Skip to main content
aboutsummaryrefslogtreecommitdiffstats
path: root/plugins/org.eclipse.etrice.doc/html/etrice-docse51.html
diff options
context:
space:
mode:
Diffstat (limited to 'plugins/org.eclipse.etrice.doc/html/etrice-docse51.html')
-rw-r--r--plugins/org.eclipse.etrice.doc/html/etrice-docse51.html520
1 files changed, 260 insertions, 260 deletions
diff --git a/plugins/org.eclipse.etrice.doc/html/etrice-docse51.html b/plugins/org.eclipse.etrice.doc/html/etrice-docse51.html
index 1fa4899f5..2f28d556c 100644
--- a/plugins/org.eclipse.etrice.doc/html/etrice-docse51.html
+++ b/plugins/org.eclipse.etrice.doc/html/etrice-docse51.html
@@ -1,266 +1,266 @@
-<?xml version="1.0" encoding="iso-8859-1" ?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!--http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd-->
-<html xmlns="http://www.w3.org/1999/xhtml"
->
-<head><title>Layering</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<meta name="generator" content="TeX4ht (http://www.cse.ohio-state.edu/~gurari/TeX4ht/)" />
-<meta name="originator" content="TeX4ht (http://www.cse.ohio-state.edu/~gurari/TeX4ht/)" />
-<!-- xhtml,3,next,html -->
-<meta name="src" content="etrice-doc.tex" />
+<?xml version="1.0" encoding="iso-8859-1" ?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!--http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd-->
+<html xmlns="http://www.w3.org/1999/xhtml"
+>
+<head><title>Layering</title>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+<meta name="generator" content="TeX4ht (http://www.cse.ohio-state.edu/~gurari/TeX4ht/)" />
+<meta name="originator" content="TeX4ht (http://www.cse.ohio-state.edu/~gurari/TeX4ht/)" />
+<!-- xhtml,3,next,html -->
+<meta name="src" content="etrice-doc.tex" />
<<<<<<< Upstream, based on branch 'master' of ssh://hrentzreich@git.eclipse.org:29418/etrice/org.eclipse.etrice.git
-<meta name="date" content="2013-06-14 00:07:00" />
+<meta name="date" content="2013-06-14 00:07:00" />
=======
-<meta name="date" content="2013-06-14 08:45:00" />
+<meta name="date" content="2013-06-14 08:45:00" />
>>>>>>> 1fbdb27 [doc] fixed problem with colored eTrice in headings
-<link rel="stylesheet" type="text/css" href="etrice-doc.css" />
-</head><body
->
-<!--l. 247--><div class="crosslinks"><p class="noindent">[<a
-href="etrice-docse52.html" >next</a>] [<a
-href="etrice-docse50.html" >prev</a>] [<a
-href="etrice-docse50.html#tailetrice-docse50.html" >prev-tail</a>] [<a
-href="#tailetrice-docse51.html">tail</a>] [<a
-href="etrice-docch10.html#etrice-docse51.html" >up</a>] </p></div>
-<h3 class="sectionHead"><span class="titlemark">10.5 </span> <a
- id="x63-10200010.5"></a>Layering</h3>
-<!--l. 249--><p class="noindent" >
-</p>
-<h4 class="subsectionHead"><span class="titlemark">10.5.1 </span> <a
- id="x63-10300010.5.1"></a>Description</h4>
-<!--l. 251--><p class="noindent" >In addition to the actor containment hierarchies, layering provides another method to hierarchically structure a
-software system. Layering and actor hierarchies with port to port connections can be mixed on every level of
-granularity.
-</p><!--l. 255--><p class="noindent" >
- </p><ol class="enumerate1" >
- <li
- class="enumerate" id="x63-103002x1">an actor class can define a Service Provision Point (<span id="textcolor49"><span
-class="ec-lmssbx-10">SPPRef</span></span>) to publish a specific service, defined
- by a protocol class
- </li>
- <li
- class="enumerate" id="x63-103004x2">an actor class can define a Service Access Point (<span id="textcolor50"><span
-class="ec-lmssbx-10">SAPRef</span></span>) if it needs a service, defined by a
- protocol class
- </li>
- <li
- class="enumerate" id="x63-103006x3">for a given actor hierarchy, a <span id="textcolor51"><span
-class="ec-lmssbx-10">LayerConnection</span></span> defines which SAP will be satisfied by (connected
- to) which SPP</li></ol>
-<!--l. 264--><p class="noindent" >
-</p>
-<h4 class="subsectionHead"><span class="titlemark">10.5.2 </span> <a
- id="x63-10400010.5.2"></a>Notation</h4>
-<!--l. 266--><p class="noindent" >For the graphical and textual notation refer to table <a
-href="#x63-1040016">10.6<!--tex4ht:ref: tab:layering_notation --></a>
-</p>
-<div class="table">
-
-
-<!--l. 269--><p class="noindent" ><a
- id="x63-1040016"></a></p><hr class="float" /><div class="float"
->
-
-
- <div class="caption"
-><span class="id">Table&#x00A0;10.6: </span><span
-class="content">Layering Notation</span></div><!--tex4ht:label?: x63-1040016 -->
-<div class="tabular"> <table id="TBL-11" class="tabular"
-cellspacing="0" cellpadding="0" rules="groups"
-><colgroup id="TBL-11-1g"><col
-id="TBL-11-1" /></colgroup><colgroup id="TBL-11-2g"><col
-id="TBL-11-2" /></colgroup><colgroup id="TBL-11-3g"><col
-id="TBL-11-3" /></colgroup><tr
-class="hline"><td><hr /></td><td><hr /></td><td><hr /></td></tr><tr
- style="vertical-align:baseline;" id="TBL-11-1-"><td style="white-space:nowrap; text-align:left; vertical-align:middle;" id="TBL-11-1-1"
-class="td11"> <!--l. 273--><p class="noindent" ><span
-class="ec-lmssbx-10">Description</span> </p></td><td style="white-space:nowrap; text-align:center;" id="TBL-11-1-2"
-class="td11"> <span
-class="ec-lmssbx-10">Graphical Notation </span></td><td style="white-space:nowrap; text-align:left;" id="TBL-11-1-3"
-class="td11"> <span
-class="ec-lmssbx-10">Textual Notation </span></td>
-</tr><tr
-class="hline"><td><hr /></td><td><hr /></td><td><hr /></td></tr><tr
- style="vertical-align:baseline;" id="TBL-11-2-"><td style="white-space:nowrap; text-align:left; vertical-align:middle;" id="TBL-11-2-1"
-class="td11">
- <div class="flushleft"
->
- <!--l. 275--><p class="noindent" >
- The layer
- connections in this
- model define which
- services are provided
- by the <span
-class="ec-lmsso-10">ServiceLayer</span>
- (<span
-class="ec-lmsso-10">digitalIO </span>and
- <span
-class="ec-lmsso-10">timer</span>)</p></div>
- <!--l. 278--><p class="noindent" > </p></td><td style="white-space:nowrap; text-align:center;" id="TBL-11-2-2"
-class="td11"> <img
-src="images/040-LayeringModel.png" alt="PIC"
- /> </td><td style="white-space:nowrap; text-align:left;" id="TBL-11-2-3"
-class="td11"> <img
-src="images/040-LayeringModelTextual.png" alt="PIC"
- /> </td>
-</tr><tr
-class="hline"><td><hr /></td><td><hr /></td><td><hr /></td></tr><tr
- style="vertical-align:baseline;" id="TBL-11-3-"><td style="white-space:nowrap; text-align:left; vertical-align:middle;" id="TBL-11-3-1"
-class="td11">
- <div class="flushleft"
->
- <!--l. 283--><p class="noindent" >
- The
- implementation of
- the services (SPPs)
- can be delegated to
- sub actors. In this
- case the actor
- <span
-class="ec-lmsso-10">ServiceLayer </span>relays
- (delegates) the
- implementation
- services <span
-class="ec-lmsso-10">digitalIO</span>
- and <span
-class="ec-lmsso-10">timer </span>to sub
- actors</p></div>
- <!--l. 287--><p class="noindent" > </p></td><td style="white-space:nowrap; text-align:center;" id="TBL-11-3-2"
-class="td11"> <img
-src="images/040-LayeringServiceLayer.png" alt="PIC"
- /> </td><td style="white-space:nowrap; text-align:left;" id="TBL-11-3-3"
-class="td11"> <img
-src="images/040-LayeringServiceLayerTextual.png" alt="PIC"
- /> </td>
-</tr><tr
-class="hline"><td><hr /></td><td><hr /></td><td><hr /></td></tr><tr
- style="vertical-align:baseline;" id="TBL-11-4-"><td style="white-space:nowrap; text-align:left; vertical-align:middle;" id="TBL-11-4-1"
-class="td11">
- <div class="flushleft"
->
- <!--l. 291--><p class="noindent" >
- Every Actor inside
- the
- <span
-class="ec-lmsso-10">ApplicationLayer</span>
- that contains an
- SAP with the same
- protocol as <span
-class="ec-lmsso-10">timer </span>or
- <span
-class="ec-lmsso-10">digitalIO </span>will be
- connected to the
- specified SPP</p></div>
- <!--l. 294--><p class="noindent" > </p></td><td style="white-space:nowrap; text-align:center;" id="TBL-11-4-2"
-class="td11"> <img
-src="images/040-LayeringApplicationLayer.png" alt="PIC"
- /> </td><td style="white-space:nowrap; text-align:left;" id="TBL-11-4-3"
-class="td11"> <img
-src="images/040-LayeringApplicationLayerTextual.png" alt="PIC"
- /> </td>
-</tr><tr
-class="hline"><td><hr /></td><td><hr /></td><td><hr /></td></tr><tr
- style="vertical-align:baseline;" id="TBL-11-5-"><td style="white-space:nowrap; text-align:left; vertical-align:middle;" id="TBL-11-5-1"
-class="td11"> </td></tr></table></div>
-
-
-</div><hr class="endfloat" />
-</div>
-
-
+<link rel="stylesheet" type="text/css" href="etrice-doc.css" />
+</head><body
+>
+<!--l. 247--><div class="crosslinks"><p class="noindent">[<a
+href="etrice-docse52.html" >next</a>] [<a
+href="etrice-docse50.html" >prev</a>] [<a
+href="etrice-docse50.html#tailetrice-docse50.html" >prev-tail</a>] [<a
+href="#tailetrice-docse51.html">tail</a>] [<a
+href="etrice-docch10.html#etrice-docse51.html" >up</a>] </p></div>
+<h3 class="sectionHead"><span class="titlemark">10.5 </span> <a
+ id="x63-10200010.5"></a>Layering</h3>
+<!--l. 249--><p class="noindent" >
+</p>
+<h4 class="subsectionHead"><span class="titlemark">10.5.1 </span> <a
+ id="x63-10300010.5.1"></a>Description</h4>
+<!--l. 251--><p class="noindent" >In addition to the actor containment hierarchies, layering provides another method to hierarchically structure a
+software system. Layering and actor hierarchies with port to port connections can be mixed on every level of
+granularity.
+</p><!--l. 255--><p class="noindent" >
+ </p><ol class="enumerate1" >
+ <li
+ class="enumerate" id="x63-103002x1">an actor class can define a Service Provision Point (<span id="textcolor49"><span
+class="ec-lmssbx-10">SPPRef</span></span>) to publish a specific service, defined
+ by a protocol class
+ </li>
+ <li
+ class="enumerate" id="x63-103004x2">an actor class can define a Service Access Point (<span id="textcolor50"><span
+class="ec-lmssbx-10">SAPRef</span></span>) if it needs a service, defined by a
+ protocol class
+ </li>
+ <li
+ class="enumerate" id="x63-103006x3">for a given actor hierarchy, a <span id="textcolor51"><span
+class="ec-lmssbx-10">LayerConnection</span></span> defines which SAP will be satisfied by (connected
+ to) which SPP</li></ol>
+<!--l. 264--><p class="noindent" >
+</p>
+<h4 class="subsectionHead"><span class="titlemark">10.5.2 </span> <a
+ id="x63-10400010.5.2"></a>Notation</h4>
+<!--l. 266--><p class="noindent" >For the graphical and textual notation refer to table <a
+href="#x63-1040016">10.6<!--tex4ht:ref: tab:layering_notation --></a>
+</p>
+<div class="table">
+
+
+<!--l. 269--><p class="noindent" ><a
+ id="x63-1040016"></a></p><hr class="float" /><div class="float"
+>
+
+
+ <div class="caption"
+><span class="id">Table&#x00A0;10.6: </span><span
+class="content">Layering Notation</span></div><!--tex4ht:label?: x63-1040016 -->
+<div class="tabular"> <table id="TBL-11" class="tabular"
+cellspacing="0" cellpadding="0" rules="groups"
+><colgroup id="TBL-11-1g"><col
+id="TBL-11-1" /></colgroup><colgroup id="TBL-11-2g"><col
+id="TBL-11-2" /></colgroup><colgroup id="TBL-11-3g"><col
+id="TBL-11-3" /></colgroup><tr
+class="hline"><td><hr /></td><td><hr /></td><td><hr /></td></tr><tr
+ style="vertical-align:baseline;" id="TBL-11-1-"><td style="white-space:nowrap; text-align:left; vertical-align:middle;" id="TBL-11-1-1"
+class="td11"> <!--l. 273--><p class="noindent" ><span
+class="ec-lmssbx-10">Description</span> </p></td><td style="white-space:nowrap; text-align:center;" id="TBL-11-1-2"
+class="td11"> <span
+class="ec-lmssbx-10">Graphical Notation </span></td><td style="white-space:nowrap; text-align:left;" id="TBL-11-1-3"
+class="td11"> <span
+class="ec-lmssbx-10">Textual Notation </span></td>
+</tr><tr
+class="hline"><td><hr /></td><td><hr /></td><td><hr /></td></tr><tr
+ style="vertical-align:baseline;" id="TBL-11-2-"><td style="white-space:nowrap; text-align:left; vertical-align:middle;" id="TBL-11-2-1"
+class="td11">
+ <div class="flushleft"
+>
+ <!--l. 275--><p class="noindent" >
+ The layer
+ connections in this
+ model define which
+ services are provided
+ by the <span
+class="ec-lmsso-10">ServiceLayer</span>
+ (<span
+class="ec-lmsso-10">digitalIO </span>and
+ <span
+class="ec-lmsso-10">timer</span>)</p></div>
+ <!--l. 278--><p class="noindent" > </p></td><td style="white-space:nowrap; text-align:center;" id="TBL-11-2-2"
+class="td11"> <img
+src="images/040-LayeringModel.png" alt="PIC"
+ /> </td><td style="white-space:nowrap; text-align:left;" id="TBL-11-2-3"
+class="td11"> <img
+src="images/040-LayeringModelTextual.png" alt="PIC"
+ /> </td>
+</tr><tr
+class="hline"><td><hr /></td><td><hr /></td><td><hr /></td></tr><tr
+ style="vertical-align:baseline;" id="TBL-11-3-"><td style="white-space:nowrap; text-align:left; vertical-align:middle;" id="TBL-11-3-1"
+class="td11">
+ <div class="flushleft"
+>
+ <!--l. 283--><p class="noindent" >
+ The
+ implementation of
+ the services (SPPs)
+ can be delegated to
+ sub actors. In this
+ case the actor
+ <span
+class="ec-lmsso-10">ServiceLayer </span>relays
+ (delegates) the
+ implementation
+ services <span
+class="ec-lmsso-10">digitalIO</span>
+ and <span
+class="ec-lmsso-10">timer </span>to sub
+ actors</p></div>
+ <!--l. 287--><p class="noindent" > </p></td><td style="white-space:nowrap; text-align:center;" id="TBL-11-3-2"
+class="td11"> <img
+src="images/040-LayeringServiceLayer.png" alt="PIC"
+ /> </td><td style="white-space:nowrap; text-align:left;" id="TBL-11-3-3"
+class="td11"> <img
+src="images/040-LayeringServiceLayerTextual.png" alt="PIC"
+ /> </td>
+</tr><tr
+class="hline"><td><hr /></td><td><hr /></td><td><hr /></td></tr><tr
+ style="vertical-align:baseline;" id="TBL-11-4-"><td style="white-space:nowrap; text-align:left; vertical-align:middle;" id="TBL-11-4-1"
+class="td11">
+ <div class="flushleft"
+>
+ <!--l. 291--><p class="noindent" >
+ Every Actor inside
+ the
+ <span
+class="ec-lmsso-10">ApplicationLayer</span>
+ that contains an
+ SAP with the same
+ protocol as <span
+class="ec-lmsso-10">timer </span>or
+ <span
+class="ec-lmsso-10">digitalIO </span>will be
+ connected to the
+ specified SPP</p></div>
+ <!--l. 294--><p class="noindent" > </p></td><td style="white-space:nowrap; text-align:center;" id="TBL-11-4-2"
+class="td11"> <img
+src="images/040-LayeringApplicationLayer.png" alt="PIC"
+ /> </td><td style="white-space:nowrap; text-align:left;" id="TBL-11-4-3"
+class="td11"> <img
+src="images/040-LayeringApplicationLayerTextual.png" alt="PIC"
+ /> </td>
+</tr><tr
+class="hline"><td><hr /></td><td><hr /></td><td><hr /></td></tr><tr
+ style="vertical-align:baseline;" id="TBL-11-5-"><td style="white-space:nowrap; text-align:left; vertical-align:middle;" id="TBL-11-5-1"
+class="td11"> </td></tr></table></div>
+
+
+</div><hr class="endfloat" />
+</div>
+
+
<<<<<<< Upstream, based on branch 'master' of ssh://hrentzreich@git.eclipse.org:29418/etrice/org.eclipse.etrice.git
-<!--l. 301--><div class="crosslinks"><p class="noindent">[<a
+<!--l. 301--><div class="crosslinks"><p class="noindent">[<a
=======
-
-<!--l. 185--><p class="noindent" ><img
-src="images/043-PreferencePage.png" alt="PIC"
- />
-<br /> </p><div class="caption"
-><span class="id">Figure&#x00A0;13.4: </span><span
-class="content">Layout preference page</span></div><!--tex4ht:label?: x66-1200014 -->
-
-
-</div><hr class="endfigure" />
-<!--l. 190--><p class="noindent" >Note that the <span
-class="ec-lmsso-10">Behavior </span>preference page will show only those entries which hold for the behavior diagrams.
-Moreover, it will allow setting default values of layout options for only those domain model elements and
-diagram types which could be present in the behavior editor diagrams. Similar thing holds for the <span
-class="ec-lmsso-10">Structure</span>
-preference page.
-</p>
-<h4 class="subsectionHead"><span class="titlemark">13.1.5 </span> <a
- id="x66-12100013.1.5"></a>Special Layout Options</h4>
-<!--l. 198--><p class="noindent" >While most layout options are used to affect how the active layout algorithm computes concrete coordinates
-for the graph elements, there are some layout options that have a special role.
-</p><!--l. 201--><p class="noindent" >
-</p>
-<h5 class="subsubsectionHead"><a
- id="x66-12200013.1.5"></a>Layout Algorithm</h5>
-<!--l. 203--><p class="noindent" >The option with identifier de.cau.cs.kieler.algorithm specifies which layout algorithm to use for the
-content of a composite node. The value can be either the identifier of a layout algorithm or the
-identifier of a layout type. In the latter case the algorithm with highest priority of that type is
-applied.
-</p><!--l. 207--><p class="noindent" >For the purpose of automatic diagram layout in eTrice, we use the <span
-class="ec-lmsso-10">Layered </span>algorithms which are meant for
-lay-outing hierarchical diagrams and are best suited for behavior and structure diagrams in eTrice. For the
-behavior diagrams we have used the <span
-class="ec-lmsso-10">Graphviz Dot </span>algorithm whereas for the structure diagrams we have used
-the <span
-class="ec-lmsso-10">KLay Layered </span>algorithm. Though the layout algorithm being used for performing layout can be changed at
-ones own will, it is recommended to use the defaults.
-</p><!--l. 213--><p class="noindent" >
-</p>
-<h5 class="subsubsectionHead"><a
- id="x66-12300013.1.5"></a>Diagram Type</h5>
-<!--l. 215--><p class="noindent" >Diagram types are used to classify graphical diagrams for setting default layout option values for
-a set of similar diagrams. The diagram type of an element is specified with the layout option
-<span
-class="ec-lmtt-10">de.cau.cs.kieler.diagramType</span>. Thus, these help in
-</p><!--l. 219--><p class="noindent" >The following diagram types have been defined and used in eTrice: </p>
- <ul class="itemize1">
- <li class="itemize"><span
-class="ec-lmsso-10">General </span>- This type is automatically assigned to all diagrams for which no specific type is declared.
- (Predefined in KIELER)
- </li>
- <li class="itemize"><span
-class="ec-lmsso-10">e</span><span
-class="ec-lmsso-10">Trice</span> <span
-class="ec-lmsso-10">Behavior Diagrams </span>- This type has been assigned to the diagram objects in eTrice Behavior
- Diagrams.
- </li>
- <li class="itemize"><span
-class="ec-lmsso-10">e</span><span
-class="ec-lmsso-10">Trice</span> <span
-class="ec-lmsso-10">Structure Diagrams </span>- This type has been assigned to the diagram objects in eTrice Structure
- Diagrams.</li></ul>
-<!--l. 228--><p class="noindent" >Note that not all diagrams objects in the behavior and structure diagrams are assigned the last two diagram
-types. Only the top-level container and the visible bounding box has been assigned these diagram types in
-respective editors.
-
-
-</p><!--l. 232--><p class="noindent" >
-</p>
-<h4 class="subsectionHead"><span class="titlemark">13.1.6 </span> <a
- id="x66-12400013.1.6"></a>Further References</h4>
-<!--l. 234--><p class="noindent" >Most parts of the above documentation have been taken from the "KIML wiki"
-(<a
-href="http://rtsys.informatik.uni-kiel.de/confluence/pages/viewpage.action?pageId=328078" class="url" ><span
-class="ec-lmtt-10">http://rtsys.informatik.uni-kiel.de/confluence/pages/viewpage.action?pageId=328078</span></a> and
-have been modified for automatic layout in eTrice. A more detailed description about the layout algorithms,
-predefined diagram types and the internal structure of KIELER Infrastructure for Meta-Layout (KIML) can be
-found there.
-
-
-</p>
-<!--l. 1--><div class="crosslinks"><p class="noindent">[<a
+
+<!--l. 185--><p class="noindent" ><img
+src="images/043-PreferencePage.png" alt="PIC"
+ />
+<br /> </p><div class="caption"
+><span class="id">Figure&#x00A0;13.4: </span><span
+class="content">Layout preference page</span></div><!--tex4ht:label?: x66-1200014 -->
+
+
+</div><hr class="endfigure" />
+<!--l. 190--><p class="noindent" >Note that the <span
+class="ec-lmsso-10">Behavior </span>preference page will show only those entries which hold for the behavior diagrams.
+Moreover, it will allow setting default values of layout options for only those domain model elements and
+diagram types which could be present in the behavior editor diagrams. Similar thing holds for the <span
+class="ec-lmsso-10">Structure</span>
+preference page.
+</p>
+<h4 class="subsectionHead"><span class="titlemark">13.1.5 </span> <a
+ id="x66-12100013.1.5"></a>Special Layout Options</h4>
+<!--l. 198--><p class="noindent" >While most layout options are used to affect how the active layout algorithm computes concrete coordinates
+for the graph elements, there are some layout options that have a special role.
+</p><!--l. 201--><p class="noindent" >
+</p>
+<h5 class="subsubsectionHead"><a
+ id="x66-12200013.1.5"></a>Layout Algorithm</h5>
+<!--l. 203--><p class="noindent" >The option with identifier de.cau.cs.kieler.algorithm specifies which layout algorithm to use for the
+content of a composite node. The value can be either the identifier of a layout algorithm or the
+identifier of a layout type. In the latter case the algorithm with highest priority of that type is
+applied.
+</p><!--l. 207--><p class="noindent" >For the purpose of automatic diagram layout in eTrice, we use the <span
+class="ec-lmsso-10">Layered </span>algorithms which are meant for
+lay-outing hierarchical diagrams and are best suited for behavior and structure diagrams in eTrice. For the
+behavior diagrams we have used the <span
+class="ec-lmsso-10">Graphviz Dot </span>algorithm whereas for the structure diagrams we have used
+the <span
+class="ec-lmsso-10">KLay Layered </span>algorithm. Though the layout algorithm being used for performing layout can be changed at
+ones own will, it is recommended to use the defaults.
+</p><!--l. 213--><p class="noindent" >
+</p>
+<h5 class="subsubsectionHead"><a
+ id="x66-12300013.1.5"></a>Diagram Type</h5>
+<!--l. 215--><p class="noindent" >Diagram types are used to classify graphical diagrams for setting default layout option values for
+a set of similar diagrams. The diagram type of an element is specified with the layout option
+<span
+class="ec-lmtt-10">de.cau.cs.kieler.diagramType</span>. Thus, these help in
+</p><!--l. 219--><p class="noindent" >The following diagram types have been defined and used in eTrice: </p>
+ <ul class="itemize1">
+ <li class="itemize"><span
+class="ec-lmsso-10">General </span>- This type is automatically assigned to all diagrams for which no specific type is declared.
+ (Predefined in KIELER)
+ </li>
+ <li class="itemize"><span
+class="ec-lmsso-10">e</span><span
+class="ec-lmsso-10">Trice</span> <span
+class="ec-lmsso-10">Behavior Diagrams </span>- This type has been assigned to the diagram objects in eTrice Behavior
+ Diagrams.
+ </li>
+ <li class="itemize"><span
+class="ec-lmsso-10">e</span><span
+class="ec-lmsso-10">Trice</span> <span
+class="ec-lmsso-10">Structure Diagrams </span>- This type has been assigned to the diagram objects in eTrice Structure
+ Diagrams.</li></ul>
+<!--l. 228--><p class="noindent" >Note that not all diagrams objects in the behavior and structure diagrams are assigned the last two diagram
+types. Only the top-level container and the visible bounding box has been assigned these diagram types in
+respective editors.
+
+
+</p><!--l. 232--><p class="noindent" >
+</p>
+<h4 class="subsectionHead"><span class="titlemark">13.1.6 </span> <a
+ id="x66-12400013.1.6"></a>Further References</h4>
+<!--l. 234--><p class="noindent" >Most parts of the above documentation have been taken from the "KIML wiki"
+(<a
+href="http://rtsys.informatik.uni-kiel.de/confluence/pages/viewpage.action?pageId=328078" class="url" ><span
+class="ec-lmtt-10">http://rtsys.informatik.uni-kiel.de/confluence/pages/viewpage.action?pageId=328078</span></a> and
+have been modified for automatic layout in eTrice. A more detailed description about the layout algorithms,
+predefined diagram types and the internal structure of KIELER Infrastructure for Meta-Layout (KIML) can be
+found there.
+
+
+</p>
+<!--l. 1--><div class="crosslinks"><p class="noindent">[<a
>>>>>>> 1fbdb27 [doc] fixed problem with colored eTrice in headings
-href="etrice-docse52.html" >next</a>] [<a
-href="etrice-docse50.html" >prev</a>] [<a
-href="etrice-docse50.html#tailetrice-docse50.html" >prev-tail</a>] [<a
-href="etrice-docse51.html" >front</a>] [<a
-href="etrice-docch10.html#etrice-docse51.html" >up</a>] </p></div>
-<!--l. 301--><p class="noindent" ><a
- id="tailetrice-docse51.html"></a> </p>
-</body></html>
+href="etrice-docse52.html" >next</a>] [<a
+href="etrice-docse50.html" >prev</a>] [<a
+href="etrice-docse50.html#tailetrice-docse50.html" >prev-tail</a>] [<a
+href="etrice-docse51.html" >front</a>] [<a
+href="etrice-docch10.html#etrice-docse51.html" >up</a>] </p></div>
+<!--l. 301--><p class="noindent" ><a
+ id="tailetrice-docse51.html"></a> </p>
+</body></html>

Back to the top