On Mar 25, 2011, at 21:03, Carlos Eduardo Mello wrote: >> If you're working with XCode 3.x, you can write an Interface Builder plugin >> for your custom view. I'm sure there are good tutorials online on how to >> create them. In XCode 4, however, IB plugins aren't yet supported. > > I am using 3.1.2, but what if I uograde to 4, would the plugin work be > wasted? I really have no idea how much work it takes (will look into that > right now) but it seems like it would be a waste to spend time making a > plugin if I couldn't maintain and reuse it when working with future releases > of the develpment tools. > > Are plugins the only way to go for this?
The IB3 learning curve for writing plugins is quite steep**. No one has any idea when or if IB plugins will be supported by Xcode 4, but if so (which seems like a good bet) I suspect the mechanism will be significantly revamped. ** The problem with IB3 plugins is that the documentation is written as if the normal thing to do is to create a framework with your plugins, which you would distribute to "client" developers and/or interface designers, who would install the framework in /Library/Frameworks. Maybe that happens sometimes. In practice, what you usually want to do is integrate the framework directly into your Xcode project(s), and use it yourself. The IB3 plugin system supports this, in a roundabout way, but it's not extremely well documented, and there's a nasty gotcha with the load path for the framework. As we've seen on the list recently, if something goes wrong it's extremely frustrating to debug the setup. _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
