Re: Advice: Plugin preference strategy
Re: Advice: Plugin preference strategy
- Subject: Re: Advice: Plugin preference strategy
- From: Dirk Stegemann <email@hidden>
- Date: Fri, 3 Feb 2006 01:06:49 +0200
Hi,
Am 02.02.2006 um 23:55 schrieb John Pannell:
My application consists of a number of interconnected pieces: the
application that people launch is responsible for the UI the people
see and work with, including the preferences for the application.
The application can host plug-ins to extend the app, and loads all
found plug-ins for the purpose of exposing them in the
preferences. Ideally, the user can configure the plug-ins, and I
(and eventually other developers) will provide nib-based UI in the
plug-in bundle for such a purpose. Note that the application
doesn't actually *use* the plug-in - it simply provides a way to
configure the plug-in.
The application, during operation, creates a number of subprocesses
(not threads) that are instances of another faceless application
that are managed via distributed objects. These subprocesses are
instructed to load *one* of the plug-ins (as chosen by the user
during operation of the app), and will need access to this plug-
in's configuration prefs to operate properly.
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 ;-)
hth.
Regards,
Dirk Stegemann
_______________________________________________
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