Bug 190571 - tree/folder view wastes space with toplevel branch
Summary: tree/folder view wastes space with toplevel branch
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kdeui (show other bugs)
Version: 4.8
Platform: Ubuntu Linux
: LO wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-25 00:19 UTC by Luis Silva
Modified: 2024-09-14 16:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
How Kmail folder iew looks right now. (16.20 KB, image/png)
2009-04-25 00:20 UTC, Luis Silva
Details
How I would like it to look. (15.56 KB, image/png)
2009-04-25 00:22 UTC, Luis Silva
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Luis Silva 2009-04-25 00:19:44 UTC
Version:           all (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

This is actually a wish for all the applications that use a tree/folder view. Most of the time, having a top-level is not at all usefull and a waste of space. With oxygen theme it is nearly the size of a scroll-bar. My proposal is that top level branch be removed both in kmail and akregator (and maybe other...) as seen in the mockups.
Comment 1 Luis Silva 2009-04-25 00:20:55 UTC
Created attachment 33072 [details]
How Kmail folder iew looks right now.
Comment 2 Luis Silva 2009-04-25 00:22:13 UTC
Created attachment 33073 [details]
How I would like it to look.
Comment 3 Luis Silva 2009-04-25 00:25:44 UTC
Oh! And this is also valid for the e-mail list. Tree branch expanders could be show inside the e-mail items and only when needed.
Comment 4 Björn Ruberg 2010-02-24 01:58:53 UTC
I'm not sure whether this is belongs to kdelibs
Comment 5 Christoph Cullmann 2024-09-14 16:17:23 UTC
Hi,

kdelibs (version 4 and earlier) is no longer maintained since a few years.

KDE Frameworks 5 or 6 might already have implemented this wish.

If not, please re-open against the matching framework if feasible or against the application that shows the issue.

We then can still dispatch it to the right Bugzilla product or component.

Greetings
Christoph Cullmann