When developing Java Swing MVC apps, what is a GUI model in opposition to an Application Model? And why is it relevant to MVC?
I read about it the example here (the example does not use a GUI model though). Found more information about it here, here and here. Also in A Swing Architecture Overview in the section GUI-state vs. application-data models.
To cite the author of the example:
Finally, this is how I implement the model / view / controller pattern (MVC) in Java Swing.
The view may read values from the model. The view may not change values in the model.
The controller will (probably) change values in the model.
The controller will (probably) cause the view to repaint.
I don’t have one master controller, usually. I let each controller do its thing.
I do usually have one master model. Sometimes, you need more than one GUI model. This isn’t one of those times. The GUI model is usually separate from the application model, when your GUI is part of a much larger Java application.