On Oct 5, 2008, at 08:01, Michael Ash wrote:
Pardon me? Cocoa did perfectly fine for over a decade having this be
the *only* way to do things. Bindings only came about in 10.3,
practically yesterday. And some of us still aren't too convinced about
their ultimate utility either. In any case, directly manipulating the
user interface, while perhaps not as shiny and new as bindings, is
*definitely* "Cocoa-like".
Beg pardon, I wasn't trying to be dogmatic or controversial, and the
"rather" in "rather un-Cocoa-like" was an essential qualifier.
Let me make one attempt at rephrasing my point, then I'll shut up.
One of the great things about Cocoa is that it frequently allows us to
avoid writing user-interface glue code (like getting a value out of
one text field and putting a calculated result in a different text
field, as in the OP's example). There's nothing wrong with user-
interface glue code other than that it's often quite tedious to write
in any quantity (and even more so to rewrite when the user interface
changes). Although bindings are not the simplest Cocoa technology and
have their frustrating aspects, the combination of bindings and a MVC
design pattern promotes code brevity through reusability via
frameworks, and those are very Cocoa-like advantages.
_______________________________________________
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 [EMAIL PROTECTED]
