1
KDE Plasma Tasks Applet
2
=======================
4
This is a desktop applet for KDE Plasma which provides a view
5
of the user's running graphical tasks and allows them to
6
switch between these tasks.
8
It is intended as a replacement for the taskbar found in
14
This section describes the main goals of the tasks applet from the user's
17
- Provide a clear, attractive visual depiction of the user's running graphical tasks
18
- Allow the user to navigate between tasks quickly
19
- Allow the user to group related tasks so that they can be operated on
23
1. Task representation
25
The information currently available from which a task representation can be
29
- A (typically small) pixmap
30
- The 'window class' of a window which can in some cases be used
31
to look up an appropriate icon for that application.
32
- Notifications about changes to a window's state (eg. raised,
33
lowered, wants attention)
35
This information is fairly limited. In order to provide more interesting
36
and useful representations in future, additional information will be
39
- A reliable source for a scalable icon for the task
40
- Information about the documents associated with a task
41
- Information about the people associated with a task
43
2. Navigation between tasks
45
The tasks applet should try to make it as easy as possible
46
for the user to perform a 'context switch' between the different
47
tasks they are performing.
49
On a basic level, this means that:
51
- The user must be able to identify the task from a small
53
- Easily activate a task's representation which causes the
54
corresponding window to be raised and placed at the top
57
Note: One of the flaws of KDE 3's Kicker is that task
58
representations are placed in a 2-task high grid
59
at one edge of the screen. This means that only half
60
of the task representations touch the screen edge and as a result
61
only half of them benefit from the 'infinite size' of a screen
62
edge with respect to activating it with the mouse.
64
In the KDE 3.5.x series there is a bug in Kicker where the
65
colour of the text for a minimized task is grey, against what
66
is usually a grey/silverish panel background. This makes the
67
text difficult to read.
69
Navigation between tasks usually occurs for two reasons:
71
A) The user decides to switch to a different task of their own
74
Example: Greg has been writing a business letter to a client,
75
he decides he wishes to take a break for twenty minutes
76
during which he intends to listen to music and read
77
the latest news online.
79
He therefore wishes to switch away from the word document
80
and email related to that letter to his music player and
83
B) An external interruption
85
Example: Paul is watching the latest episode of a TV drama online when
86
he is alerted by his messaging client that a friend he wants
87
to talk to has come online. Paul then wishes to switch
88
away from the TV episode he is watching and start a conversation
93
This is intended to be the main area of innovation in the KDE Plasma
94
'taskbar' versus that found in KDE 3, Gnome, Windows, and Mac OS X.
96
Some of these windows are likely to be related to the same logical
97
activity from the user's point of view. For example, a paper which
98
the user is writing and the various research material used to
101
The idea is to allow the user to easily group these related tasks
102
so that he can treat them as one. That is, bringing all of them
103
to the front, closing all of them or layout out the windows within
104
a group so that they are all visible on screen at the same time
105
and can be worked with together.