Bug 58002 - folder columns arbitrarily configurable
Summary: folder columns arbitrarily configurable
Status: RESOLVED DUPLICATE of bug 39782
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian stable Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 34775 44143 62136 64744 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-05-02 07:52 UTC by Jarne Cook
Modified: 2007-09-14 12:17 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jarne Cook 2003-05-02 07:52:07 UTC
Version:            (using KDE KDE 3.1.1a)
Installed from:    Debian stable Packages
OS:          Linux

Currently the only configurablity that the folder columns ahve is the ability to turn on/off size column and toggle between Sender and Reciver.

This is crap.

Guys,  you should ditch this current setup for something like the following.

Each folder has their own settings (which default to Subject, Sender, and Date (Order of Arrival A).  The settings should also remember the column ordering as well (eg. order by Date Desc, Sender, Subject)

The user should be able to edit the "global default" folder columns, and "per folder" columns.

Eg:
All folders have a install default of:
Subject, Sender, and Date

This user edits the "global default" for all unconfgured folders to be:
Importance icon , Attachment icon, Flag icon, Subject, From, To, Date Recieved, Size
Order by date, subject
(there should be a button to "reset all folders to default")

If a user changes the folder (add/moves/removes columns or changes ordering) then that fact should be stored.  If the user edits the columns in the folder such that they are the same as the "global default" then the settings for that folder should just disapear (why double up on config).
Comment 1 Tom Albers 2004-08-04 19:12:33 UTC
*** Bug 62136 has been marked as a duplicate of this bug. ***
Comment 2 Tom Albers 2004-08-04 19:14:22 UTC
*** Bug 64744 has been marked as a duplicate of this bug. ***
Comment 3 Tom Albers 2004-08-04 19:17:06 UTC
*** Bug 44143 has been marked as a duplicate of this bug. ***
Comment 4 Tom Albers 2004-08-04 21:51:21 UTC
*** Bug 34775 has been marked as a duplicate of this bug. ***
Comment 5 Michael Jahn 2004-09-01 22:39:39 UTC

*** This bug has been marked as a duplicate of 39782 ***