Yes, it is thick to me. Sometimes it is useful to make it a goal to have 1 action per controller, when you have a lot of actions per controller I have found it makes you more hesitant to break up actions into helper methods ( the relationship of actions to helper methods for me is not 1:1 so more then 4-5 complex actions and I could easily have 25+ helper methods bloating the controller. When the actions are spread out across controllers it can make it easier to factor, and they can always be re-combined later after some of those helper methods mature and are "moved up" into more abstract classes
Ryan Chan-2 wrote: > > Hello, > > On Mon, Sep 21, 2009 at 9:55 PM, Matthew Weier O'Phinney > <matt...@zend.com> wrote: >>> If it is repetitive presentation logic you could sub-class the >>> Zend_Controller_Action or create action helpers if the repeating logic >>> are >>> "cross cutting concerns". Keep in mind the saying is "fat model thin >>> controller" not just "thin controller" >> > > For example, do you think the following code is a "thick controller"? > and difficult to manage? > > http://howachen.googlepages.com/test.php > > > For me, it is. > It would be better to manage if each action is in a separate PHP class > file, isn't? > > -- View this message in context: http://www.nabble.com/Split-controller-actions-into-multiple-classes-tp25508838p25600132.html Sent from the Zend Framework mailing list archive at Nabble.com.
