Is it intended to not expose Plasma Weather Ion header files?

Development
,
1

Hello, everyone, I am creating a custom Plasma Weather Ion to let org.kde.plasma.weather applet use other third-party weather services. But I found there was no header file in my distribution’s packaged kdeplasma-addons. As I am using Arch Linux, most of the time they will package everything, include those headers, into one kdeplasma-addons package, I think this may because kdeplasma-addons does not install those header files? Anyway, if I copy them manually from repository and cmake build directory, and link my Ion to libplasmaweatherion.so provided by my distribution’s package, my Ion can be built successfully and works well.

So my question is: Is it intended to not expose Plasma Weather Ion header files?

2

I think it was simply never thought out.

I think it wasn’t an area where we imagined having third-party plugins. But nothing keeps you from creating some plugin and/or contributing it upstream.

You probably can contribute to have those headers available, or use kde-builder to build plasma-addons.

3

Actually my Ion implementation uses reverse engineered apis, its stability and legality is not guaranteed. So I am not very sure if KDE can accept. I would not like modifying sources of kdeplasma-addons either, because if I do so, I have to build whole kdeplasma-addons myself and keep it updated with archlinux. Besides, I am able to use the trick mentioned above now, which lets me do not want to modify sources even more. Maybe I can open a whishlist to let KDE developers decide to expose those headers.

4

I find the DataEngine version of Ion, which is used before KDE 6.5, exposes its header file, so I guess developers will not mind to do so if there is no technical issue…

5

Then worse raising.

You can try to contribute this, it should just be a little a little cmake scripting.

6

For anyone who concerns about this, I have created a wishlist report here: https://bugs.kde.org/show_bug.cgi?id=511320

1 Like