I have found the implementation of addObject(type, name=None, objProxy=None, viewProxy=None, attach=False, viewType=None) Here is de c++ code: https://github.com/FreeCAD/FreeCAD/blob/ef16ecafc25f8505ed6e322d5c2be1c1b4a82f4a/src/App/DocumentPyImp.cpp#L261 And here some documentation: https://github.c...

Hello Friends, I am trying to add Link support, The well know pattern to create a FeaturePython is: obj = App.activeDocument().addObject(type, name) # First create the FC PythonFeature MyFeaturePythonProxy(obj) ## Create the proxy and pass the FP MyFeaturePythonViewProvider(obj.ViewObject) # Create ...

Updated version: More ViewProvider stuff.

Chris_G wrote: ↑Mon Mar 25, 2024 9:03 pm I read the PDF. It looks great. I hope I can find time to give it a try.

Thank you Chris_G,
I will be working on this the whole week so i can publish the working API by the end of the week.

I have started a new thread to get some feedback about my current effort to create a comprehensive API and documentation about FeaturePython Objects.

viewtopic.php?t=86414

Hello Friends, For years, I've been developing FeaturePython Objects (FPOs) as internal tools. Over time, I've also built a custom API on top of the existing ones to improve robustness and consistency. I've studied many existing AddOns and Workbenches, noticing that similar problems are solved with ...

I am collecting all these spare pieces of information from the forum, source code, external workbenches, wiki.... and putting all together in one curated document about FPO creation and maintenance including migrations, selection, extension, display modes, serialization. It includes recipes and sour...

Hi Friends, I have been writing a large document of `FeaturePython` recipes and I will contribute it to FreeCAD once I complete my initial goal. My current topic is about extensions: ### Object extensions * App::GeoFeatureGroupExtensionPython * App::GroupExtensionPython * App::LinkBaseExtensionPytho...

What are the tools that would deserve transition to FC in your opinion ? Hi Chris_G, it is hard to decide, I am just learning how to use it, but I think that anything that is battle tested can be merged into upstream FC. Working with curves and surfaces is a fundamental functionality, I Think this ...

This is what I suggest: FC Py_min Py_max 0.19 3.4 3.9 0.20 3.5 3.11 0.21 3.5 3.12 0.22 3.8 3.13 Thank you wmayer. I know there is nothing "officially supported" or "officially unsupported" in FreeCAD but this table is good enough. So based on that, I assume that coding for 3.6 i...