I'd like someone to move Solvespace to GTK4. It's platform specific code is all in one file (about 1K LoC). Uses a bare minimum of UI toolkit.

https://github.com/solvespace/solvespace/issues/853

You know, in case someone wants to get their feet wet in either GTK4 or Solvespace ;-)

I haven't tried but I imagine the LLM stuff might actually work well for these super-menial coding tasks of porting between related APIs compared to other coding tasks. There are usually a lot of "how do I port this snippet of code from version x.y to (x+1).y" on Q&A sites, forums, mailing lists etc. which is probably in the training data.

I love the solvespace ui, yes it's weird and different but it works well and is internally consistent, except when a gtk dialog jumps out at you, that is jarring and breaks the flow.

I guess my point is. the obviously gtk bits of solvespace are it's worst parts, if I were a better ui programmer one of my goals would be to get rid of all the modal windows in solvespace, make them in line and operate like the rest of the native widgets.

Gtk 3.0 was released in 2011, the last 3.x release was supposed to be in 2016, but later 3.24 came along. 3.24 is now up to the 29th point release with 3.24.29. Kind of an OpenSSL 0.9esque version number...

Meanwhile Gtk 2.0 from 2002 was apparently the first GTK+ version with the GObject system. I'm not sure if distros can stop shipping Gtk 2 any time soon, as it's quite commonly used in commercial software and not always vendored (since vendoring Gtk can be tricky).

> 3.24 is now up to the 29th point release with 3.24.29. Kind of an OpenSSL 0.9esque version number...

It's just semver. Gtk 3 isn't receiving new features, so it's frozen at 3.24. It still gets bug/security fixes, so 3.24.x patch releases abound (and it seems the current version is actually 3.24.37). Similar situation with Gtk2, current version is 2.24.33.

They slightly cheated and added some new features to 3.24.x to ease the transition and integrate into newer tech better like sandboxing.

> Meanwhile Gtk 2.0 from 2002 was apparently the first GTK+ version with the GObject system

Technically true but what I remember from Gtk+ 1.2 is that it had an object system that was a lot like gobject. It was more like gobject was factored out into its own library and given a new name and some different polish.

Before 2.0 it was GtkObject. 2.0 just factored it out so you could use it for non-GUI code as well.

And Gtk3 was not useable for good quality apps until around 3.16 and Gtk4 just become useable with the recent 4.10 (fixing the ugly scrolling bug).

Wisdom is to know that technology needs to ripe at least 5 years before they are useable, thats what i did to Swift and Kotlin too. While both SwiftUI, Jetpak Compose and WinUI3 are all way to young that i would even waste time at the moment to learn.

Hopefully not. GTK4 deliberately removed support for subpixel font antialiasing, making fonts noticeably more blurry/ugly on non-HiDPI screens. There's a ton of FHD (1920x1080) or 1920x1200 screens out there that are perfectly fine for most usecases, but GTK4 turns them into landfill. :-(