On 04/02/2012 06:36 PM, Martin Gräßlin wrote:
Am 02.04.2012 18:20, schrieb Nikos Chantziaras:
If you want the Oxygen style in your app, there's a workaround: use
the Gtk
style and make Gtk use Oxygen. The Oxygen-Gtk plugin has no Qt
dependency:
$ ldd /usr/lib64/gtk-2.0/2.10.0/engines/liboxygen-gtk.so | grep -c Qt
0
Oxygen-Gtk has visual bugs when used by Qt apps. I reported one, but
it's a usual WONTFIX or INVALID case, since using Oxygen-Gtk with Qt
is not supported to begin with.
maybe you should point out the findings of this thread. It might
change the assumption that oxygen-gtk in Qt is not needed because
there is the native Qt style.
I'm not sure whether the developers knew about this very specific
constraint.
I do know about it, and am responsible for the "WONTFIX".
Using a gtk theme for a Qt app is a bad idea in general, and no gtk
theme looks identical when running on a gtk app or on a qt app.
Both styles (qt and gtk) simply have too many features (call them hacks
if you want) to have them work decently via any kind of generic wrapper.
(Sadly enough this is true for the other way around, or when trying to
wrap oxygen-qt to work with QML).
I maintain that I do not want to fix bugs generaed by oxygen-gtk when
running on a Qt app.
It is enough to fix the ones for running on a gtk app + any kind of
toolkit wrapping around gtk, there are plenty of them already +
oxygen-kde bugs when running on kde apps (and dynamically linked Qt apps).
The "fix" for using oxygen-kde in statically compiled qt application
should come from oxygen-kde and nothing else.
Maybe write a "bare" qt only version of oxygen with all kde specific
options stripped down, though I'm not sure I can find the time (nor the
motivation) to work on this.
Cheers,
Hugo
Cheers
Martin
Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
unsubscribe <<
Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
