Originally posted by arun54321
View Post
Announcement
Collapse
No announcement yet.
Google Chrome/Chromium Experimenting With A Qt Back-End
Collapse
X
-
Originally posted by skeevy420 View Post
Dialog boxes, borders, and window controls can follow the style of the graphics toolkit. That's about it. It just makes everything look the same.
"GTK-integration" on KDE has for years been based on custom-built Qt themes that try to emulate the looks of a native GTK theme... and you need one for each version of GTK, so the worst case scenario is that you have installed one for GTK 2, one for GTK 3 and one for GTK 4. And they will fail as soon as you change your theme on GTK or Qt away from the built-in theme.Last edited by curfew; 14 April 2022, 01:14 PM.
Comment
-
Originally posted by skeevy420 View PostWhat's funny is GTK programs like Firefox and Chrome can look off on GTK desktops that don't adhere to CSD like Mate and Cinnamon. A Qt Firefox or Chrome would probably look more native than the current versions on "traditional" styled desktops.
Also switching to Qt probably won't change anything in that matter. Neither Firefox and Chrome are using GTK widgets. They are using GTK for some backend stuff, when they switch to Qt there won't be probably very big difference to end user. Probably the biggest advantage of that switch would be possibility to build and install them without GTK dependencies. They won't start looking like native KDE application.
Comment
-
Originally posted by skeevy420 View Post
They use GTK for the File Chooser window and things like that. It's very distracting on my KDE Wayland desktop when I'm presented with that GNOME CSD bullcrap.Code:export GTK_USE_PORTAL=1
Code:~/.profile
- Likes 2
Comment
-
Originally posted by skeevy420 View Post
They use GTK for the File Chooser window and things like that. It's very distracting on my KDE Wayland desktop when I'm presented with that GNOME CSD bullcrap.
- Likes 4
Comment
Comment