• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Providing application resources to a Plugin
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Providing application resources to a Plugin


  • Subject: Re: Providing application resources to a Plugin
  • From: "Eric Czarny" <email@hidden>
  • Date: Mon, 21 Aug 2006 16:42:11 -0400

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)? 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?

Cheers,
Eric

On 8/21/06, j o a r <email@hidden> wrote:

On 21 aug 2006, at 20.59, Eric Czarny wrote:

> Say, for instance, I have a blogging application that should support > multiple blogging programming intefaces. If I were to implement each > blogging API as a plugin, how could I provide a common resource > (such as an > XML-RPC client) without linking them directly to the framework? > Meaning, I > would like to have my application link to (and include within its own > bundle) the XML-RPC framework. Could I simply include the XML-RPC > headers > within a Plugin.framework, along with the plugin's protocol and > abstract > class?

If both application and plugins needs access to the functionality
provided by your XML-RPC framework, why not allow both application
and plugins to link to it? While it's possible to do what you suggest
(by suppressing linker warnings), it's a less elegant approach.

Build the framework with the "@executable_path/../Frameworks" install
path build setting and include it in the application bundle. This
will allow both application and plugins to find it when the
application is running.

j o a r

_______________________________________________
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


  • Follow-Ups:
    • Re: Providing application resources to a Plugin
      • From: j o a r <email@hidden>
References: 
 >Providing application resources to a Plugin (From: "Eric Czarny" <email@hidden>)
 >Re: Providing application resources to a Plugin (From: j o a r <email@hidden>)

  • Prev by Date: Re: Providing application resources to a Plugin
  • Next by Date: Re: Newbie: Alignment and resizing of window
  • Previous by thread: Re: Providing application resources to a Plugin
  • Next by thread: Re: Providing application resources to a Plugin
  • Index(es):
    • Date
    • Thread