• 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: Valid frameworks
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Valid frameworks


  • Subject: Re: Valid frameworks
  • From: Paul Schneider <email@hidden>
  • Date: Tue, 21 Oct 2008 18:39:53 -0500


Hi Quincey,

That's a bit of a broad question. In general, an FxPlug can link to whatever it needs to, and many parts of the SDK itself depend on AppKit (NSViews, NSCoding, etc).

Most, if not all, of the AppKit runtime should be available to you. For example, the "ScrollingRichText" example in the SDK uses NSWorkspace. There will be a valid instance of an NSApplication available to you through [NSApplication sharedApplication], even in Final Cut (which is sort of a Carbon / Cocoa hybrid).

However, the openness of Cocoa certainly allows you to do some things which may cause problems. There's nothing to stop you from creating your own modeless window which hangs out alongside the application windows, for example. This could confuse the host application, or it might not, depending on how the host is written and what you do inside your window. You could inject your own events into the host application's event loop, which could certainly cause some confusion, again depending on the data you feed us.

Unfortunately, there is no list of operations that are guaranteed by the SDK to work in all versions of all hosts. It's certainly our intention that FxPlugs have access to as many OS-provided services as possible. The best thing is probably for you to post exactly what you'd like to do and how you plan to accomplish it, and let us point out any possible pitfalls.

- Paul


On Oct 21, 2008, at 6:18 PM, Quincey Morris wrote:

I'm a bit confused about which frameworks an FxPlug is allowed to link against.

The template Xcode FxPlug projects all import <Foundation/ Foundation.h> in the plug-in header file, suggesting that plug-ins are not expected to use AppKit. However, the project itself includes the AppKit framework -- as a set of headers AND as a framework to link against in the predefined target.

I'm assuming there's plenty of stuff in AppKit that it's NOT safe to use (anything to do with NSApplication, for example), but the question is what (if anything) is safe to use.

So far, open and save panels seem to work, as does the NSBundle class. Views work, for custom UI parameters, and alerts seem to be OK, but what about additional windows in general? What about bindings? I would like to use NSWorkspace, but I've no idea whether it needs support from the host application or not.

Any guidance about deciding what to use and what avoid would be welcome.

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Valid frameworks
      • From: Quincey Morris <email@hidden>
References: 
 >Valid frameworks (From: Quincey Morris <email@hidden>)

  • Prev by Date: Re: FCP Apple Event project listing bug
  • Next by Date: Re: Valid frameworks
  • Previous by thread: Valid frameworks
  • Next by thread: Re: Valid frameworks
  • Index(es):
    • Date
    • Thread