Possible Duplicate:
Understanding Model-View-Controller
If I was for example building a calculator application how would I go about splitting functionality so as to follow the MVC design pattern?
Am I right in thinking the following:
View -Contains all buttons and textfields
Model -Contains all operations (e.g. add subtract etc)
Controller Contains all the functions for handling operations and updating display based on user input Essentially the model acts as a library to the controller in this instance..
If anyone can explain better please do so, but I am struggling to fully grasp the concept..