I'm having a slight dilemma in deciding which I should use, notifications or bindings. Here is the background:
I have a bunch of C++ code that uses something akin to delegates; you derive from a base class, pass that into an instance of a server class, and the server class calls the delegate at appropriate times. I wanted to cleanly encapsulate all of this in Objective-C, so that the rest of my code can be pure Objective-C, so wrote wrappers for each base class. Now, I pass the internally wrapped C++ instance to the server, while the rest of my code will hook up to Objective-C wrapper. My dilemma is how to do this hookup; I can use either notifications or bindings, but I can't decide which is better in this situation. Bindings seem to be simpler to use, but reading about them suggests that you are expected to use the MVC design pattern, and I'm not doing MVC here. Notifications are used anywhere you want, but require more (and more careful) work to get right. So, are bindings considered general purpose, or should they really be reserved for MVC situations (even though they can work anywhere)? Thanks, Cem Karan
_______________________________________________ Cocoa-dev mailing list ([email protected]) 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]
