<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 2, 2016 at 9:42 AM, Martin Graesslin <span dir="ltr"><<a href="mailto:mgraesslin@kde.org" target="_blank">mgraesslin@kde.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Monday, February 29, 2016 9:42:11 PM CET Sven Brauch wrote:<br>
> Hey,<br>
><br>
> On 02/28/2016 03:58 PM, Luigi Toscano wrote:<br>
> > This is what I use:<br>
> > export QT_QPA_PLATFORMTHEME=kde<br>
> ><br>
> > and you need the integration plugin installed. It used to be part of<br>
> > Frameworks (frameworksintegration), it will be part of Plasma (but<br>
> > hopefully still usable without).<br>
><br>
> It isn't, unfortunately. For example, it requires KSNI support, because<br>
> for some weird reason that is part of the platform theme.<br>
><br>
> So using QT_QPA_PLATFORMTHEME=kde is basically not a viable solution for<br>
> any non-plasma desktop out there. Instead you are stuck with a 3rd party<br>
> solution like qt5ct to at least set the Qt / icon theme (color scheme is<br>
> quite hard already), and there is basically no viable option to get e.g.<br>
> KDE file dialogs back (instead of the unusable Qt5 default ones).<br>
><br>
> Quite a step back from KDE 4 times right now, unfortunately :/<br>
<br>
</span>I'm a little bit surprised by this sub-thread and the reasoning. Apparently<br>
nobody is interested in writing and maintaining a qpt-plugin for non-plasma.<br>
The Plasma devs are willing to maintain such a plugin and then get complaints<br>
that it focuses on Plasma. Seriously?<br>
<br>
If you think Qt's default is too bad, improve Qt. If you think it needs a more<br>
generic qpt-plugin which can be used outside of Plasma: do it. But don't<br>
complain to people doing actual work.<br><br></blockquote><div><br></div><div>That's always the kind of reasoning FOSS people give. "If you don't like it, provide patches to improve it".</div><div>I don't really like that argument.. But yes, i even sometimes give that argument if someone wants to have something that i don't like to make ;)</div><div><br></div><div>I don't think that improving Qt is an option here. Qt has a default simple fallback style. It uses that when there is nothing. I'm not so sure if improving Qt's default to be more fancy would be such a good thing. So lets continue this reasoning with the assumption that the Qt defaults as they are right now remain as is and a plugin has to be written to improve the situation.</div><div><br></div><div>A question for you and Thiago.</div><div>@Martin G, would it be acceptable to have two plugins:</div><div>1. A basic "KF5" plugin that integrates Qt with KF5 and the plasma style, no other plasma specific stuff besides it's theme. Lets call this "kf5_qpa"</div><div>2. A plugin _on_top_of_that_ which integrates with the very specific plasma things. Lets call this "plasma_qpa"</div><div><br></div><div>@Thiago, how would you write a plugin like that? Can this be done simply by inheriting? So the "plasma_qpa" plugin would inherit from the "kf5_qpa"? Or is there another simpler way of achieving the same goal?</div><div><br></div><div>@Martin G, if such a plugin is made, would the plasma people use this structure? Since i would hate it if this would end up with two close to identical plugins, one maintained by plasma, one slowly bit rotting away.</div><div><br></div><div>If it is that "simple" then i'm willing to put some time into it and get it working.</div></div></div></div>