Seems like every project I'm on uses a Model View Controller architecture, and that's how I roll my own projects. Is there an alternative? How else would one create an application that has persistent storage and a user interface?
+4
A:
Classic CRUD apps built using tools like VB6 and Delphi have user interfaces, persistent storage and don't use MVC. Most of them used data aware controls linked directly to database fields
anon
2009-04-17 07:11:02
A:
User interface is View and an application will always have a model and the bridge between the two is Controller. The whole MVC is nothing special as this is how the things will be always.
At the most you can get rid of Controller and have your view talk to your model but you loose the flexibility.
Bhushan
2009-04-17 07:12:22
+2
A:
You can read some article here: http://en.wikipedia.org/wiki/Architectural_pattern_(computer_science)
Dels
2009-04-17 07:14:39
Isn't SO's "Markdown" formatting system great? I just love how a major website centered around a massive programming community is unable to parse URLs with underscores in them correctly. =p
Calvin
2009-04-17 08:16:01
It's not the underscores :P It's the parenthesis :P
Sekhat
2009-04-17 08:17:45
Just don't use markdown for this one - wrap the link in a regular html anchor tag and it'll work fine.
Jon Cage
2009-04-17 08:30:02
<a></a> doesn't work by itself, you need to escape the parens with %28 and %29. (I fixed it btw)
Brad Gilbert
2009-04-17 13:52:53
Ah, I always thought it was the underscores. I just remember trying to post a link one time and not being able to get the close tag to work (the entire second half of my post was being linked). I think I was trying to post a Wikipedia link as well when it happened. I guess that's why escaping the underscores didn't fix it. I ended up simply putting the link at the end of the post.
Calvin
2009-04-17 19:16:51
+7
A:
MVC has been around for a while. It's a time tested and proven pattern. Many frameworks leverage the MVC Pattern. Martin Fowler has deconstructed the MVC into: Supervising Presenter and Passive View.
Architect Christopher Alexander said it best:
Each pattern describes a problem which occurs over and over again in our environment and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice.
I'm not sure why you would want to move from MVC. Is there a problem you are encountering that MVC does not eloquently solve? To give you a better answer we need to know more about your problem domain.
Things to take into account when considering patterns/architecture: If you are building something with a Myspace type architecture you'll need a robust architecture (MVC). If you are creating a simple crud interface via the web - almost anything will do.
For .Net Web forms (I am assuming web, since you didn't say thick or web client) which is not MVC, it was a nightmare maintaining them. Web Forms applications that lived more that a couple years tended to become big balls of mud. Even then developers discovered ways to use MVC with web forms.
Ironically, the lack of MVC architecture in ASP.NET web forms was one of the driving complaints that lead to the development of ASP.Net MVC framework.
From experience if you don't use some MVCesk approach, your solutions become hard to maintain and bloated. These applications will die a slow painful death.
If your solutions are small one-off projects, the by all means throw something together. Heck there are tools that will generate everything from the screens to the data access layer. Whatever works to get the job done.
Chuck Conway
2009-04-17 07:50:34
+3
A:
Couple of links comparing various MV* patterns which might be useful:WPF patterns : MVC, MVP or MVVM or…? & MVC, MVP and MVVM
Gordon Mackie JoanMiro
2009-04-17 08:14:55