Re: The Problems with NSController
Re: The Problems with NSController
- Subject: Re: The Problems with NSController
- From: "Alastair J.Houghton" <email@hidden>
- Date: Sun, 26 Oct 2003 15:50:18 +0000
On Sunday, October 26, 2003, at 03:26 pm, Marc Weil wrote:
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?
It's also worth saying that NSController is still pretty neat, for all
its apparent flaws... many of us that don't have a
NeXTStep/WebObjects/EOF background haven't seen anything quite like it
before, and it is still the case that it will allow people to create
software with fewer lines of code.
OK, perhaps EOF was better, but we don't have EOF. If people (like
Aaron) want EOF to reappear, perhaps they should file a bug report with
Apple? Or even use the e-mail addresses that were handed-out at WWDC
to lobby the people responsible for the Cocoa frameworks (they said
they wanted to know how we'd like them to improve things, right?)
Also, if Apple do bring back EOF, then from what Aaron said in his
original e-mail, it sounds as if it would be possible to re-implement
NSController in terms of EOF (OK, you'd still have the secret subclass
hack, but we're just going to have to live with that). So perhaps we
shouldn't worry too much at this point?
Kind regards,
Alastair.
_______________________________________________
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.