Fun fact: The XDG desktop portal for GNOME mobile is not adaptive, despite Nautilus being Adaptive (Nautilus is still not yet perfect on mobile but it's getting there)
#xdg #linux #linuxmobile #gnome
⇧
Fun fact: The XDG desktop portal for GNOME mobile is not adaptive, despite Nautilus being Adaptive (Nautilus is still not yet perfect on mobile but it's getting there)
#xdg #linux #linuxmobile #gnome
Emmanuele Bassi
in reply to Amy 🇹🇭🏳️⚧️ • • •Amy 🇹🇭🏳️⚧️
in reply to Emmanuele Bassi • • •Amy 🇹🇭🏳️⚧️
in reply to Amy 🇹🇭🏳️⚧️ • • •Emmanuele Bassi
in reply to Amy 🇹🇭🏳️⚧️ • • •Amy 🇹🇭🏳️⚧️
in reply to Emmanuele Bassi • • •Angelo Verlain
in reply to Emmanuele Bassi • • •Emmanuele Bassi
in reply to Angelo Verlain • • •@vixalientoots the GTK portal uses GTK3; the GNOME portal uses GTK4. That's the difference.
You cannot implement GtkFileChooserDialog inside GTK using libadwaita, because libadwaita depends on GTK.
The only way to do that would be for the GNOME portal to implement a whole new file selection dialog living in the portal itself.
Angelo Verlain
in reply to Emmanuele Bassi • • •Max
in reply to Emmanuele Bassi • • •Emmanuele Bassi
in reply to Max • • •Emmanuele Bassi
in reply to Emmanuele Bassi • • •Max
in reply to Emmanuele Bassi • • •@ebassi @vixalientoots Thank you for explaining!
> If we wanted them in GTK4 we would have required breaking API twice, by now.
Would adding adaptive components besides the existing ones be considered an API break? I agree it's probably the dirty way to go at it, but it would at least allow edge cases like non-GNOME software and code depended on by Libadwaita to have standardized adaptive components, although "we still have no precise idea what “adaptive” means" still remains.
Emmanuele Bassi
in reply to Max • • •Max
in reply to Emmanuele Bassi • • •Emmanuele Bassi
in reply to Max • • •