The world needs another CAD program.

Weekly Release - 2022-W37

A few weeks ago, I fell down a rabbit hole of kernel cleanups, and I'm starting to climb back up. Doing cleanups can cause me this nagging feeling that I'm indulging myself; that I should find some hack to work around the problem at hand, so I can continue doing what's actually important. But a) stacking hacks on top of each other soon causes more problems than it solves; and b) when those cleanups pay off, that is so sweet.

And last weeks, those cleanups paid off! I managed to simplify lots of kernel code and many issues are now closed (#97, #250, #695, #1020). Some of them very longstanding ones! This not only clears the way for continuing the implementation of the union operation, it will make all work easier going forward.


Fornjot is supported by @webtrax-oz, @lthiery, @Yatekii, @martindederer, @hobofan, @ahdinosaur, @thawkins, @bollian, @rozgo, @reivilibre, and my other awesome sponsors. Thank you!

If you want Fornjot to be sustainable long-term, please consider supporting me too.

End-user improvements

Improvements to Fornjot and its documentation that are visible to end-users.

None this week; busy improving the kernel!

Ecosystem improvements

Improvements to the Fornjot ecosystem that are relevant to developers who are building on top of Fornjot components.




Internal Improvements

Improvements that are relevant to developers working on Fornjot itself.

Issue of the Week

Fornjot is still an early-stage project. Many things don't work very well yet, and that can lead to a rough user experience in some places. One such problem is how the GUI is coupled to the loaded model.

The GUI assumes that a model is always loaded. If a model can't be loaded when you start the Fornjot app, due to some error in the model, the GUI won't show at all. This is extremely confusing!

If you're interested in digging into Fornjot's graphics and UI code, to make an improvement that will have a big impact on Fornjot's usability, check out #1015 - GUI should start immediately, without waiting for model to be loaded.


With all those cleanups finished, I should finally be in a position to address the issue that has been blocking the work on the union operation (#993). I expect that to be pretty easy now, but when I started looking into it on Friday (I only had a few minutes left), making the necessary changes caused a lot of test failures.

Hopefully this is going to be straight-forward. We'll see.