• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: documenting bindings (was: Re: Dynamically loading a part of a Window in Cocoa)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: documenting bindings (was: Re: Dynamically loading a part of a Window in Cocoa)


  • Subject: Re: documenting bindings (was: Re: Dynamically loading a part of a Window in Cocoa)
  • From: Michael Ash <email@hidden>
  • Date: Fri, 3 Jul 2009 00:10:36 -0400

On Thu, Jul 2, 2009 at 5:25 PM, Andy Lee<email@hidden> wrote:
> 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?

Sure, that would be a fine place to document them. And yes, I don't
think anybody ever does. Why not? Well, I don't think they document
them *anywhere else* either. Target/actions and outlets and such are
simple enough that people don't seem to feel the need to document them
at all.

If for some reason you *did* feel the need to document those, setting
them up in code would be a fine way to go.

Mike
_______________________________________________

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

References: 
 >Dynamically loading a part of a Window in Cocoa (From: Debajit Adhikary <email@hidden>)
 >Re: Dynamically loading a part of a Window in Cocoa (From: Thomas Davie <email@hidden>)
 >Re: Dynamically loading a part of a Window in Cocoa (From: Quincey Morris <email@hidden>)
 >Re: Dynamically loading a part of a Window in Cocoa (From: "Adam R. Maxwell" <email@hidden>)
 >Re: Dynamically loading a part of a Window in Cocoa (From: Quincey Morris <email@hidden>)
 >Re: Dynamically loading a part of a Window in Cocoa (From: "Adam R. Maxwell" <email@hidden>)
 >Re: Dynamically loading a part of a Window in Cocoa (From: Marco S Hyman <email@hidden>)
 >Re: Dynamically loading a part of a Window in Cocoa (From: Michael Ash <email@hidden>)
 >documenting bindings (was: Re: Dynamically loading a part of a Window in Cocoa) (From: Andy Lee <email@hidden>)

  • Prev by Date: Re: Windows on main thread always only sometimes?
  • Next by Date: Re: Replace -[NSKeyedUnarchiver unarchiveObjectWithData:] so it doesn't crash on corrupt archive
  • Previous by thread: Re: documenting bindings (was: Re: Dynamically loading a part of a Window in Cocoa)
  • Next by thread: Re: documenting bindings (was: Re: Dynamically loading a part of a Window in Cocoa)
  • Index(es):
    • Date
    • Thread