Re: The Problems with NSController
Re: The Problems with NSController
- Subject: Re: The Problems with NSController
- From: Marc Weil <email@hidden>
- Date: Sun, 26 Oct 2003 10:26:15 -0500
You also have to remember that a lot of people won't start using
NSController for a while. It is not backwards-compatible with Jaguar. Who in
their right mind would write a program that will *only* work in an operating
system that is less than 3 days old? Perhaps Apple considered this and
simply placed the current "version" of the Controller class in Cocoa and
XCode as a placeholder for something else they are currently designing. They
figure that no one will really use it outside of demos and tutorials they
provide, so why make it perfect the first time around?
I know that I won't be using the Controller stuff until many, many months
from now, when Apple assures developers that the majority of Mac users are
using Panther and not Jaguar. The same thing went when Jaguar was first
introduced. People still had to write software that was backwards-compatible
with OS X 10.1 and 10.0, and they didn't start specializing their software
for Jaguar until 3 or 4 months after its release, perhaps even longer.
- Marc W.
On 10/26/03 9:42 AM, "Aaron Hillegass" <email@hidden> wrote:
>
While working on the second edition of "Cocoa Programming for Mac OS
>
X," I have spent a good chunk of time working with NSController and the
>
bindings mechanism. And I have bad news: they are poorly designed and
>
poorly implemented. I sincerely hope that this technique is deprecated
>
because it will become embarrassment for Apple and the entire Cocoa
>
community.
_______________________________________________
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.