Views and PHP Code

[eluser]Colin Williams[/eluser]
I think there are distinctions to be made between "application logic" and "display logic." Keeping roles clearly separated, the controller should do little "display logic", because this takes power away from the views.

So what's the solution, do both! Let's say I have a blog app and there are areas where one expects to see a list of blog posts. Where do you loop. You can send an array to the view and have it loop, or you can loop from the controller, calling a view on each iteration, and send the result to the view. Or, you can do both. Pass the array and the rendered iterative result to the view. The "designer" can either template each iteration in the view that is called multiple times, or get "fancy" and iterate from the "parent" view. Best of both worlds.