Imagine an application where the user is allowed to create his/her own musical scales. The user selects notes from a list, arranges them to a group and presses a button to create the scale.
In an MVC structure, upon pressing the button, the View would tell the controller "the user wants to create a new scale, here are the names of the notes" (passing an array of strings).
These names need to be interpreted into the matching
Note objects, before they are composed into a new
The question is, should this interpretation happen in the Controller, before passing a
Notes array to the Model where the
Scale creation will take place? Or should the Controller just pass the array of strings (representing the names of the notes) along to the Model, where the Model will interpret the names to
Notes and compose the
Notes to a
What would be more conceptually correct, according to the idea of MVC?