Thursday, September 10, 2009

WorkShop 2

Convention over configuration means the developer only needs to specify unconventional aspects of the application. Assumptions are made of what the developer wants to do and how to do it. For example if there is a class 'sale' in the model, by default the corresponding table is called 'sale'. The Rails framework reduces the amount of tweaking and configuration, by the developer, that is needed to get things working.

I have learnt more about the Model-View-Controller (MVC) through the
http://wiki.squeak.org/squeak/1767. I have learnt that MVC is the pattern behind the traditional SmallTalk80 user interface and is one of the earliest and most successful design patterns. MVC was developed in 1979 by Tygve Reenskaug.

In MVC the user input, modelling of the external world and the visual feedback to the user are separated and handled by 3 types of object:
  • The view manages the graphical and/or textual output
  • The controller interprets the mouse and keyboard inputs from the user
  • And, the model manages the behaviour and data of the application domain, responds to requests for information about its state, and responds to instructions to change its current state.

References
  • http://wiki.squeak.org/squeak/1767
  • http://guides.rubyonrails.org/getting_started.html

No comments:

Post a Comment