fornjot

Have a look at https://github.com/hannobraun/fornjot

CADmium is built with the Truck kernel, though it looks like CADmium has no repo activity since June '24. https://github.com/CADmium-Co/CADmium There's also the Fornjot kernel. https://github.com/hannobraun/Fornjot

Related: Fornjot - b-rep CAD kernel in Rust https://github.com/hannobraun/fornjot

Fornjot[0][1] is also really impressive as a CAD kernel. It is written in Rust, and is still a WIP, but I think is turning out nicely. [0]https://www.fornjot.app/ [1]https://github.com/hannobraun/fornjot

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

https://github.com/hannobraun/Fornjot is another option in the space of early stage CAD kernel development.

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.

Here is another programmable CAD project, Fornjot[1], also in Rust. Fornjot, too, is being actively developed. Unfortunately it uses Rust for model description (compile times/learning curve). That said, one could probably easily put a layer of scipting lang in-between. 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/

> How do you solve that in "code CAD"? I mean referring to a geometry that's a result of some previous operations, not one that you manually created. I've written down some preliminary thoughts here: https://github.com/hannobraun/Fornjot/issues/101#issuecommen... And let me emphasize, these are just preliminary thoughts. I can see cases where what I wrote there won't work, and I'm sure there are many more problematic cases I haven't thought of yet. There's still a lot of work to do before any of that even becomes relevant for Fornjot. I'll keep thinking about it in the background, but I don't expect to come up with a meaningful solution before I had a chance to really dive into the topic. CadQuery has its own approach, which I have yet to study in detail: https://cadquery.readthedocs.io/en/latest/selectors.html

Hey, creator of Fornjot here. Support for architecture use cases is currently listed on Fornjot's feature wishlist: https://github.com/hannobraun/Fornjot/discussions/146 As is noted there, I lack any expertise in this field, and it's largely unclear what specifically would be required to support it. Feedback is very welcome! > isn't it kind of similar to OpenSCAD? Yes, OpenSCAD is one example (the most prominent, I think) of the Code-CAD approach. The Fornjot FAQ addresses OpenSCAD: https://www.fornjot.app/faq/ Second question. (Sorry, there isn't a way to link to specific questions in the FAQ yet. I've made a note to add that.)

Hey, author of Fornjot here. > The modeling language for Fornjot is Rust. To me, this seems like an akward language to write models in. I fully agree! Given that Fornjot is written in Rust, starting with Rust as the modeling language was just the most straight-forward option. But Fornjot is architected to be language-agnostic. Right now, it uses a plugin system based on dynamic linking, and you could plug anything in there that can generate C-ABI-compatible structs (the plan is to replace that with a system based on WASM). In addition, I've started splitting Fornjot into self-contained libraries[1]. Once that effort is complete, there will be lots of ways to make Fornjot available to other languages. That said, I think there's merit in having options when using Code-CAD, and Rust is certainly different enough from the typical alternatives

Hey, author of Fornjot here. Could you give a bit more detail on what you mean by that? The plan for Fornjot is to use WebAssembly as the intermediate representation for models: https://github.com/hannobraun/Fornjot/issues/71

Well, no. But it's what we currently have. As adamsvystun notes, I have to start somewhere. Making models more convenient to define is planned (https://github.com/hannobraun/Fornjot/issues/72), support for other modeling languages is on the wishlist (https://github.com/hannobraun/Fornjot/discussions/146).

>> Starting with flat surfaces and straight lines is really ignoring the hard problems and... is this flat surfaces only? Looks to me like curves are passed to the lowest level: https://github.com/hannobraun/Fornjot/blob/main/src/kernel/g...