At the very least, we need fast versions of the following 2D geometric boolean operations supported. It'll make generating fill and shell operations a lot easier, and enable more complex inter-slice operations for things like bridge-detection, adding support structures, etc. I'm borrowing the operation names used in the EDA/IC Design world for these sorts of functions:
geomAnd: Equivalent to the "intersection" operation in OpenSCAD (see http://en.wikibooks.org/wiki/OpenSCAD_User_Manual/The_OpenSCAD_Language#intersection)
geomOr: Equivalent to the "union" operation in OpenSCAD (see http://en.wikibooks.org/wiki/OpenSCAD_User_Manual/The_OpenSCAD_Language#union)
geomAndNot: Equivalent to the "difference" operation in OpenSCAD (see http://en.wikibooks.org/wiki/OpenSCAD_User_Manual/The_OpenSCAD_Language#difference)
At the very least, we need fast versions of the following 2D geometric boolean operations supported. It'll make generating fill and shell operations a lot easier, and enable more complex inter-slice operations for things like bridge-detection, adding support structures, etc. I'm borrowing the operation names used in the EDA/IC Design world for these sorts of functions:
geomAnd: Equivalent to the "intersection" operation in OpenSCAD (see http://en.wikibooks.org/wiki/OpenSCAD_User_Manual/The_OpenSCAD_Language#intersection)
geomOr: Equivalent to the "union" operation in OpenSCAD (see http://en.wikibooks.org/wiki/OpenSCAD_User_Manual/The_OpenSCAD_Language#union)
geomAndNot: Equivalent to the "difference" operation in OpenSCAD (see http://en.wikibooks.org/wiki/OpenSCAD_User_Manual/The_OpenSCAD_Language#difference)