2011/4/9 tog <guillaume.all...@gmail.com> > Dear all, >
Hi Guillaume, > > I had a brief look into pythonocc as my understanding is that it is > made of (please correct me if I am wrong): > - a tool to generate swig .i file out of header files from OCC and > SALOME (GEOM, SMESH) > - some higher (more pythonic) APIs based on the previous ones > - some plugins: FEM, ... > > Is that correct ? > Yes for the firs two points, not for the last one (we did not develop any "plugin"). > > Would that be possible to reuse part of step 1 for other programming > languages: java for example ;-) > I think so. You can notice that pythonocc ( http://code.google.com/p/pythonocc/source/browse/) and occjava ( https://github.com/galleon/jCAE/blob/master/occjava/src/) SWIG files are quite similar. Some adaptations are required from one language to the other, but I do think 95% of the work achieved for the python wrapper can be reused as-is for developping an OCC wrapper for another SWIG supported language. > > Best regards > > Guillaume > > Best Regards, Thomas > -- > PGP KeyID: 2048R/EA31CFC9 subkeys.pgp.net > > _______________________________________________ > Pythonocc-users mailing list > Pythonocc-users@gna.org > https://mail.gna.org/listinfo/pythonocc-users >
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
