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 amJust 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