It would be helpful for breeze to support gtk2 and gtk3 like oxygen, so that having an uniform look and feel for both qt and gtk applications while using breeze is possible. Reproducible: Always
Iirc Hugo said that gtk3 is deprecating theme engines and so proper gtk3 port is...unlikely. You can however still use QtCurve with the Breeze config and use QtCurve for gtk stuff. That should work.
What you said is very misleading: > GtkThemingEngine has been deprecated in GTK+ 3.14 and will be ignored for rendering. The advancements in CSS theming are good enough to allow themers to achieve their goals without the need to modify source code. so rebuilding breeze in CSS is entirely possible and as future-proof as you can get with GTK :|
> What you said is very misleading Well I said "Iirc Hugo said that gtk3 is deprecating theme engines" which is very true as you just confirmed, then I said "so proper gtk3 port is...unlikely", which is also true. It is unlikely because Hugo (iirc) refuses to do it if there's no proper support for GtkThemingEngine. Then I suggested QtCurve which (again, iirc) should support both gtk2 and gtk3. Neither word from that was "very misleading". > so rebuilding breeze in CSS is entirely possible Yes, I guess it is. Someone just needs to do it. And maintain it.
well, the misleading part was that it sounded like there wasn’t a way to get GTK to use a breeze look. am i right that you wanted to say that code sharing isn’t possible if one theme is done in GTK, and therefore there will no platform-independent breeze drawing code? i think it’s still possible to share code. we’d need to add a stylesheet/theme generator to the same repo as Qt breeze, which uses the colors and margins/paddings of Qt breeze. sure: more duplicate work, but i doubt there could be much code sharing for oxygen-gtk and oxygen.
> Then I suggested QtCurve which (again, iirc) should support both gtk2 and gtk3. Qt Curve has no GTK+ 3 version. I really doubt it will ever have one without GtkThemingEngine. -- snip --- > so rebuilding breeze in CSS is entirely possible That doesn't follow from your quote at all and remains unproven until someone tries and succeeds. > well, the misleading part was that it sounded like there wasn’t a way to get GTK to use a breeze look. "Sounded like" is your interpretation and doesn't make Martin's statement actively misleading. I can't read in there what you read in there. I read doubt that the remaining theming options in GTK+ are sufficient (and share that doubt).
Before the removal of gtktheming engine, oxygen-gtk2 and oxygen-gtk3 shared ~90%. After the said removal: 0% (and some 45 000 lines of code thrown to trash, + some nasty comments from the gtk theming dev) Same would have happened for breeze (with an addition ~50% or more, code share with oxygen, as is the case now for the Qt version). You must understand that within this context the motivation to "port" the said 45k lines (and write as much for breeze), is pretty low on my side. Note that oxygen @ gtk3 is also discontinued.
What about not starting from scratch? kde-gtk-config actually now updates gtk theme to Orion if it's oxygen-gtk previously used and breeze is the theme for Qt because it looks similar to breeze (well.. a little bit). I think the link to this theme is: http://github.com/shimmerproject/Orion/
> Before the removal of gtktheming engine, oxygen-gtk2 and oxygen-gtk3 shared ~90% wow, consider my comment null and void then. i thought hooking into the respective drawing mechanisms would have been a big part, but apparently i’m mistaken. that sucks big time!
i read it and it sucks even more: https://bugzilla.gnome.org/show_bug.cgi?id=735211 just… wow.
Please let's not turn this into Gnome bashing report. Thanks
of course not! i initially defended GNOME, as you can see from my first comments. but judging from that 90% figure hugo gave above, i think that there should be low level theming support in GTK. i think the GNOME devs might have had a similar misunderstanding as me and might see the need more clearly once shown how much code can actually be shared!
I do not see any reason not to bash gnome... From a users perspective this is more than a regression - it's a complete wipe for all the work people have done for using and integrating gnome apps in the KDE environment. And I am not just talking about devs - users like me with some impairment on my eyes have also spent many hours (admittedly towards their own benefit...) trying to get a somehow consistent look out of gnome stuff under KDE... Now to render all these efforts useless without any compatibility path offering a solutions or even suggestions is a slap in many faces and shows lack of respect for the work of their colleagues and their users. And as I accept the fact that any dev can do as he or she pleases - I on the other hand take the liberty to criticize and bash and call this annoying... I think this will lead to not using gnome applications in KDE if not absolutely necessary and it is, at least short term, the end of the idea to choose a desktop environment and then use any application at will. Even more bashing: This has been a segregating decision by the gnome devs and it is harmful in many ways. Though I understand that this is not the place for this discussion and I apologize for bringing it into this thread but on the other hand I think there should be bashing if bashing is due... thx for reading, piedro p.s: I see enough reasons to bash my comments... please feel free to do so - it's relieving!
This is a bug report in a bug reporting tool. Please refrain from any "bashing" or adding long unrelated comments that do not add any value to the actual bug report; this is not the proper venue for these comments. Use forums and/or your blogpost, but please do not clutter bugzilla with that. Thank you. That said, there is a Breeze theme in the works that's nearing completion iiuc.
@Martin Is there a place where we can follow the advancements on this theme?
Yes, I was just looking for it. It's on the KDE forums -- https://forum.kde.org/viewtopic.php?f=285&t=125246 The repos are on github - gtk2: https://github.com/scionicspectre/BreezyGTK and gtk3: https://github.com/dirruk1/gnome-breeze I don't know how well they work though, might be nice if someone tests it and posts back here.
I apologize. thx for the hint on the Breeze theme, p.
I downloaded the GIT themes and tested, well, checked out whether they work... This looks promising. Though obviously incomplete, colors are alright (void of any individual adjustments - but I guess that's expected...) Though starting Gnome Mplayer, the UI is converted - it's white fonts on black canvas ... I wonder whether these additional themes are the right concept in the long run. KDE has extensive individual theme customization options and I think it's not very attrative to customize your theme if the changes are only applied to native KDE applications. Changes in the color scheme should be picked up by non KDE applications via a kind of theme translation engine or by using a kind of chameleon theme for gtk apps. Otherwise if I decide I do not want white fonts on highlighted items (I think the idea of switching highlighted text from black font to white font is a very bad idea!) and I set the highlight color a little lighter so I can have a readable dark font with that... if I go through the effort to do that I never want to repeat all these steps for gtk2, gtk3 or other themes... So, testing the breeze-gtk themes results in similar looking gtk apps without theme customizations and still some bugs like small fonts in dropdown list selectors or selection boxes. But it's a good start I guess... thx, piedro
In 5.5