You can contribute to KDE with non-C++ code
You can contribute to KDE with non-C++ code
You can contribute to KDE with non-C++ code :: rabbiticTranslator
I always see:
- people being told they can contribute to KDE with C++/QML
- people being told they can contribute to KDE without code
But I don't often see:
- people being told that they can contribute to KDE with code that is not C++
I like C++, QML, and even CMake, but you might not be interested in them or you might just not be willing to spend time learning another language, and that's perfectly fine.
In this blog post I list a few KDE projects that you might not know about that might be written in your preferred language or in a specialized format you have expertise or interest in.
By far, the most popular programming language actively used in KDE other than the expected languages is Python.
We also have stuff that would interest sysadmins (containers), packagers (snap/flatpak) and web developers.
I remember trying to write a python script to control windows on KDE and could for the life of me not find the libraries, let alone APIs to call.
It's quite simple: when watching tournaments and other events that have multiple streams/stages, I have multiple windows streaming the content and different layouts.
I would like to be able to:
It's not many API calls, but in python, without going down all the way to some X11 library, I haven't found a way to do it using KDE libraries.
There are other usecases for example switching between audio sinks with key strokes, updating window positions depending on which window has been opened and which activity is active, and a bunch of other stuff. Unless I write C++, or know where to find the library, or know how to bind to C++, or want to take the time to bind to C++ with FFI, I'm SOL.
Anti Commercial-AI license
I’ve had good luck interfacing with KDE windows using dbus in python, although if I remember right the more granular control also required javascript (still passed thru dbus with python). The only python library I needed was Qt (for their dbus implementation because I was already using their event loop, but any other lightweight dbus package should work fine).
Is there documentation on the dbus interfaces that's easily searchable? For example, I can't find out something as simple as listing all the windows or even setting a window property.
org.kde.KWindoesn't seem to have it, nor doesorg.kde.plasmashell. Nor do I know what value to pass when it's a "QString` but clearly an enum.Anti Commercial-AI license