Re: Why use NSObjectController?
Re: Why use NSObjectController?
- Subject: Re: Why use NSObjectController?
- From: Gordon Apple <email@hidden>
- Date: Sun, 10 Aug 2008 23:39:25 -0500
- Thread-topic: Why use NSObjectController?
I don't use CoreData. Frankly, the main use I have made of
NSObjectController is to decrease my typing in IB bindings. For example, my
inspectors have a large number of controls that are bound through a fairly
long chain of references to their controllers. By using an
NSObjectController to handle the long chain, my individual bindings are much
shorter. Your mileage may vary.
On 8/10/08 11:29 PM, "email@hidden"
<email@hidden> wrote:
> On Aug 10, 2008, at 10:23 PM, Seth Willits wrote:
>> What is it that NSObjectController offers me?
>
> Great question. You are on the long steep ascent to Bindings
> understanding. For me the top is still way up there shrouded in clouds.
>
> I'll take a stab at answering your question:
>
> 1) NSObjectController fits in with Core Data
> 2) It works with a managed object context to give you undo and redo
> for "free"
> 3) It's subclasses are perhaps more handy, e.g. NSArrayController.
>
> Notice my answer contains no detail whatsoever. I still have much to
> learn.
>
> There's actually a good & useful sample using NSObjectController,
> http://developer.apple.com/samplecode/DepartmentAndEmployees/listing12.html
>
> Cheers,
> Graham.
G. Apple
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden