2009/12/14 John Griessen <j...@industromatic.com> > Thomas Paviot wrote: > > > http://opencascade.blogspot.com/2009/02/topology-and-geometry-in-open-cascade.html > > > . Roman definitely knows OCC perfectly and is able to share his > > > knowledge in a very clear manner. > > > > Thanks, I'll read that. > . > . > . > > Hi John, > > > > Welcome to you. Feel free to share your first experiments with us and to > > ask for any help. Questions from new users questions are often > > fundamentals and give a very interesting feedback. > > OK. I have not really gotten started yet before I found freecad, a > pythonic Qt GUI interface to OCC. > > How does your work overlap or complement that? Would it make sense to do > some model creation > with freecad, export with DXF v12 or ??, operate on it with pythonOCC, view > with > http://code.google.com/p/occray/ to get components right, import to a > freecad organized project, > view with freecad as an assembly, continue to make component parts with > pythonOCC, > etc, etc. >
What would make sense is that the scripting engine of freecad uses pythonOCC. > > What are the pathways for import export data > formats that are most useful when IGES is the last thing you want for > fabbing? > If you want to exchange data between 2 OCC based CAD app, I suggest you use the .brep file format. You won't have any data loss. > > The freecad developers want cooperation: They said, "I have contact with > Jelle from > pythonOCC and he is very interested in some kind of > cooperation. But the problem is still the license" > > You both mentioned GPL. Is the version differencesd between v2 and v3 GPL > the problem? > It's not exactly the truth: pythonocc license is only a problem for the freecad maintainer, not mine (pythonOCC is GPLv3, Coin is GPLv2). In august, this summer, I've been in touch with Joachim Zettler, from the freecad project. We had a few discussion and agreed that a cooperation would be a natural thing between two projects that both use OpenCASCADE and Python. I was ok to work with them. Then I heard about the licensing issue. The 15th of october, I sent an email to the freecad manager to start a cooperation. The last words of my message were: """ At last, in my opinion, I think that it's completely crazy that licensing issues can be an obstacle for the collaboration of two or more free and open source softwares (which are both GPL/LGPL). Let's be more pragmatic: if you need to use pythonOCC for your dev, we'll find a solution. Licensing is the last stage to look at, not the first one. """ I'm still wating for an answer, and never heard about the freecad project anymore since that e-mail. I don't have the feeling that a cooperation is something the freecad dev are looking for. And, anyway, the pythonOCC licensing policy cannot be the prerequisite for a discussion. You cannot say 'hey guys, change your license and then we will start to discuss with you'. It cannot work like that, it's not serious. > John Griessen > Best Regards, Thomas
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
