In a previous post I wrote about my experience when converting Scala code to Kotlin. Now, I have some fine Kotlin code but this code still uses JavaFX. I liked JavaFX when it was all shiny and new. That is, when it in version 2.0. But, JavaFX never had - as far as I can tell - any big impact. AWT was a quick UI framework followed by Swing. The latter one is mature, but old. That does not make it bad. It simply misses a lot of new patterns in use today. JavaFX was “the new hope”, but then Oracle cut it out! Now, there is a new player in town from Google: Jet Compose!

While preparing a new release for bcrm, I realized that my pipeline for Travis-CI no longer worked. That pipeline would run a small build script which would include a little chroot environment and wrap it together with the other release files. Unfortunately there is no free plan anymore. One can contact the Travis support team but that was already too much hassle for me. So, I checked Circle-CI. It is similar, but also different. Anyway, they have a free plan that one can directly use. And for my little setup, it would be more than enough.

A quick journey history of my transition from Xorg to Wayland. I waited with this transition as long as possible because two of my favorite tools do not work on Wayland. But now it seems that my favorite dock Plank is broken. And actually, Xorg server is a mess. That’s, why Wayland was introduced.

In a previous post I wrote about my local test setup for bcrm. Because I have a lot of different images in use during testing, I wanted to be able to have version management in place. This would allow me to play around with images, restore them as needed or simply jump back in time during testing.

2021-11-24 Because my “little” project bcrm over the years grew bigger and bigger, I decided about a year ago to implement automated tests.