On Tue, Sep 23, 2008 at 23:13, Alomon <[EMAIL PROTECTED]> wrote: > The homepage contains only one form. One of the table of the DB is a 'user' > table, with 3 users + 2 "admin" accounts. Each user can access to *one* page > ; one of the admin to all 3 pages + another one ; and the other admin to > this 'another page'.
I'd ask you to draw me a diagram, but never mind. :) > So we have 5 pages and 5 accounts. So, a new forms that are somewhat similar but not quite for a number of users of various roles. > I think you have all details to answer me; if not, do not hesitate to ask me > what is missing ;) Well, I still have no idea what this thing does, but I have to say upfront that I don't use MVC at all with the ZF. I'm a RESTafarian, and so have created my own little RESTful system (no, the ZF Rest class has nothing at all to do with REST :) and treat everything as resources and access control. Makes life easier and more flexible. Not sure how to apply this to your scenario, though, but ; I always start out with rejecting a framework for simple applications like this, yet always regret my own short-sightedness. These things always gets that tad extra complicated (especially after you show you tool to your peers) and messy as you hack on yet another insignificant little feature. Frameworks are created because we've all been through this cycle too many times and know that there's a bucketload of mundane and simple stuff we shouldn't have to repeat all the time. ZF is good in that it is more a library of great classes with a common thinking rather than an integrated framework. I often mix and match ZF with others, and it's really the best way to go forward. Alex -- --------------------------------------------------------------------------- Project Wrangler, SOA, Information Alchemist, UX, RESTafarian, Topic Maps ------------------------------------------ http://shelter.nu/blog/ --------
