openscad VS fornjot

A measuring tool has been worked on, here is the github issue: https://github.com/openscad/openscad/issues/3638

There is a lot of work going on for adding Python. Guenther pushed a PR with code from PythonSCAD . It is under technical review - design, api and code. https://github.com/openscad/openscad/issues/4880 this is the tracking bug.

Please let me know if you have any comments about this, I want to make sure that this will not break anyone's workflow. Feel free to reply here or in the github issue https://github.com/openscad/openscad/issues/4870

Short edges (e.g. due to very high $fn) can cause bug in the triangulator, there is a fix for this but is not ready for merging. (https://github.com/openscad/openscad/issues/4679)

LibreCAD, OpenSCAD (more script based and more for solids), FreeCAD.

Found this, not sure if it's useful: https://github.com/openscad/openscad/blob/ac1d89f2381f8d4b6eaf0492c8ba1666d7d7f393/sounds/complete.wav

Things like this should be reported at https://github.com/openscad/openscad/issues

1.) Check out the latest github source and follow the build directions: https://github.com/openscad/openscad

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.