User-agent: Mozilla Thunderbird 1.0.7 (X11/20051026)
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: http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
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:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
