> I'm trying to avoid "who said what" discussions on this list these days ;)
Though I see your emoticon, I don't really understand this statement - if there's confusion about a post, quoting is the easiest way to clear it up, which is why it's a regular practice in e-mail / mailing lists. > I merely thought you were recommending the use of a single > controller for a master-detail view, in which case the point about one > controller needing to access the selection of another would be moot. No, not necessarily - I don't have enough information about the OP's project. I was merely mentioning that your assertion that views should communicate with controllers via the model layer (which is what your original message seemed to imply) is incorrect as stated because it implies this is *always* (or even "usually") the case. Further, I was suggesting that your blanket statement that controllers shouldn't communicate with one-another (generally or not) is incorrect (or at least inaccurate) because such an approach is a matter of design, whether because of your 'tastes' or functional requirements. > Your design decisions may vary. Indeed. A lack of concrete specifications in the OP's project or our examples so far makes design debates pointless in this discussion. I just want to make sure that if we make assertions, we do so without ambiguity. Anything less may make someone else's life a whole lot harder than it needs to be. No harm was intended on my part. -- I.S. _______________________________________________ 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]
