The current project is an almost-Python-clone of the freestanding Elmer-Version (in C). It lacks the graphical mesh-part of Elmer and derives that data from the superimposed application. Meshs are created via a call to ElmerGrid.
All windows and settings are created and referenced inside one single object which is the reference to the main-class. Windows are floating and are currently based on PyQt.
If FreeCAD can keep the main-object-reference in its own memorey-context than it should work. The module itself has no main-event-loop and requires something on a higher level as well as PyQt.
FreeCAD has to have the possibility to provide names of objects and the UNV-export has to maintain them. In this way they can be addressed directly in Elmer.
All mesh-manipulation is done in the superimposed application. The elmer-module just provides the settings windows of Elmer.
So imho we would just have to conceive the interface python moduls, for
- Salome (working on that)