There are some things just left to the view. I agree with a lot of the other stuff here, but I think this one is one of those ones those principles that you shouldn't have second thoughts about if the view has very complex database requirements.
Normally you can circumvent this by calling multiple views, but often this is a mess and a performance hazard.
No instanciation of objects in the view is fine, but don't be too idealistic. You start making problems harder then they really are.
You know, I have a habit of putting controller code in the model. The MVC frameworks I've used have usually had the controller handing off to the model, which then calls the view.
MVC is not a framework, it's a pattern that the framework uses.
seppsters 11 months ago
There are some things just left to the view. I agree with a lot of the other stuff here, but I think this one is one of those ones those principles that you shouldn't have second thoughts about if the view has very complex database requirements.
Normally you can circumvent this by calling multiple views, but often this is a mess and a performance hazard.
No instanciation of objects in the view is fine, but don't be too idealistic. You start making problems harder then they really are.
yoshscout 2 years ago
*but I think this is one of those principles
yoshscout 2 years ago
oh i think that might be youtubes fault not sure...
just remove the ")" sign at the end of the url
ZerqTM 2 years ago
I quite hope the guys who made these videos realize the links to all 3 sites are broken in most of them.
AvianSuicide 3 years ago
HA! The Rick Roll was priceless!
amyw423 3 years ago 11
Hmmmm...
You know, I have a habit of putting controller code in the model. The MVC frameworks I've used have usually had the controller handing off to the model, which then calls the view.
somecomputergeek 3 years ago 3