Re: What's it called if it's not a controller?
Re: What's it called if it's not a controller?
- Subject: Re: What's it called if it's not a controller?
- From: James Duncan Davidson <email@hidden>
- Date: Mon, 26 Jan 2004 21:19:34 -0800
On Jan 26, 2004, at 20:47, Peter Jaros wrote:
I have an NSMatrix of NSButtonCells, each of which I want to bind to
certain keys, and the most convenient way to do this is
programmatically, iteratively. Where do I put this code? My instinct
tells me to put in in a "controller" class, but now controllers are
something else. Should I invent myself a meta-controller layer? :)
Where does excess glue code go?
It's still a controller. NSController is just the super-new
super-spiffy thing, but they don't mean that all the other controllers
in your MVC can't be called controllers anymore.
I find it interesting that the Apple documentation seems to be
migrating from calling the new stuff "Controller Layer" to "Cocoa
Bindings". I'm hoping this sticks as I like it much better
(personally).
http://developer.apple.com/documentation/Cocoa/Conceptual/
CocoaBindings/index.html
You can see the revision in names here:
http://developer.apple.com/documentation/Cocoa/Conceptual/
CocoaBindings/RevisionHistory.html
.duncan
_______________________________________________
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.