Dear PythonOCC users,

I am developing a CAD & Meshing application for finite element simulations 
(computational nano-optics) using PythonOCC. 
I very much enjoy the rapid software development PythonOCC offers - it's fun 
and robust at the same time.

For the software I develop I decided to update my local PythonOCC installation 
to the latest version of the underlying libraries
using the sources from Salome version 6.5.0: 
        - OCCT 6.5.3 (I use oce version 0.10)
        - SMESH version 6.5.0 
        - GEOM version 6.5.0
        - Netgen version 4.9.13 (fully functional netgen plugin with python 
wrapper)
        - Tetgen version 1.4.3 (homebrewn tetgen plugin with python wrappers)

For this purpose I wrote python scripts that basically take the Salome sources 
found in the install wizard and the PythonOCC V0.5 sources
and convert them to an updated PythonOCC Version applying necessary patches 
(e.g. for netgen). Subsequently I  hand-modified SMESH, 
GEOM sources (to create stand-alone versions of them) and SWIG interface files 
(where necessary, well, most of them, actually).

I would like to contribute my modifications to give something back to this 
great open-source library, but I am unsure as to how this could be done.
To this end the updated PythonOCC is running fine on my computer, I can run 
almost all of my test-cases and use netgen and tetgen through PythonOCC.
I am still having some small issues with SMESH though (should be resolved 
within the next days). 

There are some things I would like to discuss (e.g. HashCode functions being 
absent in OCCT Standard_Transient and Standard_Persistent classes,
new dependencies of SMESH to boost threads and VTK). Also as I am developing on 
Mac OS X I did not update the SWIG interface files for win32, so I 
would need some help for this from people developing on Windows.

Thanks for any feedback on this, 
Mark





_______________________________________________
Pythonocc-users mailing list
Pythonocc-users@gna.org
https://mail.gna.org/listinfo/pythonocc-users

Reply via email to