Here's what I have

plist file -> NSMutableArray of NSDictionary instances

NSDictionary instances all have the same keys, but different values (like a 
database record)

each NSDictionary maps to another class, RBSStore, that has properties that map 
to the keys of the NSDictionary's, and that has 2 methods:

-(id)initWithDictionary:(NSDictionary *)aDic;
-(NSDictionary *)storeDictionary;

so that I can go from NSDictionary<->RBSStore. I've got the UI laid out, 
including the  NSTableView (for displaying the NSDictionarys in the 
NSMutableArray, NSTextFields for each individual column (so that when you 
select a row, that row's info shows up in the NSTextField's, and one 
NSSearchField (not implemented yet.)

Mostly, this is all done via code. How can I transform this into a design that 
uses bindings and an NSArrayController to eliminate most of the tedious BS, and 
allow the table view, text fields, and so on to all be linked together so when 
you update a field, the appropriate row in the table view (and the 
corresponding NSMutableArray model) all stay in sync?

Mostly, what I don't understand is: what part of the work does the 
NSArrayController perform? Am I going to need an NSObjectController also to 
manage the individual rows (which are NSDictionary instances) and their 
corresponding NSTextFields? The big problem is the docs just describe the 
programmatic interface to the CoreFoundation classes, but not how to use them 
in real-world situations, or how to use them within IB.


_______________________________________________

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 arch...@mail-archive.com

Reply via email to