Re: Providing application resources to a Plugin
Re: Providing application resources to a Plugin
- Subject: Re: Providing application resources to a Plugin
- From: j o a r <email@hidden>
- Date: Mon, 21 Aug 2006 23:04:54 +0200
On 21 aug 2006, at 22.42, Eric Czarny wrote:
That seems plausible enough; however, what if I want to provide
specific
functionality of my application to plugins (such as preference pane
plugins,
for example)?
What type of preference pane plugins are you talking about? Not
plugins for the System Preferences application in any case, right?
For instance, suppose I was able to implement plugins for each
blogging API and several preference panes (implemented as plugins
themselves) needed access to the currently loaded API plugin. How
could I
pass them along to the preference panes? Would I need to create a
preference
pane framework that contained what ever headers necessary to
provide access
to the blogging API plugins?
Why would a preference plugin need to access any blogging plugin
directly? If you can provide a couple of concrete example, I think it
would be easier to give good advice.
In the general case I would expect that the application can broker
all interaction between your two sets of plugins so that they
wouldn't need to have any inter-dependencies.
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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