[x] Add method to return ElevatorMonitor's properties as a String array of size 6
return in order: CurrentFloor, ServiceDirection, MovementState, MovementDirection, DoorState, Fault
Used when comparing ElevatorView's array of TextPanes to the ElevatorMonitor's properties
Testing of Presenter updating ElevatorView
21
[x] Create PresenterTest: After Presenter receives an ElevatorMonitor, ensure that the text of each of the ElevatorView's statusPanes matches that of the elevatorMonitor it was just passed
[ ] Ensure it still works with elevator movement
Making Presenter Runnable (Optional)
To make Model not have to wait for View to update:
[ ] Give Presenter a queue for ElevatorMonitors
[ ] Model pushes new state changes (ElevatorMonitors) to Presenter's queue
[ ] Presenter could be checking the queue to see if any new ElevatorMonitors have arrived, and update the corresponding
To do this, Presenter could be Runnable
Would be started as a Thread from within the Model's main method
This is the Model View Presenter design pattern that will probably be best for our project:
For the bare minimum Iteration requirements, the Presenter does not need to accept input from the View or push anything to the Model.
Initial Integration of Model and Presenter
219
Updating ElevatorMonitor
207
Testing of Presenter updating ElevatorView
21
Making Presenter Runnable (Optional)