129

+ Add 'stay visible' button in a corner
This way these plasmoids won't hide on mouse leave ...

@Lukas I might be alone here but I'm a fan of the plasmoid being used instead of the task-bar button. If it lives in the panel then it is visible while the panel is visible.

@dflemstr I think streaming video to these things is going too far. They should be for simple functions and status updates IMHO and I think most of that could be done currently through dbus calls. Start small.

@Lachu: didn't the systray just recover from a model like that? Perhaps the model you are really after has already been implemented?

TheBlackCat wrote:

maninalift wrote:I think that "some embedded controls" might actually be a better approach, since it might be delivered in a way that was both desktop-agnostic and representation agnostic.

There is already a separate idea about that.

Do you know where it is?

andre_orwell wrote:

+ Add 'stay visible' button in a corner
This way these plasmoids won't hide on mouse leave ...

@Lukas I might be alone here but I'm a fan of the plasmoid being used instead of the task-bar button. If it lives in the panel then it is visible while the panel is visible.

@dflemstr I think streaming video to these things is going too far. They should be for simple functions and status updates IMHO and I think most of that could be done currently through dbus calls. Start small.

@Lachu: didn't the systray just recover from a model like that? Perhaps the model you are really after has already been implemented?

Very similar model, but quite different.
We can only have one systray and app must find it in global scope.
In my model we have (two)"systray" for each window. Application must start of search by own window.

@dflemstr: Both. The difference is in z-index. Stay visible, in other words is keep on top, dragging it to desktop make it below all windows + you cant drag it when any window is maximized + when plasma is locked (I'm not sure about this)

Video streaming etc.
Why we cant use one or both plasmoid and/or window preview?
In *combined* mode plasma could limit height of the plasmoid to lets say up to twice of your panle, if it is below preview

Also plasmids can have transparent backgrounds. Might be it is possible to overlay preview?

@Lukas an overlay will probably not look good in some situations, and when you have a plasma theme that isn't transparent, the overlay function would be useless. However, I understand now why you would want to be able to keep the plasmoid in a window. However, I think that such a feature would be up to the individual task manager: either it allows for window previews to be detached, or it doesn't, and that that's a completely different idea than this one.

@Lachu you rimplementation is really a legacy one. Why not use Plasmoids if we can?

Oh, and wouldn't it be possible for applications to somehow expose slots/signals to the plasmoid directly? That would be the easiest implementation, along with shared memory, that would allow for a lot of flexibility. I don't know how it would be implemented technically, however.

maninalift wrote:

TheBlackCat wrote:

maninalift wrote:I think that "some embedded controls" might actually be a better approach, since it might be delivered in a way that was both desktop-agnostic and representation agnostic.

There is already a separate idea about that.

Do you know where it is?

[Plasma/Taskbar] Actions and controls in taskbar thumbnails

@Lachu: take a look at http://www.youtube.com/watch?v=rWBfwloevgc

There was a thread a little while back detailing the improvements inflicted on the systray recently. Can't find it now.

Marked as In Progress. http://reviewboard.kde.org/r/1606/
EDIT: Hm, seems like this is not actually it (rather the reverse). Moved back to Home.