The view displays the model in the UI yes, but the controller also affects the application's presentation, albeit not visually. Repetitive controller logic like a repeating subroutine that is modifying the view, should be factored into action helpers. Repetitive display logic belongs in view helpers as you correctly pointed out. I consider both part of my application's presentation ( but maybe the line is blurred in passive MVC )
Matthew Weier O'Phinney-3 wrote: > > > Umm, not really. Controllers take the request, and determine what > view(s) and/or model(s) need to be instantiated. The view is the actual > presentation layer. > > -- View this message in context: http://www.nabble.com/Split-controller-actions-into-multiple-classes-tp25508838p25551508.html Sent from the Zend Framework mailing list archive at Nabble.com.
