[PATCH] RunnerManager

[Aaron J. Seigo]

On Monday 21 April 2008, Jordi Polo wrote:
> BTW, in the days I started with plasma development (3 weeks ago?) someone
> told me a review board was used to be around ... It is still nonfunctional?

sadly, yes. hopefully we'll have a replacement soon.

> About the configuration, if a KConfigGroup is passed it means that each app
> that wants to use runners capabilites will have a group in its
> configuration file for it.

yep; and reading this a fundamental question popped up in my mind:

should it be possible to *globally* disable runners, or should that be a 
per-application thing?

answering "yes" makes things a bit more complicated, since it's pretty obvious 
(at least to me? =) that application-local white/black lists are a must. so 
my recommendation is to start there and we can add global white/black lists 
later if the need actually arises.

hm... coming up with use cases would probably help here. currently we'll have:

* krunner, with a white/black list
* kickoff, which will use a similar list and should be shared by all kickoff 
instances
* possibly a search bar plasmoid that uses runners

so, should the krunner white/black list be shared with the kickoff one? should 
kickoff and the search bar use the same white/black list?

since these components are probably perceived by the user as the "same thing", 
i guess the answer is probably "yes, this list should be shared".

another use case might be:

* media plasmoid that lets one not only hit "next, prev, pause, stop, etc' but 
also search the media player's collection via a runner.

obviously this plasmoid's whitelist should not be shared.

so there's certainly a mixing. *thinks*

so i can see three general use cases:

* desktop global (back to your plasmarunnermanagerrc?)
* arbitrary, but shared, configurations (maybe as groups in the global 
config?)
* non-shared configurations (an arbitrary KConfigGroup from an arbitrary 
config file)

thoughts?

> Create a GUI to configure it can mean creating a 
> widget that each app should use ...

i think that's correct...

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Trolltech
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/panel-devel/attachments/20080421/c2f21a20/attachment.pgp