Basics.md

 **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. 
-
+<br>
 <div align="center">
 <img src="uploads/7356be7098cbb38173798ab15aff6368/WidgetsAndCoronas.png"  width="640" height="443">
 </div>
-
-
+<br>
 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.
+<br>
+<div align="center">
 <img src="uploads/bbdd55d77728efda4a2869ee22d402bf/Tulip.png"  width="640" height="297">
-
-From a software architecture point of view, the TULIP framework consists of the open-source Tulip core package and a number of domain specific extensions. Each extension not only adds domain specific widgets and coronas, but also adds connectivity to external systems and environments (see Figure 4).
+</div>
+<br>
+From a software architecture point of view, the TULIP framework consists of the open-source Tulip core package and a number of domain specific extensions. Each extension not only adds domain specific widgets and coronas, but also adds connectivity to external systems and environments.
 
 ***Tulip-CPS***