architecture question about writing to NSUserDefaults
architecture question about writing to NSUserDefaults
- Subject: architecture question about writing to NSUserDefaults
- From: "Mike Chambers" <email@hidden>
- Date: Fri, 12 Dec 2008 10:03:18 -0800
I have an application that opens a sheet. The sheet needs to read and
write information to NSUserDefaults.
If I built this in ActionScript (which i am familiar with) I would
pass the appropriate information to the sheet, and have the sheet send
a notification / event (which the controller would listen for) that it
needs to have some values saved to NSUserDefault. i.e. only the
controller would actually read and write NSUserDefaults.
Is this the appropriate architecture in Cocoa? Or should I just pass
an instance of NSUserDefaults to the sheet, and have it read and write
as appropriate (The controller will also read and write to it for
other settings).
Thanks for any feedback and input...
mike
_______________________________________________
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