Yes... Often it makes me want to recode it again. I'd really like to redo it in C++ too, the speed gain would be incredible, if we compare with the DXF. But that would mean have the IfcOpenShell source code in FreeCAD, which is not practical at all (it evolves too much and too fast), or having it available as a shared library on all platforms, which isn't there yet either. Better to stick with the python importer a bit more. Plus, it allows for much better experimentation.bernd wrote:Good idea. We will not catch all the different ifc dialekts, but we will catch if something is broken at all. Which could happen. importIFC is a huge code monster ...
Maybe that would actually be the response to the Arch/BIM naming issue too: Some day, we'll start a BIM workbench which will be a true hybrid C++/python workbench and which will use all the experience we gained with Arch...
