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 are the pathways for import export data formats that are most useful when IGES is the last thing you want for fabbing? 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? John Griessen _______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
