Adding new OCCT classes to FreeCAD python

[Chris_G]

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.

[wmayer]

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, like

Code: Select all

Part.Approximation.MultiPointConstraint

IMHO the mixing of freecad style and ocp style makes the API much worse.

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.

[Chris_G]

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.

So, I suppose I should take Geom2d as model for Approximation.

[ezzieyguywuf]

+1 I think we should make the naming more sane.

[mfasano]

Is this relavent to this thread?

https://forum.freecadweb.org/viewtopic.php?f=8&t=41399

[Chris_G]

Yes it is.
If I had seen this 2 weeks ago, I would have tried with PythonOCC first, probably.
Thanks