The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

The controller is the class. The action is the class methods. So, in general, you would need as many methods for the class "controller" as actions. From there you can refactor simple and/or repetitive actions.

"A nerd who gets contacts
and a trendy hair cut is still a nerd" - Stephen Colbert on Apple Users

I understand that, but say for example, I would like to have a view which has both listing and editing, how is the controller set up?

Or say I have a view which displays several different Models, does that mean I should have one controller per view? But if that's the case, won't I have repeated code if there are several places to edit/view the same data?