Augmented Reality Component SystemDifferences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
arcs.js:framework_presentation [2017/05/26 04:17] didier |
arcs.js:framework_presentation [2017/05/26 04:34] didier |
||
|---|---|---|---|
| Line 24: | Line 24: | ||
| * a list of post-connection invocations that enables dataflow; | * a list of post-connection invocations that enables dataflow; | ||
| * a list of cleanup invocations in order to set some components in a stable state. | * a list of cleanup invocations in order to set some components in a stable state. | ||
| + | |||
| + | The behavior of the application controller is the following, assuming that it received a token triggering a transition (having a starting state and an ending state): | ||
| + | - If a sheet is active (corresponding to the starting state), disconnect all components; | ||
| + | - Perform cleanup invocations on sheet; | ||
| + | - Enable the next sheet (corresponding to the ending state): | ||
| + | - Perform pre-connection invocations; | ||
| + | - Connect components of the sheet; | ||
| + | - Perform post-connection invocations. | ||
| + | To complete the behavior, the controller, when the application starts, activates the first sheet or the one that is labelled as initial. An application is finished when the statemachine reaches an ending state. | ||
| + | |||
| + | |||