Re: [Pythonocc-users] Updates on PythonOCC

2012-08-20 Thread jelle feringa
> > Gosh, I should have checked the git repositories before diving into > modifying the PythonOCC-0.5 SWIG interfaces. Well, at least > I learned a lot during that week ;-). > Your a very fast learner... > - I think the gccxml issue I am having on my Mac really is related to my > gccxml version

Re: [Pythonocc-users] Updates on PythonOCC

2012-08-20 Thread Mark Blome
Hi Jelle and Thomas, thanks for pointing me to the OCEworkflow document. My SMESH / GEOM modifications are following along the line of what Fotis Soutis did (Corba stuff removed), with working NETGEN and Tetgen mesher Plugins. I am going to contact Fotis Soutis about my modifications to see

Re: [Pythonocc-users] Updates on PythonOCC

2012-08-17 Thread Thomas Paviot
2012/8/17 Mark Blome > > Hi Thomas, hi Jelle, > Hi Mark, > > thanks for your comments and hints. > > About the GEOM and SMESH modules: I started all over again creating > stand-alone versions of SMESH and GEOM from the Salome V6.5.0 sources cause > I > judged that updating these projects file

Re: [Pythonocc-users] Updates on PythonOCC

2012-08-17 Thread jelle feringa
> > There were issues with hashes before the overloading of the python > __hash__ method with the HashCode OCCT method (which is now a static > function). This has been solved some time ago. > There's already a unittest for hash (see TestList here > https://github.com/tpaviot/pythonocc/blob/master/

Re: [Pythonocc-users] Updates on PythonOCC

2012-08-17 Thread Thomas Paviot
2012/8/17 jelle feringa > I think (but I'm not sure), that removing the __hash__ method introduces >> some regression. >> > > A solid test for __hash__ is critical. One needs to be able to compare > TopoDS_* instances for example, and I recall having some issues in the past > with the hashes. > A

Re: [Pythonocc-users] Updates on PythonOCC

2012-08-17 Thread jelle feringa
> > I think (but I'm not sure), that removing the __hash__ method introduces > some regression. > A solid test for __hash__ is critical. One needs to be able to compare TopoDS_* instances for example, and I recall having some issues in the past with the hashes. Anyway, comparing TopoDS_* can be so

Re: [Pythonocc-users] Updates on PythonOCC

2012-08-17 Thread jelle feringa
hi Mark, > thanks for your comments and hints. > Its exciting to have you onboard =) > About the GEOM and SMESH modules: I started all over again creating > stand-alone versions of SMESH and GEOM from the Salome V6.5.0 sources cause > I > judged that updating these projects file by file would

Re: [Pythonocc-users] Updates on PythonOCC

2012-08-17 Thread Mark Blome
Hi Thomas, hi Jelle, thanks for your comments and hints. About the GEOM and SMESH modules: I started all over again creating stand-alone versions of SMESH and GEOM from the Salome V6.5.0 sources cause I judged that updating these projects file by file would have been too cumbersome. Well, pr

Re: [Pythonocc-users] Updates on PythonOCC

2012-08-16 Thread Thomas Paviot
2012/8/15 Mark Blome > > Hi Jelle, > Hi Mark, Thank you for your post. It's not that usual that people here contribute to the low level SWIG layer. > thanks for your quick reply. At our institute (Zuse Institute Berlin, > www.zib.de) we have developed a FEM solver specialized for nano-optics,

Re: [Pythonocc-users] Updates on PythonOCC

2012-08-15 Thread Mark Blome
Hi Jelle, thanks for your quick reply. At our institute (Zuse Institute Berlin, www.zib.de) we have developed a FEM solver specialized for nano-optics, which is being commercialized by the startup-company JCMWave (www.jcmwave.com). In my research I am simulating functional nano-structures (e

Re: [Pythonocc-users] Updates on PythonOCC

2012-08-15 Thread jelle feringa
Dear Mark, I am developing a CAD & Meshing application for finite element simulations > (computational nano-optics) using PythonOCC. > Interesting! I take it that your developing a custom solver? Cool to see PythonOCC in such a sophisticated project, exciting. > I very much enjoy the rapid soft