Separate event handling from GUI
Separate event handling from GUI classes by giving the GUI events to event-classes together with the necessary data to unclutter the whole system and remove some hacks in there (like using doClick of buttons in one class from distance in another class - feels weird).
Blueprint information
- Status:
- Started
- Approver:
- Prunus dulcis
- Priority:
- Essential
- Drafter:
- Prunus dulcis
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Started
- Milestone target:
-
10.12
- Started by
- Prunus dulcis
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Implemented first step: database access now exclusively runs and should run through dbModel.java, which governs and directs all access to the database by the UI.
Next step: Identify events which affect multiple objects (e.g. storing changes to objects) and make sure, that these changes are reflected in other objects, which relate to them. Best done by having a common class listening to these kinds of changes and helping other classes react to those changes by notifying them - partly done via dbModel.java for now but probably should be separated into UIEvents.java [not yet existing].
