- 1 New System Tray Design
- 2 Implementation details
- 3 Further Reading
New System Tray Design
System tray icons generally fall into four categories:
- Indicators of application status
- System services
Applications registering with the system tray provide one of those categories. An instant messaging application or an email client will fall into 'Communications'. System services are for example software update notifications. Examples for Hardware are a battery monitor a mixer or a Network Management applet. Applications that use the system tray for freeing space in the taskbar use the Application Status category. The system tray implementation can choose to provide the information delivered by the client application in different ways.
A System Tray Item will Have the following elements and properties.
- pixmap (possible size variants)
- Passive (normal)
- Needs Attention
- Context menu
- Wheel up/down
The visualization of the registered application is determined by the system tray. It can be implemented as row or grid of icons, as in current system trays. The longer term perspective is to offer category-specific visualization for the applications. Applications that want to expose more control through desktop elements such as the system tray can choose to offer applets to support their specific requirements.
The interactions can be considered in terms of the 'Client' i.e. the icon itself, and the 'Host' e.g. the system tray.
Providing an interface for actions allows for coherent interaction across applications using the system tray.
A client of the system tray is an application that registers with the system tray to display its information. The system tray (the host) reacts to signals it receives from the client. The host also can pass back an action to the client application, for example when the application has been activated. The host receives the signals in an asynchronous fashion from the client. The display of the message might happen delayed.
The Host is the system tray itself. It offers an interface for applications to register in a standardized way, acts on signals sent by these clients, and can do callbacks to the client application (for example to activate a window when the icon has been clicked).
The application can signal the following to the system tray host in order to change appearance and status of the icon:
- A new pixmap is available
- The status changed
- Show the tooltip contents (replaces "balloon messages")
The Host (system tray) can call the following slots in the application:
The Host queries the client for the following properties:
- tooltip data
Draft of the D-Bus xml service description
It keeps the list of applications (dbus services actually) that want to use the systemtray, an application must explicitly register here to gain an icon. it's done outside the actual systemtray to mantain the icon list intact across different plasma sessions. Can be found here.
Protocol plugin in the Systemtray plasmoid
For now it's called DBusSystemTray, can be found here in websvn. It asks SystemTrayDaemon what the registered icons are and listens from it for new icons or removal of others. It will dialog with the applications using the protocol described in the above dbus specification.
(websvn link) This library is aimed to be a drop-in replacement for KSystemTrayIcon and will talk to SystemtrayDaemon to register the app for the assignment of an icon in the systemtray and to the systemtray widget itself with the dbus calls defined in the protocol
Features Moving From Applications to NotificationItem Visualization
Needs Attention Visualization
Some applications provides options for how the "needs attention" visualization should be rendered. This should not be a per-application setting, but something in the visualization itself, allowing for consistent (between items shown) and flexible (e.g. tasks widget vs system tray widget) presentation.
Applications affected: konversation
- notmart.org Marco Martin: Introducing Notification Icons