Re: Binding NSTableView columns to dynamic properties in Core Data?
Re: Binding NSTableView columns to dynamic properties in Core Data?
- Subject: Re: Binding NSTableView columns to dynamic properties in Core Data?
- From: Rick Mann <email@hidden>
- Date: Sun, 30 Dec 2012 20:11:22 -0800
On Dec 30, 2012, at 20:08 , Keary Suska <email@hidden> wrote:
> It seems to me that the amount of work involved in maintaining the bindings would be more troublesome than simply using data source methods. You would also have much more control as well. I have done basically what you are thinking in the way of a simple database querying UI, where the results would be loaded into a table whose columns are dynamically created to match the columns of a SQL "select" query. Data source is the way to go.
>
> Note, however, that you don't get all of the "free" behavior that NSArrayController gives you for adding objects (especially undo) nor the "free" stuff you get from bindings for cell editing. But it's not hard to code and the managed object context will still maintain undo for you. I still think the build up/tear down of bindings will be more of a pain and more fragile in any case.
Great considerations. Given that the data really isn't intended to be editable (at least, not in the first release), and the user can't add or delete rows, perhaps you're right, and the data source is the way to go.
I have a related table that displays details about the row selected, and that, I think, can still be done with Bindings.
--
Rick
_______________________________________________
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