kuiserver future (to gui or not to gui)

[Thiago Macieira]

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070222/96e40c21/attachment.sig>