The only thing that the controller of the Polling Station Dashboard
suppose to do is to handle events (not manage the llogic of adding or
removing actual parts/panels to the main stage ) this is why this logic is
now mainteined in saparated objects as Settings Visual Updater or
Status Log Visual Updater
for now we have all the main flow vor the voter voting process (without
all the logic for example the logic of fetching from server who else is
voting right now is not existing, etc'...)
in order to reduce coupling between polling station dashboard and all
other elements it produces and uses i have created status log update
interface, which expose the functuality of update the state of status log
panel.
the idea behind this is status log does not have to know polling station
dashboard. all other objects that polling station dashboard will use will
have their own interfaces (for the same reason too).
The meerkat gui is an project consist of scenes every scene is an panel,
now every panel have the loader class which loads it content
and the handler object which handles the visual effects as mouse clicked
etc'...
I have come to conclusoin (after few projects inspection) thatevery fxml
should have his own conroller and its own java class that represents it
and loads it.
Vladimir ELazar Tokarev
Dasha-1