What needs to be done in seg.JUCMNav before milestone 3?
Version #
How do we tag our versions #?
When do we start versioning?
Mediator pattern for the UI.
For example: The user click something in the UI, it notify the mediator and the mediator knows what needs to be changed in the ui when the user click this button... This way everything is centralized and not spreaded everywhere in all the event handlers.
Facade (kind of) for changing the model.
Try to abstract the way we can interact with the model (change it). This way if the model changes, we would only need to change the model and not the 100 commands classes that uses the model. Since the model will probably change, it could be a good idea to investigate this.
I'll try to work on that as I integrate the new model in seg.JUCMNav.
Make something that knows if the user can execute a command coming from a given editpolicy depending on a given global context (selection context, tool mode context etc)...