Thanks Hal. Ya, its all starting to kick in...just have to build that 'way of thinking' that every new methodology requires.
Craig ----- Original Message ----- From: "hal helms" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, May 30, 2002 10:23 PM Subject: RE: another MVC question > User roles are different from Views, Craig. A view represents something > like "HTML" v. "FLASH" v "WAP". Under each of these, you may have > separate "personalities" usch as admin, salesperson, and guest. These > should NOT be grouped by permissions, though, but because each one of > these has a different user experience (thinking of layouts will help you > with this, I find). It's important to ask yourself whether the look and > feel as well as the actual content of the interface is *necessarily* or > *coincidentally* similar. Is it reasonable to expect that at some point, > the different interfaces of personalities might diverge or would doing > so represent a change in the model you have created, in other words. > > I hope that helps, > > Hal > > -----Original Message----- > From: craig girard [mailto:[EMAIL PROTECTED]] > Sent: Thursday, May 30, 2002 1:01 PM > To: [EMAIL PROTECTED] > Subject: another MVC question > > > I have 3 user roles > > template Admin, salesperson, guest > > template admin can do anything a salesperson can, but also > > 1. create a template > 2. delete a template > > a salesperson can do anything a guest can, and also > > 1. create a project from a template > > a guest can do > > 1. view a template > > when creating the controller for these is there anyway to design it so I > do not have to duplicate the overlapping fuseactions? > > right now I see it as this > > /templateApp/controller/templateAdmin > fuseactions - > 1. create a template > 2. delete a template > 3. create a project from a template > 4. view a template > > /templateApp/controller/salesperson > > fuseactions - > 1. create a project from a template > 2. view a template > > /templateApp/controller/guest > > fuseactions > 1. view a template > > I would rather not have to duplicate fuseactions if need be. The only > thing I can think of though is nesting the user role directories by > order of authority like so > > /templateApp/controller/guest/saleperson/templateAdmin > > This does not eliminate duplicating the fuseactions in each directory, > but using FuseQ (SuperQ) I can at least not duplicate the business > logic. > > Has anyone wondered the same thing? Is this possibly already solved > somewhere that I didn't read? > > Thank you, > > Craig > > > > > ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
