vocx wrote: ↑Thu Aug 06, 2020 2:45 pm
Moreover, Werner mentioned that some functions of OpenSCAD are used by the Mesh Workbench because they are more robust (boolean operations maybe?); so to really move the OpenSCAD workbench outside the main repository, some of these issues need to be investigated in order to keep everything running without significant downtime.
Yes, it uses OpenSCAD as back-end for boolean operations as the implemented algorithms in the Mesh module are quite unstable. So, I prefer to leave OpenSCAD in master and move it to the new layout.
This could also serve as a template for people who use their own Python workbench to follow the new layout.
vocx wrote: ↑Thu Aug 06, 2020 2:45 pm
Moreover, Werner mentioned that some functions of OpenSCAD are used by the Mesh Workbench because they are more robust (boolean operations maybe?); so to really move the OpenSCAD workbench outside the main repository, some of these issues need to be investigated in order to keep everything running without significant downtime.
Yes, it uses OpenSCAD as back-end for boolean operations as the implemented algorithms in the Mesh module are quite unstable. So, I prefer to leave OpenSCAD in master and move it to the new layout.
This could also serve as a template for people who use their own Python workbench to follow the new layout.
@yorik Well the version I created in my Github is in the new layout I believe, would you like me to change it back from private to public?
The way I have been testing it, was on a test version of FreeCAD, deleting directory Mod/OpenSCAD.
Then from a command line and current directory .FreeCAD doing a git clone of the repro.
