Re: Why so many public properties all up in my grizzle?
Re: Why so many public properties all up in my grizzle?
- Subject: Re: Why so many public properties all up in my grizzle?
- From: Charles Srstka <email@hidden>
- Date: Mon, 19 Mar 2012 20:28:03 -0500
On Mar 19, 2012, at 7:28 PM, William Squires wrote:
> The fact that the header declares your IBOutlets and IBActions is intentional, otherwise your design would be too-tightly coupled; this isn't good... Not only does IB need to know where the outlets and actions are, so do any other designers (including yourself at a later date) who then want to make an alternate view on your data; all they need to is connect the new view (xib) to your existing controller and wire up the outlets and actions.
The thing about that is, in the latest versions of Xcode, IB *doesn’t* need IBOutlets and IBActions to be in the header. You can put this stuff in the .m file, and IB finds it just fine.
Charles
_______________________________________________
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