3 ms·

> so you would group controller and view into the view and have a simple overall model-view separation. > ... > But operations on the data are just as much pa

> so you would group controller and view into the view and have a simple overall model-view separation. > ... > But operations on the data are just as much part of the model as the data itself. So you want to move controller into the view or to the model? I can't tell. :)

deleted 8y ago
[deleted]
quietbritishjim 8y ago
Sorry if that wasn't clear. I understand the term "model" to include non-graphical operations on model data. For example, SaveToFile() or InsertTextAtPosition() methods. These should definitely NOT be merged with the view! --> I believe that the linked article called these non-graphical operations "controllers", but I disagree. ---------------- I understand the term "controller" to be graphical controls that allow manipulation of the data. For example, a the QMenuItem "save" along with its associated signal (which of course will just call a method on the model), or the OnKeyPress handler on an edit control. --> I believe that the linked article just considers these to be part of the "view". I'm actually OK with this, because I the distinction between controller (in this sense) and view is not very useful.