-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathusability-quick-review.txt
56 lines (40 loc) · 2.83 KB
/
usability-quick-review.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
Global:
- WhatIs button should not be in toolbar until we actually have a substantial amount of whatis help.
KMail has none, for example.
KMAIL:
- Composer window:
The settings menu has a 'configure kontact'. Which should be 'configure kmail' for consistency with the name in the main kmail settings menu.
- Composer window:
Options -> Automatic spellchecking should be moved to the settings menu since its application wide, and not limited to only the current email as the options are for current email only.
I suggest to put it under the configure of the spellchecker, but have a separator in between.
- config dialog, misc tab;
Orig: When trying to find unread messages;
Orig: do not loop
Orig: loop in current folder
Orig: loop in all folders
Propsal: Unread message traversal:
Propsal: To end of Folder
Propsal: Stay in Folder
Propsal: In all Folders
- Store IMap password checkbox should checked by default in account diag
- Remove kmail statusbar entry '0 messages' when leaving the part (see how kaddressbook removes his '%n contacts matching')
- GnuPG log viewer (tools->gnupg log viewer) opens in a waaay to small window
- in (d)imap first count the folders to be updated and set the amount of steps for the progress bar in the statubar to be relevant to that so the progressbar will work accross the whole update, and not per folder. Since the current way makes it unusable from a usability perspective
korganizer
- why does it start with 2 default resources? One is enough.
- rename default resource to "Default calendar resource"
Summary News Feeds
- No rss dcop service available.
You need rssservice to use this plugin.
Oh; my. That must be the worst (best?) example of using too technical error feedback.
Don't use techincal terminology like 'dcop' 'service' 'rssservice' or 'plugin'.
TODO viewer:
- problem: in the todo-view the categories you can set via the context menu on a todo row does not only come from the user settings, but also from the various resources. Add a resource and you might see more categories appear in te context menu. Problems start to appear when you have really old todo's in your resource which categories are auto-added.
For example; a category named after a project I was on last year, for a different boss.
Suggestion; don't add categories from resource-items older than 6mnts.
Suggestion2: add hierarchical categories and add one submenu 'old'
- The context menu for percent does not add a checkbox in front of the item that is the active one.
So if I set the completion of a todo to '40%' and open the context menu, I expect the relevant item to be checked.
naturally when its at '38%' I don't expect any to be set.
- resort ordering of the table colums. Most important things first.
See the research from Ellen for best feedback what is used. Recurrence intuitively should be about last.