RFC: split platformtheme plugin from frameworkintegration and move to kde/workspace

[Mark Gaiser]

On Mon, Dec 7, 2015 at 1:09 PM, Martin Graesslin <mgraesslin at kde.org> wrote:

> Hi all,
>
> based on the discussion in [1] I propose that we split out platformtheme
> plugin from frameworkintegration into a dedicated repository and move it to
> kde/workspace to be released together with Plasma 5.6.
>
> The main reasoning is that this plugin only gets loaded with env variables
> set
> in startkde anyway, which makes it a Plasma (Desktop) specific plugin. It's
> about integrating Qt application into Plasma and by that pretty useless for
> anything outside Plasma. Moving it to Plasma has in my opinion some
> advantages
> as we can better synchronize the release cycle and also allow us to depend
> on
> libraries provided by workspace [2].
>
> I'd like to get some feedback on the proposal and if this gets positive
> feedback, I'll look into performing the split.
>
> Best Regards
> Martin Gräßlin
>
> [1] https://mail.kde.org/pipermail/kde-frameworks-devel/2015-November/
> 029022.html
> [2]  e.g. I need a dependency to KWayland, which is currently not yet
> possible
> due to KWayland not yet being moved to frameworks.
> _______________________________________________
> Kde-frameworks-devel mailing list
> Kde-frameworks-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
>
>
While at it. Why does frameworkintegration force [1] specific fonts upon
the user?

It's fine that apparently some folks prefer Oxygen fonts over all else, but
i thoroughly dislike it.
I always end up blacklisting it in my pacman manager (pacman, archlinux)
since 99% of the time when i have font issues, it's because of that package
being installed.

Imho, it's ok if Plasma "prefers" one font over another (which can be
Oxygen) but it should definitely not force it upon the user.


Regarding your proposal. When running KDE apps on something other then
Plasma, you would also want to have the frameworksintegration plugin to be
loaded, right?
Specially the platformtheme folder with the vastly improved dialogs over
stock Qt. Remember, those improved dialogs have the power of KIO behind it
instead of the default Qt support (only the local filesystem)

I really see value in having that usable in - say - openbox or any other
non plasma environment where people would want to open KDE applications
that make use of framework libraries (like KIO).

Isn't the only plasma specific part the KStyle folder?


[1]
https://quickgit.kde.org/?p=frameworkintegration.git&a=blob&h=75dc9b92578577c28288500795198027b4c725ad&hb=fcb3f531ae7161f4ef0768a86db8ce98571f3118&f=CMakeLists.txt#l72
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20151207/7259fa41/attachment.html>