cadquery VS opencascade-emscripten-port

I was thinking about cadQuery or DrawSVG. But maybe you have a better idea ? I'm beginner in python (started on november ...)

Last few months, I've made over 20 3D printed panels using the CadQuery Python library. Its syntax is pretty complex, so every time I wanted to make a panel, I'd just copy-paste bits and pieces from my previous panels. In the process, I learned what work and what doesn't, and I thought it was time to polish up this system to share it with others.

>Python for CAD

You might be interested in CadQuery:

https://github.com/CadQuery/cadquery

Spicy! I'm also a solidworks user but I've been playing around with cadquery recently, that installed and performs pretty nicely on Linux for me. Haven't really pushed it though.

I am currently developing a pipeline for creating STL files, slice them and create a print job based on it. My setup at the moment is an Ultimaker S5, which offers a simple REST-API, for example starting a job with a G-Code or UFP file. I am using the cadQuery library for creating parametrized 3d shapes and export them as a STL file. I want to use the CuraEngine CLI interface (Backend for Cura) for slicing or their library libArcus (python bindings) but there is literally no documentation or any kind of examples, except the source code. There is also the prucaSlicer, which also offers a CLI interface for creating G-Code, but no support for the Ultimaker S5.

Not C but maybe cadquery? https://cadquery.readthedocs.io

CadQuery would be a closer alternative to OpenSCAD. Not sure if it’s available on OpenBSD.

Check out https://github.com/CadQuery/cadquery

There is an OpenCascade version compiled down to wasm [1] that we're currently using embedded in our own app. Rendering to WebGL is relatively straight-forward and the system as a whole works well. Gives me a lot of power when designing mechanical systems and running simulations on the resulting models. Perf of the CAD kernel on the web is not great, but 'just good enough'.

Troubleshooting issues is tricky though. If something doesn't work debugging is nearly impossible and the (C++) docs are very challenging.

OpenCascade is very powerful, but the ergonomics of the API aren't great. Writing a simple FP-style immutable wrapper around it has proven very fruitful and we can now describe relatively complicated models with a bare minimum of TypeScript code. Lot's of fun!

[1] https://github.com/gabrielcuvillier/opencascade-emscripten-p...