Make runner KCMs easier to extend
Open, WishlistPublic

Description

The dbus support for KRunner is great for users who don't know C++ and makes writing the plugins a lot easier.
But the KCMs for the runners have to be written in C++.

My idea is that the users can use an existing kcm and configure a .desktop file for it.
In this file they can expose some basic configuration defining trigger word and making this trigger word required.
And maybe later on some additional widgets.

This will make it also very easy to add basic configuration to an existing plugins and
it will avoid duplicate code.

alex created this task.May 3 2020, 9:48 AM
alex triaged this task as Wishlist priority.
apol added a subscriber: apol.May 3 2020, 11:21 PM

Wouldn't it be better to support different languages on the KCM through QML+KPackage?

KCMs are already supported using QML and it is better integrated on the different form factors.

From QML you can import different languages (at least python and rust, possibly others).

alex updated the task description. (Show Details)May 4 2020, 5:20 AM
alex added a comment.May 4 2020, 9:49 AM

Wouldn't it be better to support different languages on the KCM through QML+KPackage?

That sounds great, but goes beyond the idea of this task :-).

The idea is to make a KCM which does only very basic configuration.
The issue with KRunner is that there are often many different results from different plugins
and being able to define a trigger word helps to clear things up.
Instead of creating (more copy-pasting) a KCM this one can used.

meven renamed this task from Make runner KCMs easier to use to Make runner KCMs easier to extend.May 16 2020, 3:47 PM