I recently completed a personal project, and one of the methods that I used to break the interface was to have one main model view controller that handled most of the main application logic. Then, for the most part, there were a lot of common controls that let you use the Slider and text box that were associated with the same float value. They themselves will constitute another (Model View Controller), with which the parent controller of the model view interacts. Although communication would still be down the hill, never looping on a loop.
So, in the general case, the controller will interact with the Slider controller and textField, which were connected together. But both of them did not have direct access to each other, therefore, when the event occurred for the Text field controller and slider, it will be processed by the parent controller, which will process most of the program logical flow, and then to the slider controller and text field.
It did a great job and received a lot of great feedback from users who used the app and loved the flexibility that it brought with the help of very logical corrective controls that they didn't need to think about.
Although the developer in me asks a question about pragmatism and clean design. System design was a city approach that I took from this publication in Adobe:
Adobe General Algorithms
http://www.youtube.com/watch?v=4moyKUHApq4
and, as a rule, using MVC as objects inside objects reflected this instead of a single global MVC controller.
And suggestions that I could improve in the next project, or should I use the same approach again?
source
share