(10-29-2014, 08:50 PM)jlp Wrote: I tend to agree with Hobbes. Part of what I try to get through to my students is proper separation of concerns. Controllers are for handling usecases, models encapsulate data sources, and views present stuff for human consumption. Taken to an extreme, we end up with a Model-View-Adapter pattern, where the view has no idea where data comes from - that is up to the controller.
I give my students a small set of "golden rules" at the beginning of my course...
If a model generates HTML, you are "fired".
If a view is aware of the origin of data (eg RDB), you are "fired".
In this context, "fired" means 20% off your grade for a lab or assignment, no questions and no mercy. You also get "fired" if your webapp somehow triggers a PHP error visible to the user.
This is a simplisitic view, and doesn't work or apply in absolutely every case, granted, but it sure drives home the point of MVC 
Man, there are a lot of 'programmers' out there that would be fired. Good thing for enforcing the rules. You should make sure they get fired if they don't escape SQL queries too ^^
