Re: Handling preferences changes
Re: Handling preferences changes
- Subject: Re: Handling preferences changes
- From: Steve Israelson <email@hidden>
- Date: Thu, 3 May 2007 14:11:01 -0700
I have gone over this in more detail with my partner and it seems the
best thing is to use CoreData to store all the settings and then have
a main theme controller that each view or controller can make use of
to get the settings they need.
They can then retain each setting and observe the values they need to
in order to render and thus detect changes made.
This means I can write zero code for my preferences window since
CoreData and Bindings work well.
I may have to write code to place the DB into the prefs system, but
that seems minor.
Since I need to keep each entity around for rendering anyway,
observing each value is not a big issue. I can put all that code into
one init method.
If you have any other comments, feel free to send em along.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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