truck

Looks like this uses the Truck modeling kernel: https://github.com/ricosjp/truck Interestingly, ttouch created browser-based CAD tool CADmium a few years ago based on Truck. Then, a few months ago, they created another one (CADara) based on OpenCASCADE: https://news.ycombinator.com/item?id=48070083. Truck seems cool, but creating a b-rep kernel is a phenomenal amount of work. Given that, I'm curious how quickly SolidCraft will mature.

There is Truck - "Rust CAD Kernel" (https://github.com/ricosjp/truck) being developed by a Japanese CAE company, but not sure how full featured it is currently.

Truck (Rust CAD Kernel) - https://github.com/ricosjp/truck

Also Truck https://github.com/ricosjp/truck

This looks super nice! That is kind of the interface I wish FreeCAD could have. I am more the type of person who likes to use a python interface to create parametric models, but this is really cool! Anyone knows what is the status of Truck [1] in this regard. Are they going to implement an open-source CAD program with their CAD-kernel? That also looks like a promising project. [1] https://github.com/ricosjp/truck

To add, there's a new CAD kernal that is in slow development called truck [1]. Is is written in Rust and you script/make models in Rust. It doesn't have any geometric constraints though. There was a very short attempt at starting to make a GUI for truck [2] but development has seemed to have halted. There was discussion and hype about this here a couple months ago [3]. [1]: https://github.com/ricosjp/truck [2]: https://github.com/CADmium-Co/CADmium [3]: https://news.ycombinator.com/item?id=40428827

I like how the Truck kernel's github [1] says that their choice to use Rust and WGPU is due to "Trendy Tools" being a core principle. I'm super excited about this. [1] https://github.com/ricosjp/truck

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 representation

There is no renderer mixed into anything. I would suggest you look at the actual crates. There is the truck-rendimpl crate and that is not relied on by any other truck-* crate that does actual B-Rep stuff. I also think you confuse the book/tutorial with the documentation on docs.rs. My impression is that the former is very much a work in progress. I never looked at it until now. The latter (and the examples in the resp. crates) is what you want to check out to see the kernel being used. E.g. https://github.com/ricosjp/truck/blob/master/truck-modeling/... The main README has links to all the documentation of the crates.

As a small example of the complexity see this issue: https://github.com/ricosjp/truck/issues/5 The last comment in that thread is me pointing to a related discussion about a bug in solvespace. Someone tried to cut a cone shape out of a flat surface and the boolean failed because of the degenerate normal at the vertex of the cone. It was days of discussion to select which few lines of code would be best to fix it. BTW the solvespace NURBS kernel is under 10kloc and is fairly simple for what it's capable of. The bugs can be crazy to track down and require a deep understanding of what's going on in the code and geometry, but oh so rewarding to fix if that's your kind of puzzle.

There are two Rust projects working on parametric kernels I'm aware of. The first one, Truck[1] seems to have a company behind it, Ricos Ltd, that look like they to know what they're doing[2]. The tweet shows their product using functionality from Truck (the frontend is not OSS AFAIK). Fornjot is an ambitious project IMHO. Their kernel is in a separate crate[3]. As for OSS code that could be a good base to either use (or port to something like Rust) for someone to write their own kernel is Ayam [4], the oldest OSS 3D NURBS modeler that is still being developed. [1] https://github.com/ricosjp/truck [2] https://twitter.com/RICOS_ltd/status/1550390552482693120 [3] https://crates.io/crates/fj-kernel [4] https://ayam.sourceforge.net/

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.

I will definitely keep reading and learning, as well as gaining practical implementation experience. We'll have to see how that goes, and what the solution will end up being. > Another direction you could take is to define just the API, and use the opencascade kernel (like FreeCAD) until the rest of your code is ready. A CAD kernel is the central dependency for any CAD program, and I feel that it would be wrong to just use one and accept its limitations. I need to be able to take ownership, to work on it directly. OpenCASCADE is a huge pile of C++ code, which is the opposite of all that. (Not saying it's wrong to use in general, just that I'm the wrong guy to work on a huge pile of C++ code.) I've considered using Truck[1], but decided not to do that for now. I really want to see what I can come up with. If that doesn't work out, at least