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: Jean-Daniel Dupas <email@hidden>
- Date: Tue, 16 Aug 2011 13:40:26 +0200
Le 16 août 2011 à 13:20, Vince a écrit :
>
>
>> The point Charles makes about garbage collection is a very valid one.
>> Writing dual-mode code sucks so much that Apple invented ARC. And I'm
>> sure that the Xcode 4 team had perfectly valid reasons for omitting IB
>> plugins from their ground-up rewrite of the IDE, even if garbage
>> collection wasn't among them. But I do hope that the Xcode team
>> reconsiders its abandonment of this technology, especially now that IB
>> is an even more integral and easy-to-use component of the developer
>> tools, and the underlying technologies have changed to make supporting
>> the same code in design mode and at runtime far easier.
> If IBPlugins really are incompatible with Xcode 4 (O_ô), then why is Xcode 4 still/again using them?
> - /Developer/Platforms/MacOSX.platform/Developer/Library/Interface Builder/Plug-ins/CocoaPlugin.ibplugin
> - /Developer/Library/Frameworks/InterfaceBuilderKit.framework/Versions/A/Headers/IBPlugin.h_______________________________________________
Because these plugins are distributed with IB, and if the latter change its API / ABI, all plugins will be updated at the same time.
This is something not possible when the API is public and used by third party plugins.
-- Jean-Daniel
_______________________________________________
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