|
|
|
**Framework Basics**
|
|
|
|
|
|
|
|
The TULIP framework is a collection of customizable building blocks, mapping the physical objects on the table to a virtual representation on the screen (See Figure 3). Each physical object, identified by its marker, is mapped to a dedicated software representation, called a Widget. Widgets define the functional behaviour of the object. Each widget has one or more associated Coronas, defining the visual representation of the object on the table. The mapping of markers to widgets and subsequently of coronas to widgets is defined in an external XML file called a Scenario. The scenario file encapsulates all design related aspects of the application to build, i.e. graphical and functional attributes of coronas, configuration of data sources, chaining of data processing steps.
|
|
|
|
The TULIP framework is a collection of customizable building blocks, mapping the physical objects on the table to a virtual representation on the screen.
|
|
|
|
|
|
|
|
<div align="center">
|
|
|
|
<img src="uploads/7356be7098cbb38173798ab15aff6368/WidgetsAndCoronas.png" width="480" height="332">
|
|
|
|
</div> |
|
|
\ No newline at end of file |
|
|
|
</div>
|
|
|
|
|
|
|
|
Each physical object, identified by its marker, is mapped to a dedicated software representation, called a Widget. Widgets define the functional behaviour of the object. Each widget has one or more associated Coronas, defining the visual representation of the object on the table. The mapping of markers to widgets and subsequently of coronas to widgets is defined in an external XML file called a Scenario. The scenario file encapsulates all design related aspects of the application to build, i.e. graphical and functional attributes of coronas, configuration of data sources, chaining of data processing steps. |
