Bug 376164 - GTK3 Engine
Summary: GTK3 Engine
Status: CONFIRMED
Alias: None
Product: QtCurve
Classification: Frameworks and Libraries
Component: gtk3 (show other bugs)
Version: git
Platform: Compiled Sources Linux
: NOR major
Target Milestone: ---
Assignee: Yichao Yu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-08 00:18 UTC by Илья Индиго
Modified: 2018-06-24 06:57 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Илья Индиго 2017-02-08 00:18:36 UTC
Recently on openSUSE Firefox updated to 51.0.1 and it now uses GTK3 style :( , I have no idea how to configure KDE4 in general, and looking it badly. :'(
Before that geany and chromium migrated to it, and more and more applications migrate from gtk2 to gtk3. :(
GTK-3.22.x already stabilized ABI and API, and will not be changed and is just right for it to make a theme that would gtk3-applications looking is nice.
Comment 1 Yichao Yu 2017-02-08 00:58:54 UTC
The stabilized API apparently has all the APIs used by most theme engines removed so it's much harder to implement anything for GTK3 now. There was a debate on the thread where they decide to deprecate the API by keeping the symbol and make them no-op. The bottom line is that it's unlikely that QtCurve will have a GTK3 port before Oxygen does (and Oxygen-GTK3 doesn't work anymore for some GTK versions already AFAICT).
Comment 2 Vadim A. Misbakh-Soloviov (mva) 2017-04-09 19:13:18 UTC
(In reply to Yichao Yu from comment #1)
> QtCurve will have a GTK3 port before Oxygen does (and Oxygen-GTK3 doesn't
> work anymore for some GTK versions already AFAICT).

And it is nothing no take from breeze?

It seems, they did some black magic to work with gtk3 (although, I'm not sure if they already fixed colouring issues, or it still requires re-generation of gtk3-variant).
Comment 3 edisonalvaringo 2018-05-20 23:41:52 UTC
hi any update?? Firefox really does look ugly. Sorry to bother.
Comment 4 Lars Wendler (Polynomial-C) 2018-06-02 13:11:58 UTC
I cannot prove this with a link to upstream documentation, but I've read on many occasions over the last two years that gtk+-3 theming API has been made stable and should not become "broken" anymore with new releases. Now that gnome developers seem to focus on gtk+-4, this seems to be rather unlikely anyway.
Since I consider qtcurve still being the best theme for qt and gtk+-2 I would also like to raise my wish of having gtk+-3 support in qtcurve.
Comment 5 edisonalvaringo 2018-06-02 18:36:34 UTC
is the most flexible theme it could prove useful for integration with none breeze themes. Please make it happen.
Comment 6 edisonalvaringo 2018-06-24 06:55:31 UTC
(In reply to Lars Wendler (Polynomial-C) from comment #4)
> I cannot prove this with a link to upstream documentation, but I've read on
> many occasions over the last two years that gtk+-3 theming API has been made
> stable and should not become "broken" anymore with new releases. Now that
> gnome developers seem to focus on gtk+-4, this seems to be rather unlikely
> anyway.
> Since I consider qtcurve still being the best theme for qt and gtk+-2 I
> would also like to raise my wish of having gtk+-3 support in qtcurve.

isn't the 3.24 the last release in the 3xx series? It might be a good time to port to gtk+3, after all firefox will still be using gtk+3 for a long time. I mean they just switched completely and nuked the gtk+2 _this_year_. It took them several years to switch to gtk+3.
Comment 7 edisonalvaringo 2018-06-24 06:57:59 UTC
https://blog.gtk.org/2018/06/23/a-gtk-3-update/