title: MVC pattern for GUIs - should model interact with view
body: <p>So I was always taught that the correct cycle is that a view (e.g. a dialog in a gui) only holds display features and no functionality -- it is "dumb" in a sense.</p>
  
  <p>In the view you then have listeners for when a user presses a button, and when that happens, the view communicates to the controller that the button was pressed (via an observer pattern), and then the controller does the appropriate action -- update the GUI and model. So the view never interacts with the model.</p>
  
  <p>But then there are other versions like the one below, in which the view interacts with the model directly.</p>
  
  <p><a href="https://i.stack.imgur.com/a4UfP.gif" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/a4UfP.gif" alt="enter image description here"></a></p>
  
  <p>It's kind of annoying that there are so many different variants across the internet and no one standard thing -- so what really is the correct mvc style for GUI apps???</p>