Lee, Thanks, that does give me some good Insight. I was wondering if you still separate them into directories if the do not use ANY common views. I think your email address that though.
Can you define what you mean by Entities? Just to make sure I follow you. Thanks, Craig ----- Original Message ----- From: "Lee Borkman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, May 30, 2002 9:39 AM Subject: Re: MVC question > Hi Craig, > > I'm not sure I understand your question. You are asking about a situation where the CSR and Manager Views have > *nothing* in common, is that correct? Surely, in that case, there would be a very clear need for separate CSR and > Manager Views. > > In the general case, I think that this is the basic set-up: > * 1 Model per entity (probably only *independent* entities); > * 1 View per user/role > * 1 Controller per user/role > > I don't really know if that addresses your question ;-( > > Thoughts, anyone? > LeeBB > > ----- Original Message ----- > From: craig girard <[EMAIL PROTECTED]> > > > > In MVC, I believe the reason for such a directory structure > > > > MyApp/Admin/View/CSR > > MyApp/Admin/View/Manager > > > > is when I have views that are different for both CSR and Manager. > > > > Say however the views for this curcuit were never duplicated. IE. CSR and > > Manager never used the same views. Using MVC design would you still create > > the CSR and Manager directories for organizational sake? Or are we not > > worried about that sense the controller will handle it? > > > > Hope this makes sense. > > > > > ==^================================================================ 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 ==^================================================================
