[Panel-devel] System tray

Georges A.K. georgesak at gmail.com
Tue Jun 21 21:55:48 CEST 2005


I know the systray has been discussed before, numerous times, but
there was still no consensus reached. Therefore, I'm starting a new
thread dedicated to the systray.
The first thing that should be discussed, IMO, is the technical
aspect. Should the QXEmbed be retained or should we switch to an IPC
mechanism ? I would favour the second option for several reasons.
First off, it would give the systray more control since everything
will be done out of process and will be in the hands of the tray. This
is interesting for the icon hiding, for example (we can know the state
of the app, or whenever the icon is modified). Furthermore, once the
API is pretty stable and functional, we could develop a tool that
would parse specifications (in XML) and output a C++ class (a la
dcopidl). For programs that need a static tray (no modification to the
icon or popup menu), all they would need to do is describe it (XML)
and connect the slots to signals. The obvious problem with that is
interoperability with other DE and with existing non-KDE apps (aMsn
for example).

What do you guys think ?

Georges.


More information about the Panel-devel mailing list