With libadwaita 1.5 adaptive about windows and dialog are finally a reality. This is the only reason why we forked GTK4, so we should use that opportunity to drop it.
@tpikonen do you think you can test and verify when would this be ready to be dropped?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
Apparently the only app depending on GTK4 only is megapixels, which we can probably ignore for this. Apps depending on libadwaita areSome important apps depending on libadwaita are (full list of libadwaita reverse dependencies in alpine is here):
calls (the Gtk4 port is almost there)
chatty
epiphany
gnome-bluetooth
gnome-calculator
gnome-calendar
gnome-clocks
gnome-console
gnome-contacts
gnome-control-center
gnome-firmware
gnome-maps
gnome-passwordsafe
gnome-podcasts
gnome-software
gnome-system-monitor
gnome-text-editor
gnome-usage
gnome-weather
livi
loupe
nautilus
phosh-mobile-settings
portfolio
postmarketos-welcome
resources
tuba
When these are ported to the new AdwDialog interface the patches to GTK4 can be removed. Gnome 46 probably fixes this for most of core Gnome apps.
Edit: Made the app list into a checklist, added calls.
Edit 2024-09-06: Ticked chatty, phosh-mobile-settings and postmarketos-welcome
Todays edge update brought in these packages from Gnome 46: calls, gnome-calendar, gnome-console, gnome-control-center, gnome-usage, loupe.
Only gnome-calendar and gnome-usage use at least AdwAboutDialog and presumably have ported also other dialogs to AdwDialog. It looks like we still need to patch Gtk4.0 for this Gnome release cycle.
There's a thin line to walk there. If we keep the fork, then we provide people with no motivation to actually contribute upstream and help them port their widgets. If we remove the fork, we will regress, and have the risk of annoyed people getting bugs filled upstream for things upstream care less than us, and that does not help our relationship with them. I've always been on the team of creating slight inconvenience. Hopefully now that there's a real upstream widget, I can convince you that it's the correct thing to do? Maybe together with an edge blogpost informing people about it?
In principle I agree with you on creating incentives for porting, but basically all apps in the list above are either Gnome core apps which have AdwDialog support as a release goal (I suppose), or mobile focused replacements. I'm not sure how much influence pmOS dropping convenience features has in these cases.
Gnome seems to make monthly point releases, I suggest we wait 2-3 of these to re-evaluate this, after all libadwaita 1.5 is only a week old.
@tpikonen what do you think about the current status? At least in papers we are now using the dialogs, and I hope others also did, but did not follow it closely. I'd be very happy if we could drop this for 47
There's no excuse any more to not use AdwDialog in libadwaita apps, so for those apps the GTK4 patches are not needed. That leaves app-like things using GTK4, but not libadwaita. I found at least these in alpine after a quick search:
czkawka-gui
freeciv-client-gtk4
image-roll
iwgtk
megapixels
pavucontrol
pidif
ripdrag
transmission-gtk
The list is not too long, some of these claim to be (and are) adaptive without libadwaita and some have obvious adaptive replacements (but some could use porting to libadwaita, so if someone is in need of a project, go ahead ). There's nothing here to justify keeping the GTK4 patches either, so feel free to drop the fork.
Nice! Thanks a lot for the research! I just set the due date to 18th of September for GNOME's 47 release, as we don't package unstable things. But so happy to hear we finally have a deadline to drop this!