3 ms·
I see the controller as an objects whose purpose is to shuttle data back and forth between the view and the model. The business rules should be in the model. th
by JustSomeNobody 10y ago
I see the controller as an objects whose purpose is to shuttle data back and forth between the view and the model. The business rules should be in the model. the controller can do some very minor formatting type things, handle events, etc. but no business rules.
Basically, the View is presentation, the Controller is interaction and the Model is logic and data.
- Fargren 10y agoYeah, in that case I agree with you. Under that definition M-VC just means to separate your business rules from your UI, which is always a wise move. I do think the interesting part that is missing is how you organize everything that isn't UI, but I guess that's a topic for another discusion.