On Wed, Oct 22, 2008 at 6:37 PM, Chris Idou <[EMAIL PROTECTED]> wrote: > > I think bindings don't merely avoid glue code, it also provides a separation > of concerns.
Agreed. There are a number of benefits but, as with all technologies, those benefits don't always outweigh the detractors. It sounds as though you're doing things that Bindings doesn't handle well (whether due to design or bugs you've encountered). If so, it's time to reconsider their use for this project. :-) > As for Cocoa, the most annoying thing is the source is invisible. Why doesn't > Apple make it visible? Okay, though related, this is a completely different argument. With respect, I'm going to leave that one alone. > I'm in a bit of a bad mood at the moment about Apple's quality of testing. > The Genius playlists on my iPod Classic synched from iTunes *play the wrong > song* when you click on one. iDisk seems to blow up every month or two. I'm > just now recovering from the iPhone 2.0 software debacle, not to mention > Mobile Me. I'm chuckling not out of cruelty but recognition. :-) I understand the sentiment and agree some closer quality control is needed. This is, I believe, why the next 'big cat' will focus on stability and performance more than consumer features. This is, however, veering a bit too far off-topic for this list. Back to my original (on-topic) point: It sounds as though Bindings won't work for your current project. There's nothing wrong with simply not using the mechanism. A little more glue code to do it right and otherwise-hassle-free isn't so bad, is it? -- I.S. _______________________________________________ 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]
