KRunner config dialog

Ryan P. Bitanga ryan.bitanga at gmail.com
Wed May 7 10:43:48 CEST 2008


Hi,

My patch will be a little bit delayed yet again due to conflicting
changes in libplasma. My patch reenabled queue timers for
Interface.cpp but Aaron fixed that in RunnerManager a short while ago.
Similarly I also used id() for getting KPluginInfo->pluginName because
I needed it for reloading configs of a specific runner.

For everyone's benefit (and to prevent further delays in my patch), I have:

* Added a reparseConfiguration method to AbstractRunner to reload the
config of a specific runner.
* Got rid of runner phase. Use
setPriority(AbstractRunner::HighestPriority) for first runners, etc.
instead
* Got rid of the blacklist and revamped the load function. (Whitelists
make more sense since the default behavior should be "plugin disabled
by default" ie X-KDE-PluginInfo-EnabledByDefault=false)

(Similarly, for Jordi's priority list, manipulation of relevance would
be the best thing to do IMO)

I'll make a more detailed list as soon as I finish fixing everything.

Just a little question, what did we gain by sharing searchcontext? The
point of performMatch and local searchcontexts was to reduce the locks
on the searchcontext. Currently, we still lock everytime we add a
match and DataPolicy is useless.

Cheers,
Ryan


More information about the Panel-devel mailing list