cadquery VS fornjot

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

I agree 100%.

Truck[1] and Fornjot[2] are recent attempts in the Rust space, both are WIP.

But both seem to be going the traditional way. I.e. B-Rep that can be converted to (trimmed) NURBS.

I think if one wanted to incorporate the last 50 years of computer science, particularly computer graphics, one needed to broaden the feature set considerably.

You need support for precision subdivision surface modeling with variable radius creases (either via reverse subdivision where you make sure the limit surface pass through given constraints or using an interpolating subivision scheme that but has the same perks as e.g. Catmull-Clark).

Then you need to have SDF modeling ofc.

Possibly point based representations. If only as inputs.

And traditional B-Rep.

Finally, the kernel should be able to go back and forth lossless between these representations wherever possible.

And everything must be node-based, like e.g. Houdini. Completely non-destructive.

[1] https://github.com/ricosjp/truck

[2] https://github.com/hannobraun/fornjot

Fornjot seems like this question was tailored for it: https://www.fornjot.app/

I think some interesting developments are made in that sector in the form of https://github.com/hannobraun/Fornjot and https://github.com/ricosjp/truck. Let's see whether one of those will actually get anywhere near a usable level. Fornjot in particular is shaping up really well.

E.g. Rhai[2] or Lua or whatever.

And I guess if their tech is solid enough, someone will do that eventually and open a PR or fork the project. They do not use an existing geomtry kernel but do everything from scratch which makes this a very interesting endeavour.

There also seems to be a goal overlap between Fornjot and DieselCAD

[1] https://github.com/hannobraun/Fornjot

[2] https://rhai.rs/

I have heard of yet another in-development CAD software like OpenSCAD or CADQuery, called Fornjot. Still, these are not ideal.

I'm not opposed to someone else adopting that code and creating that crate though! (Fair warning though, Fornjot might not end up using that crate. We might still go with another approach eventually.)

also it's to early to be off much use to you, but have you heard of https://www.fornjot.app/ ? it's a very in development cad kernel that is also aiming for integration into multiple host languages.

Yes! The website and repository README have a screenshot, and there are screenshots for each model in the models/ directory.

I'm kind of interested in this issue because it's what I immediately wanted when I ran fj-app.