On Jul 2, 2009, at 4:25 PM, Andy Lee wrote:
On Thursday, July 02, 2009, at 11:39AM, "Michael Ash" <michael....@gmail.com
> wrote:
On Wed, Jul 1, 2009 at 11:18 PM, Marco S Hyman<m...@snafu.org> 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
This is why I tell people nibs are no good.
Also bindings. ;-)
-Jeff
_______________________________________________
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
