0

Hello.

Bug 159480: Hide labels or icons in taskbar

I think this would be a really great option that would go very well with the KDE 4.2 UI and the options users are used to get when configuring the display coices:
* Icons only
* Text beside Icons
* Text only
* Text below Icons

It would largely increase the possibilities to work with the screen edges and/or get to save a lot of panel space.

Thanks for your support.

Already exists in form of STasks. So Already Implemented.

Primoz wrote:Already exists in form of STasks. So Already Implemented.

As much as I like Stasks, I do not agree that "already implemented" should be used as soon as something on kde-looks/kde-apps have implemented it. Maybe I'm alone in this, but "already implemented" should in my opinion only be used when a feature/app is considered stable enough to be a part of a default installation.

Giving recommendations for third-party (or whatever you want to call it) apps, plasmoids, scripts, whatever. That's fine. I don't think it's a good idea to say something is already implemented if it requires the user to either compile something extra for themselves or having to rely on a non-official (for their distro) repo such as Debian's experimental or Suse's factory/unstable.

Kryten2X4B wrote:

Primoz wrote:Already exists in form of STasks. So Already Implemented.

As much as I like Stasks, I do not agree that "already implemented" should be used as soon as something on kde-looks/kde-apps have implemented it. Maybe I'm alone in this, but "already implemented" should in my opinion only be used when a feature/app is considered stable enough to be a part of a default installation.

Giving recommendations for third-party (or whatever you want to call it) apps, plasmoids, scripts, whatever. That's fine. I don't think it's a good idea to say something is already implemented if it requires the user to either compile something extra for themselves or having to rely on a non-official (for their distro) repo such as Debian's experimental or Suse's factory/unstable.

Oh sorry, I forgot that I use Arch with KDEmod. STasks is part of main KDEmod repository so I totally forgot that it's not easily available to everyone.
Thanks for pointing this out.
I wonder should I send this idea back to main Brainstorming section under edited title:
provide STask with basic KDE.
As I'm using it and it's really cool. It does copy Windows7 heavily now you can even end application from it's taskbar tooltip and clicking on it raises / focuses that app.
So it really should be among defaults.
[hr]
I've just realised that OP proposes other types of taskbar modes than STasks provides.
But ten again idea was already proposed on bugs.kde.org. Which means that devs are aware of it and there is no need for it to clutter Brainstorm with
already wishlisted ideas.

We are still undecided what exactly to do with ideas that refer to bugs.kde.org. Most of them are still unapproved; I made exception with this one as I felt that
STasks provides solution but as it turns out it really provides only a part of solution.

The idea of brainstorming is to get something new into KDE. new as in not-yet-existant.
All entries in kde-look.org are valid additions to KDE (as kde-look is part of the family ), just not shipped in the SVN branches of KDE. If an entry like the above mentioned should be included into KDE svn in your opinion, maybe the author should be poked to mail the maintainers of plasma with the wish to being included.

But that is probably something different from what is intended here.
This place is for getting new ideas in or improving existing parts.

Sorry neverendingo I miss merged your and my post, as I haven't noticed that you have posted while I was posting my post.
Now I can't un-merge it.
Sorry; I'm sometimes a bit to gung-ho and don't look before I leap.

no problem, i fixed it back

Thanks!

neverendingo wrote:All entries in kde-look.org are valid additions to KDE (as kde-look is part of the family ), just not shipped in the SVN branches of KDE.

Very true. But that's also part of my reaction. Things in kde-look.org are very valid additions to KDE, but not everyone can take advantage of everything there, and especially not the things that needs to be compiled. And I think the proportion of the KDE-audience that do not know how to compile things from source is only going to increase.

Maybe the Implemented section should be divided up like:

*Already implemented and will be a part of 4.3 (and increase the version number as necessary)
*Implemented elsewhere. You may need to compile this yourself or install it from an unsupported source (ppa, personal build-service, whatever).

Nice idea, can you please make an own idea of it? I'd like to see what others think before this will be done.

Kryten2X4B wrote:

neverendingo wrote:All entries in kde-look.org are valid additions to KDE (as kde-look is part of the family ), just not shipped in the SVN branches of KDE.

Very true. But that's also part of my reaction. Things in kde-look.org are very valid additions to KDE, but not everyone can take advantage of everything there, and especially not the things that needs to be compiled. And I think the proportion of the KDE-audience that do not know how to compile things from source is only going to increase.

Maybe the Implemented section should be divided up like:

*Already implemented and will be a part of 4.3 (and increase the version number as necessary)
*Implemented elsewhere. You may need to compile this yourself or install it from an unsupported source (ppa, personal build-service, whatever).

I agree with you. This would be useful for users who wonder; if it's implemented where is it? So this would direct them to appropriate address where they could get this or just inform them to wait until KDE4.3.

neverendingo wrote:Nice idea, can you please make an own idea of it? I'd like to see what others think before this will be done.

Done!