Hey guys
I am currently trying to get my head around core data. First
impression - quite impressive.
I've followed some tutorials to get started but somehow I am a bit
lost when I want to do some more complex things. This might actually
be more because of bindings than because of core data. Or maybe I just
did not look at the right place. Maybe you guys can give me some hints
links and so on.
I have got a little demo project. I have a NSTableView bound to a Core
Data array of objects that where I can edit the name. So that was the
first easy step. Here are a few more:
1.) What I want to do next is show all attributes of the object in my
NSTableView. Right now I assume I need to subclass the NSTableCell and
somehow make the NSTableView use that class instead. Then I will need
to bind the individual attributes to the controls in that view. Is
that the correct way to do it?
2.) Instead of binding ALL the objects to the NSTableView I would like
to filter the objects so only objects e.g. with attributes
"color='red'" get shown.
3.) Now I would like be able to make this filter more dynamic. For
example adding 3 buttons. "show red", "show green", "show all".
4.) Next thing would be to have this filter somehow defined
dynamically. Having the user assigning the condition "color='red'" to
the "show red" button and so on.
I was also wondering ...what if we are talking about 1M objects (or
rows thinking of it in terms of a database). How does this scale?
Also I am wondering about migrations. When you change the data model
and users upgrade the application. How can one define the migrations?
cheers
--
Torsten
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
