Re: How does Apple want us to deal with custom elements in Xcode 4, with IBPlugins having been killed?
Re: How does Apple want us to deal with custom elements in Xcode 4, with IBPlugins having been killed?
- Subject: Re: How does Apple want us to deal with custom elements in Xcode 4, with IBPlugins having been killed?
- From: Sean McBride <email@hidden>
- Date: Tue, 16 Aug 2011 11:56:08 -0400
- Organization: Rogue Research Inc.
On Mon, 15 Aug 2011 20:21:15 -0500, Charles Srstka said:
>I do hold out a tiny bit of hope that this might all be related to
>Xcode’s ill-fated adoption of garbage collection. The old IB plugins
>didn’t support GC, so they wouldn’t be compatible with Xcode 4
But this would only require a few code changes and rebuilding your .ibplugins. Binary compatibility of ibplugins is not too important I don't think.
In my own case, I had to switch some code from GC-only to dual mode so that I could make an ibplugin, it was still worth it.
I have about 20 nibs that all use a complex view that exposes about 15 custom bindings. Not looking forward to adding all those programmatic bind:::: calls. :(
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden