• 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: Rainer Brockerhoff <email@hidden>
  • Date: Fri, 2 Nov 2007 09:45:55 -0200

At 04:07 -0700 02/11/2007, RICKY SHARP wrote:
>Thanks again; this helps greatly.  It's all starting to make sense now.  I know when I get home I will definitely be filing bugs against several things to include the ClockControl sample and stock IB plugin template in Xcode.  Both need to give you something working out-of-the-box.
>
>I'll double-check the docs too for any mention of overriding requiredFrameworks.  I've been only concentration on the "quick start" section so that's probably why I didn't see it before.  Still, the quick start section should include such a step.

The new docs are marvelously better than the previous ones, which were almost non-existent, but it's true they still can be improved.

I had started way before the final ibplugin template came out, so I in the end just made a sample project from that and copied some settings etc. over to my old project. Haven't checked for the GM version, though.


>Finally, I did find IBFragmentView sample code, but it's half-baked at most.  The biggest problem with that sample is that the plugin extension still uses ".bundle".  Even after renaming to ".ibplugin", I think it also suffers the dependent frameworks issue.

When I started, I thought I could get away with a simple renaming, but in the end I didn't use more than a handful of lines from my old palette code - and those were in categories on my own class. Everything has changed; it's not a conversion job at all.

You really have to go over, line by line, both the IB plugin programming guide and the 8 class reference documents, and check each method to see if you have to implement it...

--
Rainer Brockerhoff  <email@hidden>
Belo Horizonte, Brazil
"In the affairs of others even fools are wise
 In their own business even sages err."
Weblog: http://www.brockerhoff.net/bb/viewtopic.php
 _______________________________________________
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: 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: Rainer Brockerhoff <email@hidden>)
 >Re: Grief with porting IB palettes to plugins (From: RICKY SHARP <email@hidden>)

  • Prev by Date: Re: Grief with porting IB palettes to plugins
  • Next by Date: Re: Xcode 3.0 frequent lockups
  • Previous by thread: Re: Grief with porting IB palettes to plugins
  • Next by thread: Re: Grief with porting IB palettes to plugins
  • Index(es):
    • Date
    • Thread