[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Re: [PATCH] RunnerManager
From:       "Ryan P. Bitanga" <ryan.bitanga () gmail ! com>
Date:       2008-05-05 4:25:16
Message-ID: cf617050805042125u127b435aw2570c584295d12a6 () mail ! gmail ! com
[Download RAW message or body]

2008/5/2 Jordi Polo <mumismo@gmail.com>:
>
>
> 2008/5/2 Aaron J. Seigo <aseigo@kde.org>:
>
> >
> > On Thursday 01 May 2008, Jordi Polo wrote:
> > > Done, I've tried to solve the last issues of this mail and already
> commit
> > > it.
> > > It will be much easier work with it in SVN.
> >
> > no doubt. i'm so happy that we're on the way with this one.
> >
> >
> > > Yes, detach on reset, now I hope it is OK (If I believed in deities will
> > > pray or something)
> >
> > i'm building now, will test extensively today ...
> >
> > what's next on your krunner agenda? personally, i'm going to move all the
> > runner related classes into a subdirectory in libplasma to keep them
> > together.
>
>
> Most immediate and easy thing would be create a widget to configure
> blacklisting. I will use a KActionSelector (or similar name, don`t have the
> sources here to reference). RunnerManager::configWidget to return it? But
> I`d like to see the patch from Ryan first as he may be doing something
> similar.

Yes, I am. :) I svn up'd last week and krunner kept crashing. So I've
spent the past few days cleaning up some things. I'll have a
clean-up/config patch ready in a day. :) In the meantime, the
spellcheck runner should serve as an example how to get runners to
support config options.

My only problem is access to krunnerrc is hardcoded. I was wondering
if it would be more feasible to have a global RunnerManager instance
and access the config from there.

Cheers,
Ryan
_______________________________________________
Panel-devel mailing list
Panel-devel@kde.org
https://mail.kde.org/mailman/listinfo/panel-devel
[prev in list] [next in list] [prev in thread] [next in thread]