Decide how to implement pinning (and related) in taskmanager / plasma
Open, Needs TriagePublic

Description

As per https://notes.kde.org/public/plasma-5.14-kickoff this is the discussion on how to implement pinning in the task manager / plasma in general.

Past discussions and feature requests related include

Use cases:

  1. Application "launchers" for apps you frequently use
  2. Always-visible icon (systray replacement?) for things like new e-mails
  3. Management of open windows

Right now there are two ways: there is an application launcher plasmoid and there is task manager, which is split into the "regular" one with a label and the icons only task manager. The feature set differs a bit, as the latter can also be bound to activities (which are going to be abandoned?)

Various requests sparked a discussion, e.g. people wanting the option to not show the text label for some applications to save space whilst still have it always visible.

This ticket is to discuss and hopefully decide which part of plasma should implement what use cases, and how (UX) they are presented to the user.

Fuchs created this task.Jul 2 2018, 9:25 AM
abetts added a subscriber: abetts.Jul 2 2018, 2:13 PM

Does this have an expected look yet? What would it look like on the desktop?

Fuchs added a comment.Jul 2 2018, 2:27 PM

Does this have an expected look yet? What would it look like on the desktop?

I think the look (on the desktop, mobile is not my area) is mostly given and will be what it currently is. This would be consistent with what other systems do and it makes sense.
What can be discussed, once the technical implementation is clear and thus what features will stay and which ones won't, is how the interaction with it is done.
That will mostly be wording and not looks though I guess, but I might be wrong on that.

abetts added a comment.Jul 2 2018, 2:28 PM
In T9113#149478, @Fuchs wrote:

Does this have an expected look yet? What would it look like on the desktop?

I think the look (on the desktop, mobile is not my area) is mostly given and will be what it currently is. This would be consistent with what other systems do and it makes sense.
What can be discussed, once the technical implementation is clear and thus what features will stay and which ones won't, is how the interaction with it is done.
That will mostly be wording and not looks though I guess, but I might be wrong on that.

Awesome! Let's keep the discussion open.

ngraham updated the task description. (Show Details)Jul 3 2018, 10:02 PM
ngraham added a subscriber: Plasma.
fabianr added a subscriber: fabianr.Jul 4 2018, 9:20 AM