Replies: 2 comments
|
Released version 0.2.1. The main changes are bug fixes in the bundled libui-ng library. The sample code has also been updated. This includes fixes for memory leaks in the examples. I also plan to make one or two more releases later this year. |
|
In the next release, I plan to end support for some old versions of Windows and macOS. Supported platformsI plan to drop support for Windows Vista. For macOS, I plan to require macOS 10.13 or later, or possibly macOS 11 or later. On Linux, I plan to keep GTK3 and not move to GTK4. No API changesThis update will not add new features. I will clean up and update the code while keeping the current API unchanged. I plan to use AI assistants to update legacy code. I think their ability to find bugs will make the transition safer. However, the decision about what to support and what to drop must be made by a human. I am currently putting a lot of passion into my main job, so I will work on this little by little as a personal side activity. The release will probably be later this year. |
Uh oh!
There was an error while loading. Please reload this page.
Yes.
I forked libui-ng and have been using AI agents to fix bugs without changing its API or behavior. I think this strategy can work.
https://github.com/kojix2/libui-ng
One thing to watch out for, though, is that agents tend to make types stricter and remove nullable cases. That needs care, because Ruby has implicit conversion from
niltoNULL.The only new feature I plan to add is a simple API for displaying images.
Yes, I do plan to make a release in 2026.
However, this is being done in my spare time, so it will probably take a while.
All reactions