I need to make the design decision regarding how the model and the views will be kept in sync with each other. Namely:
- I can use key-value coding and observing (KVC and KVO) - I can use bindings (not sure if it's really different from the KVC/KVO) - I can write the "glue code" myself The concept of KVC/KVO is new to me. I have been looking at the Sketch sample (a kind of application I am building myself too), which is based on KVC/KVO, and I have found that the use of KVC/KVO makes the program very unreadable and clumsy (like C++ COM code in Windows, you know), because of the generic messages and hidden dependencies. I suspect that it could be way easier, when a property's value changes, to just explicitly send a concise and clearly named message to the subscribed objects, than try to fit into the over-generalized model of KVC/KVO for the sake of skipping a few lines of code. And I still have to subscribe objects to objects with KVC/KVO, don't I? Does anyone actually use KVC/KVO? What is your experience? Any pros/cons, opinions and best practices would be appreciated. Thanks _______________________________________________ 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]
