According to Wikipedia , a Model-view-controller (MVC) is an architectural pattern used in software engineering. In complex computer applications that present lots of data to the user, one often wishes to separate data (model) and user interface (view) concerns, so that changes to the user interface do not impact the data handling, and that the data can be reorganized without changing the user interface. The model-view-controller solves this problem by decoupling data access and business logic from data presentation and user interaction, by introducing an intermediate component: the controller.
For example, in the diagram above, the solid lines for the arrows starting from the controller and going to both the view and the model mean that the controller has a complete access to both the view and the model. The dashed line for the arrow going from the view to the controller means that the view has a limited access to the controller. The reasons of this design are :
- From View to Model : the model sends notification to the view when its data has been modified in order the view to redraw its content. The model doesnt need to know the inner workings of the view to perform this operation. However, the view needs to access the internal parts of the model.
- From View to Controller : the reason why the view has limited access to the controller is because the dependencies from the view to the controller need to be minimal: the controller can be replaced at any moment.
In Tiny ERP, we can apply this model-view-controller semantic with
- model : The PostgreSQL tables.
- view : views are defined in XML files in Tiny ERP.
- controller : The objects of TinyERP.