Beta of SVG inflate path at https://preview.c9users.io/chilipeppr/widget-svg2gcode/widget.html
+Peter van der Walt this one’s for you. @Todd_Fleming your ClipperLib.Clipper.SimplifyPolygons was amazing to use. Thank you.
Well, it helped that I spent so much time getting to know Clipper in the Eagle BRD Import widget. What I never used though was the SimplifyPolygons method because it was never necessary there. I also borrowed the drawClipperPaths from the Eagle widget.
Yeah, I agree that possibly the CAM needs to get moved to a more generic CAM widget rather than trying to shove CAM into each widget. I’m sitting here thinking of adding pocket operations because you just keep deflating the path until it disappears and presto. This could be done at a later layer though like a CAM widget, so why do it in the SVG widget.
Concurred. Or maybe CAM can be a separate tab that gets injected into all your existing widgets - that way it won’t disrupt the workflow. I believe that all these widgets should follow this format: they take their file type as input and output ready gcode.
The CAM tab could take a Three Object/ Mesh/ Geometry and provide a UI for setting up the kerf, inner vs outer profile, pocket, etc. It’s all related to design and machine, not filetype, so that’s why I think the CAM UI does not need to be widget specific.
Cloud 9 didn’t really exist when cp was built. Cp was ahead of its time.