The main thrust of last week's development was the continuing cleanup of the object construction code (#1249). This remains a high priority, as it's blocking work on boolean operations (#42, #43, #44), which are the next step on the way to making Fornjot actually useful.
I might actually be in the middle of a breakthrough. I've had an idea last week (described here), which could solve most of the issues with the object construction code. I've been prototyping this idea in a local branch, and so far haven't hit any blockers. It's too early to tell, really, but I'm optimistic!
Fornjot is supported by @webtrax-oz, @lthiery, @ahdinosaur, @Yatekii, @martindederer, @hobofan, @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.
Improvements to Fornjot and its documentation that are visible to end users.
- Display more errors in the GUI and display more information about them (#1405)
Improvements to Fornjot components that are relevant to developers building on top of those. These have an indirect effect on end users, through fixed bugs and improved robustness.
- Move validation to separate service (#1403, #1404)
- Continue cleanup of object construction code (#1406, #1407, #1408, #1409)
- Touch up documentation of objects (#1411)
Improvements that are relevant to developers working on Fornjot itself.