Re: plugin theory
Re: plugin theory
- Subject: Re: plugin theory
- From: Uli Kusterer <email@hidden>
- Date: Mon, 10 Apr 2006 08:45:36 +0200
Am 10.04.2006 um 00:05 schrieb Jeffrey J. Early:
on 4/9/06 10:58 AM, Ryan Glover at email@hidden wrote:
In my mind, the app should launch, create a list of
available plugins and populate the menu with their names and only
when the user selects the menu option is an instance created. Is it
possible to create a list of available plugins without creating an
instance of each of the plugins?
Once you have an array of all the valid plug-ins, like Ed Baskerville
showed, you could then query the class to find out how it wants to
identify
itself, without actually instantiating the class.
You can also add keys to the Info.plist or some property list file
of your own design inside the plugin bundle. Then you can use those
keys to get some basic information about a plugin *before* you decide
whether you'll even load the class. That way, you can e.g. have
importer plugins not loaded until the user actually exports to that
particular file format.
Cheers,
-- M. Uli Kusterer
http://www.zathras.de
_______________________________________________
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