Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: How does Apple want us to deal with custom elements in Xcode 4, with IBPlugins having been killed?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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: Eli Bach <email@hidden>
Date: Sun, 14 Aug 2011 00:36:52 -0600

Slowly.  Painfully.  Manually.

As in, instantiate and configure all your custom UI objects in code.

I wonder what the FinalCutPro and the rest of those apps guys do with all their custom UI.  Are they sticking with 3.x.x InterfaceBuilder, or instantiating everything with code/templates, or does their Xcode have support for plugins?

Eli

_______________________________________________

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

Follow-Ups:
- Re: How does Apple want us to deal with custom elements in Xcode 4, with IBPlugins having been killed?
  - From: Richard Somers <email@hidden>

References:
	>How does Apple want us to deal with custom elements in Xcode 4, with IBPlugins having been killed? (From: Samuel Wenschen <email@hidden>)

Prev by Date: Re: Difficulty getting full screen window support in Lion fully working
Next by Date: Re: File Copy With Progress?
Previous by thread: How does Apple want us to deal with custom elements in Xcode 4, with IBPlugins having been killed?
Next by thread: Re: How does Apple want us to deal with custom elements in Xcode 4, with IBPlugins having been killed?
Index(es):
- Date
- Thread