On Jul 3, 2009, at 00:25 AM, Jeff Johnson wrote:
This is why I tell people nibs are no good.
Also bindings. ;-)
Bindings are definitely the worst-case scenario for nibs. They tend to
proliferate, and they are burrowed deep in the IB UI making them hard
to miss if you don't check every wi
On Jul 2, 2009, at 4:25 PM, Andy Lee wrote:
On Thursday, July 02, 2009, at 11:39AM, "Michael Ash" > wrote:
On Wed, Jul 1, 2009 at 11:18 PM, Marco S Hyman wrote:
[...]
That leads directly to something I've been thinking about as one
new to
cocoa:
how do you document your bindings? Any prefe
On Thu, Jul 2, 2009 at 5:25 PM, Andy Lee wrote:
> On Thursday, July 02, 2009, at 11:39AM, "Michael Ash"
> wrote:
>>On Wed, Jul 1, 2009 at 11:18 PM, Marco S Hyman wrote:
> [...]
>>> That leads directly to something I've been thinking about as one new to
>>> cocoa:
>>> how do you document your bind
On Thu, Jul 2, 2009 at 2:25 PM, Andy Lee wrote:
> 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
On Thursday, July 02, 2009, at 11:39AM, "Michael Ash"
wrote:
>On Wed, Jul 1, 2009 at 11:18 PM, Marco S Hyman 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 st
