the gui should not know anything about the underlying model, and vice-versa?
Is it the gui, or model, that has state, or is it both
The state of the gui should be updated to reflect the presence of data in the model. If the model knows nothing about the gui, is this something that is done from the model side by calling a method in the adapter class (suggesting the adapter has to implement an interface?), or is there a mechanism for the gui to register itself as an listener to events fired in the model?
Can we use Observer/Observable pattern? (GUI Observer and Model Observable).
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton