Scope of framework integration plugin?

[Aleix Pol]

On Mon, Nov 30, 2015 at 12:59 PM, Luigi Toscano
<luigi.toscano at tiscali.it> wrote:
> On Monday 30 of November 2015 12:48:26 Martin Graesslin wrote:
>> Hi all,
>>
>> there is currently a review request to add OSX specific changes to framework
>> integration plugin [1].
>>
>> This seems wrong to me. I think our framework integration plugin is about
>> integration Qt applications into the Plasma workspace. In my opinion it
>> should not be used anywhere else. Not on GNOME, not on Windows and not on
>> OSX. The idea of integration is that applications look native on the
>> desired platform. The plugin defines the native look on Plasma and by that
>> using it on other platforms is automatically breaking the integration.
>>
>> Now I understand that some people don't like the native look of their
>> platform and would prefer using Plasma. Sorry I don't have an answer to
>> that. Unfortunately I think it's completely out of scope for the
>> integration platform to be considered outside Plasma.
>
> Really? I see people trying to use KDE Applications (for example on #kde) on
> different desktop environment and being confused for the look and feel. I
> understand that:
> - you don't want the Plasma look used outside Plasma
> - yes, other desktop environment should provide and integration plugin
>
> but isn't it really possible to have a "simpler" default integration plugin,
> when no one else is provided, that at least show the icons, for example?
>
> I think we are not helping users of KDE applications but not Plasma users, and
> let's be realistic about the possibility of other desktop environment
> providing an integration plugin.

Qt already provides QPlatformTheme plugins that integrate on those
platforms. If they don't work, we should fix them upstream.

I'm assuming we agree that we expect applications on non-plasma
platforms to look and behave native.

>
>> Given that: if people agree with my view that the framework integration is
>> only about Plasma, I suggest that we move the framework integration to kde/
>> workspace to release it together with Plasma instead of frameworks.
>
> IMHO only if it's possible to package and load it outside Plasma, or otherwise
> if there is a more sane default plugin.

Aleix