Hi Yannick and Yzokras,
Yes you are right, pycharm is doing some static analysis of the classes and as orekit wrapper is not python files it does not find it. Dynamic completion works, as in jupyter notebooks, but also in the pycharm python shell. The interactive debug in pycharm is really useful, and it has completion. I do not know if there is any possibilities or API for class discovery for compiled classes. Would be nice.
And regarding docstrings, yes they are not populated today. I was digging a bit in this some time ago, and it should probably be not too hard to make them a bit more descriptive like which parameters a method has. The really nice thing to have would be the proper docstrings, but this would require much more parsing and messing about as the docstring is not saved in the jar file and needs to be extracted somehow.
Both these things are generated by the JCC tool, so that’s where one need to start to improve things, help is welcome. It has a bit steep curve to enter as it is code generation in c++ to wrap java JNI calls, and then the c interface to Python.
Regards
/Petrus