documenting bindings (was: Re: Dynamically loading a part of a Window in Cocoa)
documenting bindings (was: Re: Dynamically loading a part of a Window in Cocoa)
- Subject: documenting bindings (was: Re: Dynamically loading a part of a Window in Cocoa)
- From: Andy Lee <email@hidden>
- Date: Thu, 02 Jul 2009 17:25:13 -0400
On Thursday, July 02, 2009, at 11:39AM, "Michael Ash" <email@hidden> wrote:
>On Wed, Jul 1, 2009 at 11:18 PM, Marco S Hyman<email@hidden> wrote:
[...]
>> That leads directly to something I've been thinking about as one new to
>> cocoa:
>> how do you document your bindings? Any preferred formats other than a text
>> file stuck somewhere in a project?
>
>If you're going to stick your bindings in a text file, why not stick
>them in a text file which happens to end in .m, and document them in a
>format that the compiler can understand? In other words, why not just
>make your bindings in code? Then you can easily see them, you can
>comment them to your heart's content, you can search for them, and all
>the other benefits of having stuff not be in your nib.
My first reaction was: "Elegantly put!" But then I thought, isn't *not* generating this kind of code one of the reasons we tell people nibs are good? Wouldn't a .m be a good place to "document" targets and actions as well? And delegates and other outlets? Or do you think there's something about bindings that makes them subtle enough that for *them*, in some cases, it might make sense to "document" them by coding them?
--Andy
_______________________________________________
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