Re: The Problems with NSController
Re: The Problems with NSController
- Subject: Re: The Problems with NSController
- From: Jonathan Wight <email@hidden>
- Date: Sun, 26 Oct 2003 10:28:53 -0600
>
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').
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.
To me - the biggest problem with the NSController technology is that it's
10.3 and up only.
Jon.
_______________________________________________
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.