• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: MVC Design Variations?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MVC Design Variations?


  • Subject: Re: MVC Design Variations?
  • From: Creed Erickson <email@hidden>
  • Date: Wed, 16 Jul 2003 15:00:11 -0700

On Wednesday, July 16, 2003, at 03:30 AM, Ashley Aitken wrote:

However, when the model data is large (or more particularly the display of that model data is selective, eg a page of a word processing document) it is not sensible for the controller to pass all the data back and forth between the view and model. In this case, it is more appropriate for the view to query the model for what it needs to update its display etc.


One of the problems I see with this is that views are then forced to know about each other and/or the state of the model. Consider two separate views on the model, e.g. a split editing window. If the upper view changes, only a mediating object -- a controller -- will be able to determine how many and which views need updated.

---
Creed Erickson <email@hidden>
"Not a shred of evidence exists in favor of the idea that life is serious."
- Brendan Gill
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
  • Prev by Date: Hmmmm. Duplicate classes
  • Next by Date: Re: Version number of apps
  • Previous by thread: MVC Design Variations?
  • Next by thread: Re: MVC Design Variations?
  • Index(es):
    • Date
    • Thread