On Mon, Jul 28, 2008 at 8:12 PM, I. Savant <[EMAIL PROTECTED]> wrote:
> On Mon, Jul 28, 2008 at 8:01 PM, Hamish Allan <[EMAIL PROTECTED]> wrote: > >> On Mon, Jul 28, 2008 at 5:51 PM, Wickl thomas <[EMAIL PROTECTED]> wrote: >> >>> I know how MVC works with one Model, one View and >>> one Controller but I really don´t understnd how the controllers of different >>> Views communicate with each other. > >> Through the model. The controllers of different views do not generally >> communicate directly. > > That's a pretty general blanket statement that is most certainly > not always the case. > > Consider (as a very basic example) a master/detail view (without the > use of Bindings, especially). Sure there're plenty of reasons I can > think of to have multiple controllers (one for the master list and one > for the detail view), but for every reason I can think of to > separate the controllers in this scenario, I can think of one that > strongly suggests keeping them as one. I agree, so I'm not sure why you're using this as a counter-example to what I said! I also said "generally", with just such an exception being master-detail views complex enough to require separate controllers :) I guess there are plenty of those around, though... Hamish P.S. Trimming attribution when you quote me makes it complicated for people reading Cocoa-dev to follow, as my posts to the list are moderated and do not appear straight away. _______________________________________________ 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]
