On Wed, Jul 1, 2009 at 11:18 PM, Marco S Hyman<[email protected]> wrote: > On Jul 1, 2009, at 6:50 PM, Adam R. Maxwell wrote: > >> Well, I generally avoid bindings, since I can't comment nib/xib files, and >> it takes too long to reverse engineer my own (or worse, someone else's) >> bindings when I'm doing maintenance work. With that perspective, the minor >> glue code to swap views is no big deal :). > > Warning: subject creep. > > 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. Mike _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
