Bob, Yup I'd say you got it. Using the MVC PATTERN, not some specific API or app.
Bob wrote "then you're not going to gain anything by using MVC (cause you're already using it)." Yup, this is the conclusion I have come to. We have decided to keep views in with the controller files and put the models under their own directory. We want the model separated so we can use it with other applications. Bob wrote "You seemed to be referring to a "technology" which MVC isn't. It's just a pattern." Ya, sorry, just using a generic term for it. I guess my BIG question is if you are already using FB, what is the advantage of MVC? I am not seeing much, as it seems FB is already a form of MVC. Thanks, Craig ----- Original Message ----- From: "Bob Jacoby" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, June 04, 2002 5:30 PM Subject: Re: Can you give me the 'why's' of MVC? i guess i'm confused. When you say directory structure are you referring to: /src/model/ /src/controller/ /src/view/ as opposed to /src/everything (or some other structure of your choosing? And when you say you've "been working with MVC" what do you mean? Are you referring to a specific product/tool/API that utilizes the MVC pattern or just the pattern itself? If the former then it's just the way that product stores the separate parts - separate directory structures is not required by the pattern. I've done both before. Since you've been doing things the MVC way before realizing what the "MVC" pattern is, then you're not going to gain anything by using MVC (cause you're already using it). am i missing something in your question? It didn't seem like you were asking why use the MVC design pattern in the first place, since, again, you said you've already been using it. You seemed to be referring to a "technology" which MVC isn't. It's just a pattern. Bob >>> [EMAIL PROTECTED] 06/04/02 03:45PM >>> I have been working with MVC for the past couple of days and what has dawned on me is that I am really replicating what I have been doing in regular fusebox all along. Separating code into views, models, and controllers. The difference seems to be now I am separating them into their respective directories, which I am not seeing the need for. This has got me wondering is MVC truley solving a problem, or is it just the latest 'thing' to do? When faced with this question I always ask "why should I use this 'technology'?" And many time comes out that its overkill for what I wanna do. Why do I want 3 separate directory structures? Why is model/view/controller an advantage over basic fusebox? Can you give me the whys? Thanks, 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 ==^================================================================
