Note. I do not mean any specific interpretation of the MVC structure
If, for example, I am developing an application for the rich Silverlight client, this is due to relatively complex user interface behavior, such as dragging rows between two GridViews filled with a dynamic user request, will this be a suitable template for use?
Some user interface behavior (for example, deleting a row in another valid row) will also lead to the application of business rules and the corresponding modification of the model. If MVC is not suitable for this type of application; what would be a good way to structure this?
EDIT: re-reading my original question, it seems a bit general; I will analyze it for a more directed question:
Is there an upper limit for detailing user interaction when an MVC pattern is not appropriate?
t. A user interface that will include a controller action that should handle something on mouse_move, mouse_button_up, etc.
source
share