Difference between revisions of "Sceneflows"
| Line 3: | Line 3: | ||
=== Description === | === Description === | ||
| − | A sceneflow is a ''hierarchical'' and concurrent statechart | + | A sceneflow is a ''hierarchical'' and ''concurrent statechart'' that consists of different types of nodes and edges. A ''scenenode'' can be linked to one or more scenegroup playback or system commands and can be annotated with statements and expressions from a simple scripting language, such as type- and variable definitions as well as variable assignments and function calls to predefined 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 definitions and variable definitions 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. |
| − | that consists of | ||
| − | |||
| − | system commands and can be annotated with statements | ||
| − | and expressions from a simple scripting language, such as | ||
| − | type- and variable | ||
| − | and function calls to | ||
| − | 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 | ||
| − | 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:56, 20 December 2011
IRIS Wiki - Computational Models - Sceneflows
Contents
Background
Description
A sceneflow is a hierarchical and concurrent statechart that consists of different types of nodes and edges. A scenenode can be linked to one or more scenegroup playback or system commands and can be annotated with statements and expressions from a simple scripting language, such as type- and variable definitions as well as variable assignments and function calls to predefined 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 definitions and variable definitions 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.
