[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: kuiserver future (to gui or not to gui)
From: Thiago Macieira <thiago () kde ! org>
Date: 2007-02-22 18:11:29
Message-ID: 200702221911.36899.thiago () kde ! org
[Download RAW message or body]
Aaron J. Seigo wrote:
>in the latter case, kuiserver should be available and registered on the
> dbus. when another application (e.g. plasma) appears it can take over
> the dbus service. dbus allows such take-overs, so it should be a
> problem.
>
>kuiserver can even give up the service and put itself back in the queue
> so if/when the app (e.g. plasma) disappears later kuiserver will be
> reinstated as the fallback again until something once again comes along
> to take over for it. it could even be made a dbus autostart service so
> simply making a call to ord.kde.kuiserver would cause it to be started
> if it wasn't already.
All of the above is doable and actually easy to do with D-Bus.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
[Attachment #3 (application/pgp-signature)]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic