Re: MVC Alternatives?
Re: MVC Alternatives?
- Subject: Re: MVC Alternatives?
- From: Bob Peterson <email@hidden>
- Date: Tue, 3 Jan 2006 09:49:36 -0500
The thing is to not get hung up on the three parts of the design
pattern equalling only three classes in your code.
Some people are trying to distinguish MVC from MVP, Model-View-
Presenter. I'm not convinced there is a difference. (But I'm an old
fogey, and I also don't see the difference between a stub and a mock,
as I've never limited my notion of stub to being codeless.) As the
Cocoa docs have described, there is room for multiple kinds of
controllers in the same application. As you dream up logic you have
to decide where it belongs: in the model because it is universal, in
a business logic controller, because it is specific to your
application's use of the model, or in a view controller, because it
is used to extract simple types from model data. The only time I've
ever had to write view logic is in .NET; That's because I think
Windows Forms are full of badly designed views. Even then I'm really
just writing in lower level view controller that manages simple data
types only.
Here's just two starting points:
<http://developer.apple.com/documentation/Cocoa/Conceptual/
CocoaDesignPatterns/Articles/MVC.html>
<http://www.darronschall.com/weblog/archives/000113.cfm>
\bob
On Jan 3, 2006, at 3:01 AM, Alexander F. Hartner wrote:
In it's core MVC is about separation of concerns. It assigns one
particular responsibility or concern to a particular component /
object. The responsibilities are clearly defined and separated and
should not overlap. This is the bases of many design paradigm's and
architectures. It also provides a lot of flexibility if implemented
correctly for the long run, as it allows any single component to be
changes independently of the others as well as promote reuse.
I haven't come across other paradigm's but there might well be
others. If they do not separate these basic aspects their solutions
could quite easily result in a convoluted product which is not easy
to maintain modify.
Personally I find Cocoa's implementation quite friendly, in
particular with Bindings it is very easy to use.
I hope this helped
alex
Jonathan Faulkenberry wrote:
Hi all,
Simply out of curiosity, are there any popular
alternatives to the Model-View-Controller paradigm?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40j2anywhere.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40contracorner.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden