I'm pretty terrible at the whole MVC thing but I've done ok with a separate controller for each table (except for obvious exclusions like intersection tables or tiny tables for normalization purposes), and then extra controllers for stuff in your app, like "users", and action helpers / bootstrap code for stuff that you'll use across all the controllers like logging or ACLs.
One thing I will say is that you'll probably end up implementing a "Base" controller that all your other controllers inherit from. Apparently you are meant to use action helpers for stuff like that though, but eh... it works for me and it is pretty simple and easy to follow. On Mon, Dec 1, 2008 at 7:13 PM, Julian102 <[EMAIL PROTECTED]> wrote: > > Hello, > > I am new to using the MVC (or any other design pattern) as well as zend > framework. > > I can find lots and lots of documentation on what a controller is and how > it > works however I am still struggling to find out how to decide how to > organise controllers in my applicaiton. > > Say I had a community site where people go to discuss their faviroute music > albums and it was made up of the following > > a bar at the top where people can login, register, logout, access their > personal account > > home page (where you can pick your preferred genre) > page which shows each album in that genre > page which allows people to discuss the album they have picked > login page > signup page > logout page > > How would you decide what the controllers are. > > If you could help me, or point me to somewhere that can I would be very > greatful > > Thanks in advance > -- > View this message in context: > http://www.nabble.com/Question-on-organising-controllers-tp20768820p20768820.html > Sent from the Zend Framework mailing list archive at Nabble.com. > >
