Difference between revisions of "Sceneflows"
(Created page with "IRIS Wiki - Computational Models - '''{{PAGENAME}}''' === Background === === Description === ==== Intuitive representation ==== ==== Formal description ==== === Exam...") |
|||
| Line 3: | Line 3: | ||
=== Description === | === Description === | ||
| + | A sceneflow is a ''hierarchical'' and concurrent statechart | ||
| + | that consists of dierent types of nodes and edges. A sce- | ||
| + | nenode can be linked to one or more scenegroup playbackor | ||
| + | system commands and can be annotated with statements | ||
| + | and expressions from a simple scripting language, such as | ||
| + | type- and variable de�nitions as well as variable assignments | ||
| + | and function calls to prede�ned functions of the underlying | ||
| + | implementation language (Fig. 2 | ||
| + | 1 ). A supernode extends | ||
| + | the functionality of scenenodes by creating a hierarchical | ||
| + | structure. A supernode may contain scenenodes and supernodes | ||
| + | that constitute its subautomata. One of these subnodes | ||
| + | has to be declared the startnode of that supernode (Fig. 2 | ||
| − | + | 2 ). The supernode hierarchy can be used for type- and variable | |
| − | + | scoping. Type de�nitions and variable de�nitions are | |
| − | + | inherited to all subnodes of a supernode. The supernode | |
| + | hierarchy and the variable scoping mechanism imply a hierarchy | ||
| + | of local contexts that can be used for context-sensitive | ||
| + | reaction to user interactions, external events or the change | ||
| + | of environmental conditions. | ||
=== Examples === | === Examples === | ||
Revision as of 13:54, 20 December 2011
IRIS Wiki - Computational Models - Sceneflows
Contents
Background
Description
A sceneflow is a hierarchical and concurrent statechart that consists of dierent types of nodes and edges. A sce- nenode can be linked to one or more scenegroup playbackor system commands and can be annotated with statements and expressions from a simple scripting language, such as type- and variable de�nitions as well as variable assignments and function calls to prede�ned functions of the underlying implementation language (Fig. 2 1 ). A supernode extends the functionality of scenenodes by creating a hierarchical structure. A supernode may contain scenenodes and supernodes that constitute its subautomata. One of these subnodes has to be declared the startnode of that supernode (Fig. 2
2 ). The supernode hierarchy can be used for type- and variable scoping. Type de�nitions and variable de�nitions are inherited to all subnodes of a supernode. The supernode hierarchy and the variable scoping mechanism imply a hierarchy of local contexts that can be used for context-sensitive reaction to user interactions, external events or the change of environmental conditions.
