Augmented Reality Component SystemDifferences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
arcs.js:framework_presentation [2017/05/26 03:24] didier [Component model] |
arcs.js:framework_presentation [2017/05/26 04:14] didier |
||
|---|---|---|---|
| Line 15: | Line 15: | ||
| * using slot calls (see invocations below). | * using slot calls (see invocations below). | ||
| + | ==== Application model ==== | ||
| + | In ARCS.js, an application is considered to have a lifecycle going through several different states (initialisation, normal mode, recovery mode, etc). Each state is characterized by a set of omponents and a set of signal/slot connections. Such configuration is called a **sheet**. | ||
| + | The application is then controlled by a finite statemachine, each state of it corresponding to one sheet. When a transition is triggered in the statemachine, it activates a change of sheet. | ||
| + | |||
| + | The sheet is composite structure. It contains components as well as other data: | ||
| + | * a list of pre-connection invocations for component initialization; | ||
| + | * a list of connections to establish datapath between components; | ||
| + | * a list of post-connection invocations that enables dataflow; | ||
| + | * a list of cleanup invocations in order to set some components in a stable state. | ||