> No more .ibplugins in Xcode 4, so now what...? I've faced the same problem, and found no elegant solution. Removing dependencies on external plug-ins from a large IB file is tedious and error-prone. Maybe it's unreasonable to think that Xcode will support plug-ins again, but I'm still hopeful. Apple ships numerous complex applications that do not use standard Cocoa controls (think all Pro apps that rely on the ProKit private framework). Are we to believe that they are laying out and configuring their UI programmatically? My guess is that they are also still using IB3 until Xcode 4 supports IBPlugins again.
If it turns out that there is really *no* hope to get them back, a good question for Apple engineers at WWDC would be to let them explain what they're doing for Aperture/Logic Pro/Motion/etc. Given that those are *their* apps, I'm sure that's a pretty strong argument in favor of IBPlugIns or something equivalent. Gabe_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
