diff options
author | Thomas Jung | 2011-10-31 20:37:55 +0000 |
---|---|---|
committer | Thomas Jung | 2011-10-31 20:37:55 +0000 |
commit | 5f3f1c75c50b1edee895417603b66f10c7c46441 (patch) | |
tree | 7b0ad0fe39c865374083165eabc859eded6857dd | |
parent | 58edd9d51d0a306b9816c55ee7b4535dc6949e03 (diff) | |
download | org.eclipse.etrice-5f3f1c75c50b1edee895417603b66f10c7c46441.tar.gz org.eclipse.etrice-5f3f1c75c50b1edee895417603b66f10c7c46441.tar.xz org.eclipse.etrice-5f3f1c75c50b1edee895417603b66f10c7c46441.zip |
[doc.doc] Blinky updated
-rw-r--r-- | plugins/org.eclipse.etrice.doc/doc/010-room-introduction.textile | 9 | ||||
-rw-r--r-- | plugins/org.eclipse.etrice.doc/doc/images/020-Blinky151.png | bin | 0 -> 76075 bytes | |||
-rw-r--r-- | plugins/org.eclipse.etrice.doc/doc/images/020-Blinky16.png | bin | 0 -> 72982 bytes |
3 files changed, 6 insertions, 3 deletions
diff --git a/plugins/org.eclipse.etrice.doc/doc/010-room-introduction.textile b/plugins/org.eclipse.etrice.doc/doc/010-room-introduction.textile index 357551d44..6098dbdca 100644 --- a/plugins/org.eclipse.etrice.doc/doc/010-room-introduction.textile +++ b/plugins/org.eclipse.etrice.doc/doc/010-room-introduction.textile @@ -90,10 +90,13 @@ h3. Hierarchy in Structure and Behavior ROOM provides two types of hierarchy. Behavioral hierarchy and structural hierarchy. Structural hierarchy means that actors can be nested to arbitrary depth. Usually you will add more and more details to your application with each nesting level. That means you can focus yourself on any level of abstraction with always the same element, the actor. Structural hierarchy provides a powerful mechanism to divide your problem in smaller pieces, so that you can focus on the level of abstraction you want to work on.
-The actor's behavior will be described with a state machine. A state in turn may contain sub states. This is another possibility to focus on an abstraction level. Take the simple FSM from the blinky actor from the blinky tutorial:
-
+The actor's behavior will be described with a state machine. A state in turn may contain sub states. This is another possibility to focus on an abstraction level. Take the simple FSM from the blinky actor from the blinky tutorial.
+
+Top level:
!images\020-Blinky15.png!
-TODO: add a screenshot of the SubStateMachine
+
+??blinking?? Sub machine:
+!images\020-Blinky151.png!
From an abstract point of view there is a state "blinking". But a simple LED is not able to blink autonomously. Therefore you have to add more details to your model to make a LED blinking, but for the current work it is not of interest how the blinking is realized. This will be done in the next lower level of the hierarchy.
diff --git a/plugins/org.eclipse.etrice.doc/doc/images/020-Blinky151.png b/plugins/org.eclipse.etrice.doc/doc/images/020-Blinky151.png Binary files differnew file mode 100644 index 000000000..e45462427 --- /dev/null +++ b/plugins/org.eclipse.etrice.doc/doc/images/020-Blinky151.png diff --git a/plugins/org.eclipse.etrice.doc/doc/images/020-Blinky16.png b/plugins/org.eclipse.etrice.doc/doc/images/020-Blinky16.png Binary files differnew file mode 100644 index 000000000..911ec6517 --- /dev/null +++ b/plugins/org.eclipse.etrice.doc/doc/images/020-Blinky16.png |