• 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: Grief with porting IB palettes to plugins
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Grief with porting IB palettes to plugins


  • Subject: Re: Grief with porting IB palettes to plugins
  • From: Ricky Sharp <email@hidden>
  • Date: Fri, 2 Nov 2007 17:29:55 -0500


On Nov 2, 2007, at 4:20 PM, Dave Camp wrote:

Got my first plugin working :) As Rainer pointed out previously, I needed to implement requiredFrameworks in the IBPlugin subclass.

I also modified ClockControlPalette and it too now works.

I'm going to file bugs against that sample code as well as the docs. The IB Plugin "Quick Start" section really should include the following additional steps:

6. In the new project window, double-click your framework target to open the inspector window for that target.

7. In the Properties tab of the inspector window, type a custom bundle identifier name in the Identifier field. Ensure the identifier name differs from the one used for the plug-in target.

8. In your IBPlugin subclass, provide an implementation of requiredFrameworks as follows:

- (NSArray *)requiredFrameworks {
return [NSArray arrayWithObject:[NSBundle bundleWithIdentifier:@"framework.identifier.here"]];
}


Or, it should at least point to the chapter on the Simulator which mentions the requiredFrameworks API.

Any chance you can post the working ClockControlPalette sample someplace where others can download it?


Well, that code belongs to Apple, so I won't be reposting it. However, the fix is trivial (sorry, should have included that in the original e-mail).

Add the following to ClockControlPalette.m:

- (NSArray *)requiredFrameworks {
return [NSArray arrayWithObject:[NSBundle bundleWithIdentifier:@"com.apple.ClockControlPaletteFramework"]];
}


The string constant used in that method must match the framework target's bundle identifier.

___________________________________________________________
Ricky A. Sharp         mailto:email@hidden
Instant Interactive(tm)   http://www.instantinteractive.com

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


References: 
 >Grief with porting IB palettes to plugins (From: Rainer Brockerhoff <email@hidden>)
 >Re: Grief with porting IB palettes to plugins (From: "Sean McBride" <email@hidden>)
 >Re: Grief with porting IB palettes to plugins (From: Ricky Sharp <email@hidden>)
 >Re: Grief with porting IB palettes to plugins (From: Ricky Sharp <email@hidden>)
 >Re: Grief with porting IB palettes to plugins (From: Dave Camp <email@hidden>)

  • Prev by Date: Re: Xcode 3 All-In-One oddity
  • Next by Date: Re: Xcode 2.5 linker undefined symbols for PowerPlant application
  • Previous by thread: Re: Grief with porting IB palettes to plugins
  • Next by thread: [ADMIN] Monthly Reminder: How to Ask for Help on Xcode-users
  • Index(es):
    • Date
    • Thread