I was able to spend most of last week heads-down working on the union operation (#42). The bulk of this work related to the various intersection tests that the union algorithm requires, but it also resulted in some cleanups to kernel APIs.
@Michael-F-Bryan has been busy too, with the
--version argument he added to
fj-app being merged last week.
Fornjot is supported by @webtrax-oz, @lthiery, @Yatekii, @martindederer, @hobofan, @ahdinosaur, @thawkins, @bollian, @rozgo, and my other awesome sponsors. Thank you!
If you want Fornjot to be stable and sustainable long-term, please consider supporting me too.
Improvements to Fornjot and its documentation that are visible to end-users.
Improvements to the Fornjot ecosystem that are relevant to developers who are building on top of Fornjot components.
- Improve wording in doc comment (#880)
- Clean up API of object types (#881, #891)
- Implement curve/edge intersection (#884, #888, #889)
- Clean up surface/surface intersection (#890)
Improvements that are relevant to developers working on Fornjot itself.
Issue of the Week
The Fornjot repository has a continuous deployment workflow that builds binaries for the Fornjot app every time new changes are pushed to the
main branch. There is currently a bug that mislabels those binaries as official release binaries, which results in the wrong output being displayed for them, if the user calls the app with the
If you're looking for a way to get involved with Fornjot and are interested in CI/CD and GitHub Actions, why not take a look at #883 - All binaries built by CD workflow are labeled as release binaries?
I understand the union algorithm from a high-level (and have been for a while now, I think), but working out and implementing all the details is still a challenge. I expect that this work will continue for a while.