On Fri, May 13, 2011 at 1:02 PM, Mark Munz <unmar...@gmail.com> wrote: > Then maybe Xcode 4 wasn't ready for public consumption.
There are a lot of things about Xcode 4 that people consider worthy of holding it back. Whoever decides the release schedule obviously disagreed. > I think some > of us that believe Apple's previous praise for their new IB3 plugin > API feel serious burned by that. The fact that there is no replacement > at hand means that I'll likely waste many more hours undoing IB3 > plugin stuff in my XIB files just so I can build for the future. Yes, > Xcode 3 offers a solution for now, but it won't be there for future > development. > > All in all, IB changes were a major step backward with this new > release. It is harder to use, less flexible, completely un-extendable, > and I've yet to see any real benefit from this change as a developer. We're starting to head off-topic here. The important thing to do now is to file bugs against Xcode 4's lack of an IB plugin API. Yes, complaining is cathartic and might be great exercise for developing an argument, but even the most well-though argument isn't helpful unless it's presented to the right people. --Kyle Sluder _______________________________________________ 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
