You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The architectural pattern might actually be a MVP Supervising Controller, where views do not have any data binding and do not call model logic.
Model is the application, View is the set of Swing dialogs (along with their event handlers) + StartAction and Presenter might be CoreDriver.
Proposal:
Rename application --> model
Rename presentation --> gui (this allow future User Interfaces)
Rename CoreDriver --> CorePresenter
CoreDriver(Presenter) should observe on each dialogs instead of using callback interfaces
Dialogs should implement a View/Observable interface
CoreDriver(Presenter) should implement an Observer interface
Split CoreDriver(Presenter) into some Presenters
Another alternative is with Mediator pattern
The text was updated successfully, but these errors were encountered:
The architectural pattern might actually be a MVP Supervising Controller, where views do not have any data binding and do not call model logic.
Model is the application, View is the set of Swing dialogs (along with their event handlers) + StartAction and Presenter might be CoreDriver.
Proposal:
Another alternative is with Mediator pattern
The text was updated successfully, but these errors were encountered: