https://bugs.kde.org/show_bug.cgi?id=378113
--- Comment #2 from Ruslan Kabatsayev <b7.10110...@gmail.com> --- > I just set up a KDE dev account and do have some knowledge in CSS, but > unfortunately none in creating theme engines or reverse-engineer and convert > the to CSS. Do you realize that maximum what you should expect as achievement is something more or less similar to "Oxygen Molecule" GTK theme, i.e. 1) No runtime switching of color schemes, since GTK3 themes are now CSS, not executable code 2) No adjustments of widget sizes (e.g. combobox dropdown, GtkFrame, etc.) 3) No Oxygen shadows, since this requires ability to set X11 properties (not sure how this is implemented on Wayland) 4) Not even alpha channel for corners of menus, tooltips, combobox dropdowns (although GTK3 might have implemented this for CSS) 5) No way to use XShape for corners for the cases when compositor is off (although this is already broken even in KWin's Oxygen window decorations) 6) Probably not even background gradient (although this might be possible now) 7) Window decorations for GTK3 windows won't have background gradient anyway since X11 properties are impossible to set (again, not sure how this works on Wayland) 8) Complete inner shadows in e.g. lists are not possible with CSS, since this required some hacks on GTK-level compositing of widget rendering 9) Some other features lacking All that said, I think if you want more or less complete implementation of Oxygen, you might want to look into implementing it as a plugin similarly to implementation of overlay-scrollbar-gtk3 in Ubuntu. This will allow to inspect widget tree as oxygen-gtk2 does (and oxygen-gtk3 did), thus providing a means of implementing most of (if not all) the hacks needed. If you don't feel like going this "hacky" way, then you're limited to basic support via CSS with the limitations listed above. -- You are receiving this mail because: You are watching all bug changes.
