Proposal: use Icon Tasks as our default taskmanager.

[Mark]

On Mon, May 7, 2012 at 10:04 AM, Aaron J. Seigo <aseigo at kde.org> wrote:

> On Saturday, May 5, 2012 14:25:09 Mark wrote:
> > 1. Ghosting still seems to be an issue. Even though i do have Qt 4.8.1. I
> > haven't re-opened https://bugs.kde.org/show_bug.cgi?id=275469 yet since
> i
> > think the ghosting doesn't occur in icon tasks.
>
> feel free to work on it. the last causes of it were found to be related to
> issues with x events in Qt.


> > 2. Sometimes taskbars seem to be overlapping. It's very efficient use of
> > space and perhaps usable for tablets but i rather dislike it. hehehe,
> > anyway, there is a bug report for that as well:
> > https://bugs.kde.org/show_bug.cgi?id=275469
>
> this is very likely just the same issue as #1
>
> > 3. Task Manager sometimes seems to forget which applications are pinned.
> > They are back again when the user logs out and back in. (restarting
> > plasma-desktop is probably also an option)
>
> a friend here in zürich did some sleuthing work and figured out when this
> happens -> it turns out it is triggered when kbuildsycoca runs. with that
> information in hand, i was able to fix it quickly, and that fix is in
> 4.8.3.
>
> i also fixed the issue that preferred applications (e.g. "dolphin" == "file
> manager") were not being properly associated with each other.
>
> > 4. Minimize effect could go all ways with taskmanager. Sometime even to
> the
> > middle of the screen. This issue happens so darn often! At first i
> thought
>
> As for all the issues i mentioned. It really "seems" like libtaskmanager
is working as it should and the one feeding the data to libtaskmanager is
doing something wrong. So the taskmanager plasmoid. I'm not 100% positive
that this is the case, but those issues seem to be occurring when the
geometry of the actual task is being set. That one is being set from within
the taskmanager, not libtaskmanager. That's "probably" where icon tasks is
doing something a bit better/different then the current task manager
plasmoid.


> please feel free to offer a fix. i believe on the bug report for this item
> i
> explain quite clearly what the issues are.
>
>
> anyways ... we have an amazing process called "bug fixing". instead of
> replacing one body of code with another under the mistaken impression that
> if
> we just pick a different set of code all bugs will go away, we fix bugs
> that
> exist.
>

I know, i know. But that really depends on the vision. If it is the
intention to keep the current task manager plasmoid in KDE for the coming
releases than it's worth taking a look into it. If it's going to be
replaced by either the QML version or icon tasks then it's not even worth
looking into it since it will change fairly soon anyway.

Please do let me know. Is it the intention to keep this baby around for the
coming releases or should we switch to the QML version? Since if it's the
latter then i will happily start hacking on the QML version to get it on
par with the current plasmoid. Assuming i can even get the QML version to
work.

>
> --
> Aaron J. Seigo
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel at kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20120507/4b39b44e/attachment.html>