2 ms·
The distinction you describe between view and controller should be relevant nowadays in the exact same way as it was on the 1970s. For example, the logic of in
by axilmar 8y ago
The distinction you describe between view and controller should be relevant nowadays in the exact same way as it was on the 1970s.
For example, the logic of inserting text when insertion mode is active, removing the selected text when the delete key is pressed etc is all part of the controller, not the view.
By splitting the view and the controller, a different view, for example a console one, or a remote one, can be done with the exact same editing capabilities, since they are to use the same controller.
- ensiferum 8y agoThe MVC pattern dates back to the time when people actually had to write code for the "view" part. These days most people don't write code for this anymore (except for games and other graphical apps) but use a toolkit. In this case the Qt provides the view so the code where the user writes the signal handlers to handle signals such as button presses etc. is the controller. The view part doesn't need to be done.