MT tools is mess of Eclipse-RCP based tools (CubeIDE) and tools with hand-made GUI, which
resembles GUI of 90x (CubeMX, CubeProgrammer).
Hand-made GUI applications has a lot of code which can be thrown out after switch to Eclipse RCP.
Anyway, CubeMX is Java GUI application. CubeMX and CubeProgrammer has primitive Java GUI
developed from scratch.
Instead of use a lot of existing functionality of Eclipse RCP, developers had to write own code
and invent a lot of wheels. It increase costs of development and maintanence.
It is not much effort to move CubeMX functionality to Eclipse RCP application.
A lot of code can be thrown away. It will decrease costs.
With Eclipse 4 one can make GUI XML model with visual tool and make several simple adapters
to inject existing Java panels in corresponding model views.
With such approach MX-relative perspectives can be used as standalone application and used with
any IDE. And can be integrated in CubeIDE.
It is very flexible solution. Current CubeMX is old monolithic Java. It is bad primitive architecture.
It would be give CubeIDE competitive advantage over other IDEs. CubeIDE 2.0 has nothing. Only slow speed due to Java.
I switch from Keil to CubeIDE due to integration with Device Configuratyion Tool.
With CubeIDE 2.0 I switch back to Keil.
