Re: The Problems with NSController
Re: The Problems with NSController
- Subject: Re: The Problems with NSController
- From: Brent Gulanowski <email@hidden>
- Date: Sun, 26 Oct 2003 12:34:44 -0500
On Sunday, October 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').
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.
Considering the amount of time Aaron has been working with these
frameworks, you should take a little more time before accusing him of
FUD. It's not like he has some competing product to sell. He's staked
his career on this stuff and so far has been nothing but a supporter in
the Cocoa community.
To me - the biggest problem with the NSController technology is that
it's
10.3 and up only.
I have to say that it is clearly a kind of hostage-taking tactic on
Apple's part, considering the ease with which they could patch earlier
versions of the operating system, and certainly Jaguar. I'd like to see
them for once demonstrate the fantastic simplicity of their own bundle
design and release new versions of the Cocoa frameworks for Jaguar.
Then again, I'm happy with what exists now. Whatever this NSController
class does, someone else (maybe even me) can probably implement
something as good or better, given time. However I would like even
better if I could be proved wrong about Aaron's not having a better
product. If he or someone else could replace EOF with a new product,
that would be, in my opinion, the best strategy. I have just recently
been reading up on the origins of Objective-C and the concept of
general purpose components, and I have to say that it seems as though
the real power of objects in the marketplace has never been realized.
"Not built here" syndrome seems to be alive and well (even in the Open
Source community), scattered exceptions aside.
I guess everyone's still worried about Apple undercutting them. Seems
that Operating Systems vendors are still the number one obstacle to
software innovation. Not a happy situation.
ASIDE: did anyone else note that Apple has got a rotational slider in
the Font Panel similar to the one from Jiiva?
--
Brent Gulanowski email@hidden
_______________________________________________
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.