Question

I have seen all types of tutorials:
View running controller, controller passing model to the view, controller setting setter of view.

An example: MVC for a reading of a news.
The controller loads the Model. If the result of the model is ‘false’ I can call another method from another model containing different block.

The View class must be relevant to, View_found View_not_found?

if (model-> news === true) {
      $ comment = model-> comment ()
}

Would this code snippet be the responsibility of the controller or is it a rule that such logic should belong to business model?

Answer 1

in my experience, i tend to program the model and view as “blind”. the model and view only receives parameters needed and then spits out what is needed. they should do minimal to no logic at all.

for the model it performs minor checks, like parameter type and validity and returns either a result or false. the controller does not know how the data is stored, where, why etc.

for the view, it should receive a string preferably through only one entry point, a function which will do the escape and echo. other than that, the controller should never echo to a page.

everything else is for the controller to digest like validation, calling what’s needed, determine what is what. the controller sees everything:

//get from model, pass parameter - that's it
if (model-> news ('all')) {
    //manipulate data for result
    //get appropriate view
    view->parse(html); //pass html to view, that's it
} else {
    //manipulate data for no result
    //get appropriate view
    view->parse(html); //pass html to view, that's it
}