GTK4 migration

[Elbullazul]

This thread is meant to discuss the future of the project regarding GTK4. The available options are:

1. Remake the build system from scratch, reuse some components (mostly SCSS)
2. Rebase the build system on Adwaita's or Yaru
3. Keep using the same system, migrate styling to GTK4 (build system rework coming later)
4. Stop support. GTK4 is not as easy to work with, and GNOME 40 runs very poorly on my machines, so development is slow and tedious

Post your thoughts or ideas below

[Elbullazul]

Turns out the build solution is still quite capable. After some tweaks, we're back in business!

Tonight, experimental support for GTK 4 has been pushed out to most themes, minus the Brilliance pack and B00merang themes (hopefully coming soon).

This is mostly untested code, although I expect few breaking bugs. Please report any errors or inconsistencies you come across in the theme's repo.

[Elbullazul]

Decided to drop a few themes to make the transition a bit easier. Here's the list, along with a short explanation on why. Repositories will be archived eventually.

• Chrome OS (Chrome OS looks mostly the same as Android these days)
• Android TV (No real reason to keep it, as it's almost the same as Android Dark)
• Fuchsia (Didn't really have an identity of its own. Google also seems to have dropped the idea of a Fuchsia UI)
• Wear OS (Same as Chrome OS)
• watchOS (Made redundant with iOS Dark)
• tvOS (Transparency effects make migration to GTK4 difficult, and a matte version is basically iOS)
• Windows Server 2003 (Renamed to Windows Classic)
• Window Server 2012 (Not so different from Windows 8.1)
• Window Server 2019 (Not so different from Windows 10, also who would use a server-themed desktop lol)
• Azurra (bland design IMO, some code will be reused)

along with the B00merang themes, although some of them may return once the migration is completed.