Hi Stéphan, Welcome on this ml, and many thanks for your support.
According to your message, the scope of your business seems to perfectly match our purpose here : contribute a free and open source CAx python library able to be part of a global digital toolchain dedicated to product engineering (and beyond). Well, a lot of things actually need to be coupled to pythonocc in order to achieve such a project, but we definitely defined the path to follow, that could be, in a few words : open source and open standards for open semantics. The best way to start with the Step-By-Step pythonocc learning is to study/copy-paste/modify the examples. They are grouped by categories in the /src/examples/ folder. There is no pdf/html tutorial for pythonocc. Feel free to ask any question here. This message on the ml is the opportunity for me to let registered users know about the current work. First of all, I apologize I was not very active these last months on this ml, mostly because of a huge quantity of work to achieve : I defended my PhD thesis on the 1st of July attended three conference between may and june, and finally moved away from Paris during the summer to enjoy a new way of life in a smaller town. I however never stopped commiting code to the svn repository, but I had no free time to publish long emails or post on the website. I expected the next release to be available on november, but the release workflow is quite long and the mislestone was delayed (untill I have two or three days). Most of the recent work was dedicated to SWIG the wrapper enhancements, bugfixes, new features in all the components of the higher level API (topology, meshing, Parametric modeling, rigid body simulation etc.). Let's say it's only a development activity intended to make pythonocc more robust and agile. In my dreams, I'd like this project to have both an industrial and scientific credibility : - industrial credibility means that the library could be suitable for industrial CAx processes. This still has to be demonstrated ; - scientific credibility means pythonocc is a field for experimenting new ideas, innovative algorithms or services. The first bullet point is clearly related to code/project quality. I'm not a developer, and looking for/fixing memory leaks or encoding issues is not my favorite activity. Furthermore, I have no special skill with that. We already discussed this point many times with Jelle, and we definitely agree! The second bullet point is my core business : I recently joined the Product Design and Innovation Laboratory (Arts et Metiers ParisTech) to go on with my researches on interoperability/product design-manufacturing. I will base the future developments of this researches on pythonocc. The current work is related to the STEP standard, more precisely API/webservices for STEP. A standardized way to interoperate between softwares/systems would make engineers life easier, and pythonocc even more open that it is now. A few other ideas are being tested, but nothing serious enough to be officialy announced as a research project. To conclude this long email, I'd like to finally warn all of you about the following point : the pythonocc project, as it is structured now, is too dependent on Jelle and me. If we both, at the same time, are busy, then the project stops. I'd really like pythonocc to become a more open project, so that its future can be ensured and the quality is improved. The priorities are : - to hunt bugs ; - to write simple but efficient documentation. All the best, Thomas 2010/12/8 Stéphan AUBIN <stephan.au...@thy-engineering.com> > Hi to all > > first of all congratulations for your amazing work so far. > There seem to be much more than what I look for in python-occ !! > > We are in the process of manipulating surfaces to design machines, simulate > then, and finally post process. > > Right now I am looking for a 3D engine to create our own design toolbox : > convenient, open source, full of expertise ! > > Python-occ seems to be the birck I was looking for my wall ! > > Then we'll see about plugging it with meshing tools, and solvers like > Saturn... and then we'd like to re import results on the geoemtrical > entities used for design... > > I could manage 2D splines, but 3D is too much for me ;) > > So I installed your packages on my 64bit kubuntu, and for the moment > everything works ok ! no works great !! > > I am now looking for some basic step by step stuff to re-create points, > curves, splines... and then 3D ! > > Congrats again, and looking forward to hearing from you ! > Stéphan > > _______________________________________________ > 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
