Re: The problem with bindings
Re: The problem with bindings
- Subject: Re: The problem with bindings
- From: m <email@hidden>
- Date: Thu, 29 Jul 2004 14:04:10 -0700
On Jul 29, 2004, at 11:13 AM, Drew McCormack wrote:
I usually find that if things go well with bindings, I really can save
that '300 lines of code' that everyone talks about, but when things go
wrong, I can spend hours tracking down the problems, effectively
negating any benefit I may have gained. Furthermore, easy things, like
populating a table view with values, are well documented, and can be
achieved very efficiently with bindings. But try to go a bit deeper,
and do something not in the manual, and it requires a considerable
commitment.
Basically, it comes down to this: bindings are very hard to debug. You
can't set a breakpoint, so you are left guessing at what is happening
based on an obscure error message from an exception thrown deep in the
Cocoa frameworks. Anyone else have this problem?
Yes. But I don't think it's a problem with bindings in principle; it's
a UI problem. The current UI for setting up and checking bindings makes
it hard to check them for correctness. I think a better UI for
displaying bindings would go a long way to making problems easier to
find. (This goes for IB generally as well.)
Without thinking about too deeply, I'm thinking that something like a
text description at one extreme, or something more visual at the other
(how about both!) would be better than the current design.
_murat
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.