Originally posted by oiaohm
View Post
Announcement
Collapse
No announcement yet.
XWayland 21.1 Release Candidate Offers Split From The X.Org Server
Collapse
X
-
Originally posted by curfew View PostThis doesn't happen on classic Linux desktops because the libraries are shared. Not sure about those pesky flatpaks and snapchats and whatevers, though.
https://docs.flatpak.org/en/latest/d...tegration.html
In fact, theming of flatpak apps (except proprietary) tends to be pretty good/unified.
However, apps can still use different libraries.
No clue about snap (.. and don't care enough to check).
Edit: out of curiosity, I installed picard from debian repos and flatpack:
--> flatpack follows system-wide dark theme; the native installed client does not (even with preference set to use system-wide theme)!
I would upload a screenshot but seem to be "not authorized to upload attachments".
Anyhow, this is quite interesting; anyone concerned with theming might want to try installing as many apps from flatpak as possibleLast edited by mppix; 22 February 2021, 04:47 PM.
Comment
-
Originally posted by mppix View PostFlatpak has desktop integration and decides what application toolkit (Electron, GTK, Qt) to use
https://docs.flatpak.org/en/latest/d...tegration.html
Flatpatk cannot do anything more than what is possible via regular "global filesystem" in a traditional distro installation. Flatpak can only introduce additional restrictions which make unifying the look-and-feel of different toolkits even more complex. This is what I was referring to in my earlier post.
The optimal scenario for Flatpak would be that it doesn't break anything; it also cannot fix anything. (Aside maybe per-app themeability but the docs you linked mention that this is not possible.)
Comment
-
Originally posted by curfew View PostWhat you said here is impossible. The apps are programmed using Qt or GTK or something else and the packacing format cannot change that.
Flatpatk cannot do anything more than what is possible via regular "global filesystem" in a traditional distro installation. Flatpak can only introduce additional restrictions which make unifying the look-and-feel of different toolkits even more complex. This is what I was referring to in my earlier post.
The optimal scenario for Flatpak would be that it doesn't break anything; it also cannot fix anything. (Aside maybe per-app themeability but the docs you linked mention that this is not possible.)
Comment
-
Originally posted by ssokolow View PostIt did invent and drive the introduction of the XDG Portals system (Can't remember if that was back when it was called xdg-app or if it came about after the name change), which allows anything using QFileDialog without the non-default DontUseNativeDialog flag or GtkNativeFileChooser to seamlessly pick up your desktop's preferred Open/Save dialogs. (Though, when running outside Flatpak or snappy, GTK requires you to manually set the GTK_USE_PORTALS environment variable.)
Comment
-
Originally posted by curfew View PostFlatpatk cannot do anything more than what is possible via regular "global filesystem" in a traditional distro installation. Flatpak can only introduce additional restrictions which make unifying the look-and-feel of different toolkits even more complex. This is what I was referring to in my earlier post.
Yes it would be good to add per application theming with flatpak but that does not change that flatpak intentionally don't use the host theming that could be modified in ways that could break applications.
The current GTK, Qt.... themes have to match the libraries we don't have proper generic theming.
Comment
-
Originally posted by oiaohm View PostYou need to read over the flatpak link again. There is something mega horrible but also required, Flatpak is not using the host themes. Instead you install themes from flatpak repository that are close to the host theme.
Yes it would be good to add per application theming with flatpak but that does not change that flatpak intentionally don't use the host theming that could be modified in ways that could break applications.
Comment
-
Originally posted by ssokolow View PostIt did invent and drive the introduction of the XDG Portals system.
Comment
-
Originally posted by curfew View PostWhat you said here is impossible. The apps are programmed using Qt or GTK or something else and the packacing format cannot change that.
Flatpatk cannot do anything more than what is possible via regular "global filesystem" in a traditional distro installation. Flatpak can only introduce additional restrictions which make unifying the look-and-feel of different toolkits even more complex. This is what I was referring to in my earlier post.
The optimal scenario for Flatpak would be that it doesn't break anything; it also cannot fix anything. (Aside maybe per-app themeability but the docs you linked mention that this is not possible.)
My testing suggests that this is more consistent than native themes, at least as far as dark/light theming goes. Of course, flatpak does not rewrite apps in a different toolkit...Last edited by mppix; 23 February 2021, 01:52 PM.
Comment
-
Originally posted by oiaohm View PostThere is something mega horrible but also required, Flatpak is not using the host themes. Instead you install themes from flatpak repository that are close to the host theme.
Originally posted by oiaohm View PostYes it would be good to add per application theming with flatpak but that does not change that flatpak intentionally don't use the host theming that could be modified in ways that could break applications.
In short, native apps and flatpak use distinct theming. Both can fall back to defaults if needed. However, flatpak seems to be more consistent about installing and using the proper themes without extra configuration (at least on debian).
Originally posted by oiaohm View PostThe current GTK, Qt.... themes have to match the libraries we don't have proper generic theming.
Last edited by mppix; 23 February 2021, 01:56 PM.
Comment
Comment