Overall Modules and Classes Design

[fabienrohrer]

Here is a new iteration on the module and class design:
https://github.com/omichel/robot-designer/wiki/Design

Since the last version and according the Olivier:

• The view3D and the partView have been separated into 2 modules.
• Classes and modules are listed in a more exhaustive way.
• A top module has been introduced.

Moreover:

• I renamed "View3D" to "RobotView"
• I dropped the UIControl classes which could be implicitly added the main class of each module (RobotView, etc.)
• I added a PartBrowser module.
• I didn't show all the interactions with the data blocks (DOM, ThreeJS), because they are implicit in most of the cases.

This document needs to be validated and improved with the implementation.

[omichel]

Thank you. It looks much better to me like that.
Two minor comments:

1. It seems the PartMediator class is duplicated.
2. PartView should link to Part Controller, not RobotController.

[fabienrohrer]

1. It seems the PartMediator class is duplicated.

This is done on purpose. For example, when a color is changed on a part, it should be dealt in the 3D view and in the part view, so both of them should listen the part model,

2. PartView should link to Part Controller, not RobotController.

OK.

[omichel]

So, do we have two "PartMediator" classes or only one? If only one, in which module is it stored?

[fabienrohrer]

I planned 2 classes. There is a name clash to solve.