Re: Advice: Plugin preference strategy
Re: Advice: Plugin preference strategy
- Subject: Re: Advice: Plugin preference strategy
- From: John Pannell <email@hidden>
- Date: Thu, 2 Feb 2006 17:01:52 -0700
Thanks Dirk-
This was certainly my gut instinct, but then the high-level interface
cannot be used: NSUserDefaults will only operate on my app's prefs
plist - not any other domain's. Looking over CFPreferences, it looks
like all the tools are there. Perhaps I just need to learn to use them!
Any corrections regarding my understanding of NSUserDefaults, or
comments regarding the appropriateness/ease-of-use of CFPreferences
functions is appreciated!
John
On Feb 2, 2006, at 4:06 PM, Dirk Stegemann wrote:
The question... where to keep the plug-in prefs?
Why not storing the individual plug-in's prefs to its own defaults
file?
For sure, each plug-in has a unique identifier
("com.vendor.cool_plug-in").
So the plug-in's prefs would be accessible independently from any
host's prefs, and the plug-in doesn't have to care about the host's
prefs (if it just uses the host's pref, all settings are gone in
case it is loaded by another plug-in).
Also, users sometimes delete certain pref files (when they think
they can fix a problem thereby), so they wouldn't trash everything ;-)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden