I totally agree. Making it dynamic is necessary, considering that odrive V4.0 would be for single motor.
My python development skills would be put to test on this one. But I am up for it.
Having a tree view is a really good idea, and being able to customize your windows is really an ultimate goal. As I encountered these needs already while trying to tune motors, needing to switch between config tabs and graphs.
So, in QT there are treeview and MDI area widgets that would allow to have custom windows to be added and moved by user. I will have to play around with them to learn more and understand it’s limitation. But I suppose I can start working on these things and slowly build a new app.