Thanks to all for the help.
Ickby, I agree.
Some of the occt naming is not very meaningful.
And I don't like the AppDef name neither.
"Approximation" would be way better.
Adding new OCCT classes to FreeCAD python
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
Re: Adding new OCCT classes to FreeCAD python
Yes, you're right. At the moment we have only one of the BRepOffset classes exposed to Python but if we do more of them we should think about making packages to make it more Pythonic.ickby wrote: ↑Thu Nov 28, 2019 10:12 am Just a general question about the naming: Is this occt sheme of naming a good idea? it seems extremely un-freecad-like. It is already pretty bad for the "BRepOffsetAPI_" things already exposed: it is completely unintuitive in the freecad environment to use occt prefixes. I'm all for exposing more functionality, but why not using it in the existing shape API? Or creating just a some logical sounding subpackages in part, likeIMHO the mixing of freecad style and ocp style makes the API much worse.Code: Select all
Part.Approximation.MultiPointConstraint
-
- Posts: 656
- Joined: Tue May 19, 2015 1:11 am
Re: Adding new OCCT classes to FreeCAD python
+1 I think we should make the naming more sane.
Re: Adding new OCCT classes to FreeCAD python
Yes it is.
If I had seen this 2 weeks ago, I would have tried with PythonOCC first, probably.
Thanks
If I had seen this 2 weeks ago, I would have tried with PythonOCC first, probably.
Thanks