Re: The Problems with NSController
Re: The Problems with NSController
- Subject: Re: The Problems with NSController
- From: Jonathan Hendry <email@hidden>
- Date: Mon, 27 Oct 2003 00:14:45 -0500
On Oct 26, 2003, at 11:28 AM, Jonathan Wight wrote:
From: Aaron Hillegass <email@hidden>
Date: Sun, 26 Oct 2003 09:42:15 -0500
Subject: The Problems with NSController
If good demos is the goal, NSController is sufficient, but if Apple is
serious about the enterprise, they should take a long, hard look at
this poorly thought-out mechanism and yank NSController. They could
replace it with something more like EOF. Heck, they could just
recompile the old Objective-C EOF source code.
These are harsh words, but someone should have stopped this train a
long time ago. The best I can do now is tell you not to get on.
Your argument to me sounds like "if it isn't EOF, it sucks". I've been
using
NSController & co for a while now and it works for me (despite some
problems
I'm happy to put down to 'learning curve').
Based on my reading of the ControlLayer doc, I really think it's
significantly more complex than EOF was. EOF's architecture was
much cleaner and easier to explain, which, I think, is a sign of
a good design. EOF got hairy at some lower levels, but at the IB
level, it was connect-the-objects and drag and drop.
The net effect is that NSController reduces the number of lines of
code in
my projects and that makes them easier to maintain and extend. I don't
really care whether it "hacks the runtime system", or if Apple isn't
using
NSController in their projects (yet). Some of your points have merit
(like
missing undo support and private APIs) but quite frankly this kind of
scare
mongering isn't particularly useful.
The problem is that people have spent hundreds or thousands of hours
developing real applications with EOF. Applications like financial
trading systems. And having done that, I'm pretty sure it would be
significantly harder with NSController.
What's baffling is that it's almost like they didn't even consider
EOF at all. I mean, wasn't EOF the whole reason Key-Value Coding
was added in the first place? The AppKit and Foundation were extended
for EOF, and now EOF's gone, and they're adding things again to support
NSController.
It's not like they don't have the source code. An institutional memory
is a terrible thing to waste.
I don't get it.
All that said, it's nice to have something to remove the drudgery of
MVC, at least in smaller apps.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.