Re: Grief with porting IB palettes to plugins
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 15:55:33 -0500
On Nov 2, 2007, at 3:20 PM, Ricky Sharp wrote:
On Nov 2, 2007, at 10:04 AM, Sean McBride wrote:
I don't much like needing a framework either, it's a pain to need a
separate target just to build a framework for one class. Anyway, I
think they did it like that because the simulator now runs as a
separate
process, instead of in IB, and so how else is it supposed to get the
code? The good thing is that the crashing simulator does not hurt
IB.
Anyway, if you don't care about supporting the simulator, you can
just
make a plugin without any framework.
That is indeed true. In my specific case, I make heavy use of the
simulator (main two tasks are validating key loop and reviewing
content for a custom help-tag implementation).
Ricky, I converted the nice SMDoubleSlider code to use an ib3
plugin a
few months ago, now that the NDA is over, I should send it back to
the
author. Hopefully he'll want to publish it... it should made a
good example.
I'll look at that if/when it comes out. Thanks, Sean.
With any luck, I'll have working plugins tonight.
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.
___________________________________________________________
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