refactoring #112
Description
- game event messages (duplicate code, ...)
- bikeview, bikecontroller, motionstate, bikemodel, bikeinputstate (long methods, unclear dependencies, hard to extend, ...)
- maybe an event based approach for model/view communication would be an improvement
- no methods in controller that directly call model XOR view methods, public getter for model/view
- can the multiplayer integration be reworked - get rid of all the if multiplayer statements (traits?!)