While this certainly is a nifty feature (thanks Chris, hadn't known about that yet), it's in no way a replacement for having proper live in-editor previews of your actual interface objects. While it allows you to save a couple of lines of code per object, it at the same time—instead of giving you a visual clue—hides them in an inspector. Easily missed by somebody else who's not familiar with your project and wondering "why the heck does this custom object get that property assigned, where is the code?!"
Being a former intensive user of IBPlugins (and contributor to BGHUDAppKit) I'd love to know how the devs of apps like Pixelmator, Kaleidoscope, Capo, do their UIs since Xcode 4. Any of them reading this by any chance? Or the folks in Apple's FCPX/Aperture/… teams. I can hardly believe that those guys actually hand-code their custom UIs, which they clearly have plenty of. They aren't using code, are they? Being unable to use custom UI elements in XIB kind of kills the whole purpose of having an Interface Builder (even more so a tightly integrated one, nowadays) in the first place, doesn't it? So, why remove IBPlugins in the first place, I wonder? Internally Xcode appears to still be using them after all, making Apple's decision even less understandable to me (and lots of others I guess). It looks like Apple turned IBPlugins from being public and recommended API into some kind of forbidden exclusive "private API" for some obscure and apparently political reason. Kind of a dick move, no? Being a free ADC member I'm unfortunately very sparsely informed about Apple's stand regarding IBPlugin's assassination (only through dev blogs & twitter). Could anybody give a brief summary of Apple's stance regarding the future of custom UI in XIBs and/or IBPlugins and Apple's official reasonings for the removal of IBPlugins? Also shouldn't there be some kind of a "IBPlugin Transition Guide" for those who highly relied on them? This is all one can find about IBPlugins these days. It's like Apple is rewriting the past. As if we had always been at war with Eastasia. - Vincent Ps: Sorry if this has been asked over and over before. I'd have loved to, but couldn't RTFD. <rant>And those silly closed up forums (hey, I too signed the NDA, still get no access to them) aren't helping much either. Also, paying for a forum, seriously? </rant> On Aug 14, 2011, at 7:53 PM, Chris Hanson wrote: > If you're targeting Mac OS X 10.6 or later, you can set arbitrary properties > on your objects in Interface Builder that will be set via KVC at nib load > time. > > These are called "User Defined Runtime Attributes" and are specified in the > Identity Inspector right under the place where you can set an object's custom > class. It's a mini-plist editor, so you can specify not just a key path and > a value, but the type of the value; the value can even be a localized string > from your nib's string table. > > -- Chris _______________________________________________ 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
