diff options
Diffstat (limited to 'plugins/org.eclipse.etrice.doc/html/etrice-docse7.html')
| -rw-r--r-- | plugins/org.eclipse.etrice.doc/html/etrice-docse7.html | 62 |
1 files changed, 30 insertions, 32 deletions
diff --git a/plugins/org.eclipse.etrice.doc/html/etrice-docse7.html b/plugins/org.eclipse.etrice.doc/html/etrice-docse7.html index 23c1b6c91..b94e49ff6 100644 --- a/plugins/org.eclipse.etrice.doc/html/etrice-docse7.html +++ b/plugins/org.eclipse.etrice.doc/html/etrice-docse7.html @@ -10,7 +10,7 @@ <meta name="originator" content="TeX4ht (http://www.cse.ohio-state.edu/~gurari/TeX4ht/)" /> <!-- xhtml,3,next,html --> <meta name="src" content="etrice-doc.tex" /> -<meta name="date" content="2013-03-25 22:23:00" /> +<meta name="date" content="2013-03-26 21:41:00" /> <link rel="stylesheet" type="text/css" href="etrice-doc.css" /> </head><body > @@ -22,34 +22,34 @@ href="#tailetrice-docse7.html">tail</a>] [<a href="etrice-docch5.html#etrice-docse7.html" >up</a>] </p></div> <h3 class="sectionHead"><span class="titlemark">5.2 </span> <a id="x14-280005.2"></a>Create a new model from scratch</h3> -<!--l. 19--><p class="noindent" >The easiest way to create a new eTrice Project is to use the eclipse project wizard. -From the eclipse file menu select <span -class="ecbx-1000">File->New->Project </span>and create a new eTrice -project and name it <span +<!--l. 19--><p class="noindent" >The easiest way to create a new eTrice Project is to use the eclipse project wizard. From the +eclipse file menu select <span +class="ecbx-1000">File->New->Project </span>and create a new eTrice project and name it +<span class="ecbx-1000">HelloWorld</span>. </p><!--l. 21--><p class="noindent" ><img src="images/015-HelloWorld10.png" alt="PIC" /> -</p><!--l. 24--><p class="noindent" >The wizard creates everything that is needed to create, build and run an eTrice -model. The resulting project should look like this: +</p><!--l. 24--><p class="noindent" >The wizard creates everything that is needed to create, build and run an eTrice model. The resulting +project should look like this: </p><!--l. 26--><p class="noindent" ><img src="images/015-HelloWorld11.png" alt="PIC" /> </p><!--l. 29--><p class="noindent" >Within the model directory the model file <span -class="ecti-1000">HelloWorld.room </span>was created. Open the +class="ecti-1000">HelloWorld.room </span>was created. Open the <span +class="ecti-1000">HelloWorld.room </span>file +and delete the contents of the file. Open the content assist with Ctrl+Space and select <span +class="ecti-1000">model</span> <span -class="ecti-1000">HelloWorld.room </span>file and delete the contents of the file. Open the content assist with -Ctrl+Space and select <span -class="ecti-1000">model skeleton</span>. +class="ecti-1000">skeleton</span>. </p><!--l. 31--><p class="noindent" ><img src="images/015-HelloWorld12.png" alt="PIC" /> -</p><!--l. 34--><p class="noindent" >Edit the template variables by typing the new names and jumping with Tab from -name to name. +</p><!--l. 34--><p class="noindent" >Edit the template variables by typing the new names and jumping with Tab from name to +name. </p><!--l. 36--><p class="noindent" >The resulting model code should look like this: - - - + + </p> <div class="verbatim" id="verbatim-1"> RoomModel HelloWorld { @@ -67,9 +67,9 @@ RoomModel HelloWorld {  <br />} </div> <!--l. 52--><p class="nopar" > -</p><!--l. 54--><p class="noindent" >The goal of eTrice is to describe distributed systems on a logical level. In the current -version not all elements will be used. But as prerequisite for further versions the -following elements can be defined: </p> +</p><!--l. 54--><p class="noindent" >The goal of eTrice is to describe distributed systems on a logical level. In the current version not all +elements will be used. But as prerequisite for further versions the following elements can be defined: +</p> <ul class="itemize1"> <li class="itemize">the <span class="ecti-1000">LogicalSystem </span>(currently optional) @@ -80,23 +80,21 @@ class="ecti-1000">SubSystemClass </span>(mandatory) <li class="itemize">at least one <span class="ecti-1000">ActorClass </span>(mandatory)</li></ul> <!--l. 61--><p class="noindent" >The <span -class="ecti-1000">LogicalSystem </span>represents the complete distributed system and contains at least -one <span -class="ecti-1000">SubSystemRef</span>. The <span -class="ecti-1000">SubSystemClass </span>represents an address space and contains at -least one <span +class="ecti-1000">LogicalSystem </span>represents the complete distributed system and contains at least one <span +class="ecti-1000">SubSystemRef</span>. +The <span +class="ecti-1000">SubSystemClass </span>represents an address space and contains at least one <span class="ecti-1000">ActorRef</span>. The <span -class="ecti-1000">ActorClass </span>is the building block of which an application will -be built of. It is in general a good idea to define a top level actor that can be used as -reference within the subsystem. -</p><!--l. 63--><p class="noindent" >The outline view of the textual ROOM editor shows the main modeling elements in -an easy to navigate tree. +class="ecti-1000">ActorClass </span>is +the building block of which an application will be built of. It is in general a good idea to define a top level +actor that can be used as reference within the subsystem. +</p><!--l. 63--><p class="noindent" >The outline view of the textual ROOM editor shows the main modeling elements in an easy to navigate +tree. </p><!--l. 65--><p class="noindent" ><img src="images/015-HelloWorld02.png" alt="PIC" /> - - - + + </p> <!--l. 69--><div class="crosslinks"><p class="noindent">[<a href="etrice-docse8.html" >next</a>] [<a |