KDE TechBase - User contributions [en]

Projects/Usability/HIG

2009-07-27T14:14:06Z

Seele: add kns entry

__NOTOC__
Please add any guidelines questions or requests to the [[Projects/Usability/HIG_Questions|HIG Questions]] page.

Also see the [http://developer.kde.org/documentation/standards/kde/style/basics/index.html KDE3 User Interface Guidelines] and the draft notes for the [http://wiki.openusability.org/guidelines/ KDE4 Human Interface Guidelines].

[[Projects/Usability/HIG/SOU_Workspace|Season of Usability HIG & Design Patterns Workspace]]

==Index==
===C===
* [[Projects/Usability/HIG/Capitalization|Capitalization]]
* [[Projects/Usability/HIG/Check_Box|Check Box]]
* [[Projects/Usability/HIG/Combo_Box|Combo Box]]

===D===
* [[Projects/Usability/HIG/Date_Time|Date and Time]]
* [[Projects/Usability/HIG/Dialogs|Dialogs]]

===E===
* [[Projects/Usability/HIG/Ellipsis|Ellipsis]]

===F===
* [[Projects/Usability/HIG/Form_Label_Alignment|Forms: Label Alignment]]

===K===
* [[Projects/Usability/HIG/KNS|KNewStuff Button Labels]]
* [[Projects/Usability/HIG/Keyboard_Accelerators|Keyboard Accelerators]]
* [[Projects/Usability/HIG/Keyboard_Shortcuts|Keyboard Shortcuts]]

===L===
* [[Projects/Usability/HIG/Labels|Labels]]
* [[Projects/Usability/HIG/Lists_Rich_Lists|Lists and Rich Lists]]

===M===
* [[Projects/Usability/HIG/Menu_Bar|Menu Bar]]
* [[Projects/Usability/HIG/Messages|Messages]]
===R===
* [[Projects/Usability/HIG/Radio Buttons|Radio Buttons]]
===S===
* [[Projects/Usability/HIG/Slider|Slider]]
* [[Projects/Usability/HIG/Spin_Box|Spin Box]]

===T===
* [[Projects/Usability/HIG/Tabs_Pages|Tabs and Pages in Dialogs]]

===W===
* [[Projects/Usability/HIG/Wording|Wording]]

[[Category:Usability]]

Projects/Usability/HIG/KNS

2009-07-27T14:13:16Z

Seele: new page on kns

K New Stuff (or Get Hot New Stuff) is an integrated data service which allows users to share and download themes, templates, wallpapers, and more through a single click of a button in the application.

Because of translation issues, a single class cannot be created which controls the icon and label automatically. Developers must manually create the button in their application. The following are recommendations on what that button should look like.

For more information about the usability issues regarding the KNS button, see [[http://obso1337.org/hci/kde/KNS_Review_July_14_2009.pdf|this report]].

A KNS button has four parts:

*Icon: use get-hot-new-stuff.png
*Instruction: "Get New"
*Object: The type of file the user will download
*Ellipsis: To indicate the user must provide additional input to complete the task

KNS has it's own oxygen '''icon''', get-hot-new-stuff.png. This is placed on the left side of the button. The button label is a combination of the '''instruction''', '''object''', and '''ellipsis'''. For example, if the button will help the user download new wallpapers, the button label would be "Get New Wallpapers...".

Here are some examples of KNS buttons:

[[File:Kns.png]]

File:Kns.png

2009-07-27T14:12:25Z

Seele: KNewStuff Button Examples

KNewStuff Button Examples

Projects/Usability/Meetings

2009-05-28T03:00:56Z

Seele:

This is the planning page for KDE Usability Project meetings on #kde-usability on irc.freenode.org. The purpose of the meetings is to '''Get Usability Stuff Done'''. These meetings are free for anyone to listen in on; however, they are mostly for designers and developers. For more information scroll and read About the Usability Meetings.

==Next Meeting in May ==

The next meeting will sometime near the end of June 2009 in #kde-usability.

==Previous Meetings==

* 2009 May 13 (need IRC logs!)
* [[Projects/Usability/Meetings/2009March18|2009 March 18]]
* [[Projects/Usability/Meetings/2009Feb21|2009 Feb 21]]

===Meeting Topics===

Add meeting topics you would like to discuss. Not all of the topics will be able to be covered in a single meeting and so might be deferred until later. Please include your name/irc nick and a link to a project page or bug.

# KWin: Placement policy 'Remember' ([http://bugs.kde.org/show_bug.cgi?id=15329 Bug 15329])
# To which menu entry we should add icons, and to which one we shouldn't add icons. ( Possible UI case could by Qt application Kadu Instant Messenger: 1) http://tinyurl.com/menukadu , 2) http://tinyurl.com/menucontacts , 3) http://tinyurl.com/menuhelp2 , 4) http://tinyurl.com/menucontext2 [Too many icons] )
# Desktop Settings Dialog: Review its usability (Anne-Marie Mahfouf)
## Improve Desktop Theme: Customized (works with Desktop Theme Details kcm from System Settings)
## Add SlideShow effects options: where, how
# KDE4 KMail 1.11.1 doesnt store column order ([http://bugs.kde.org/show_bug.cgi?id=186841 Bug 186841]).
# lots of drawing glitches, mostly in tray
# DragonPlayer general usability
# Quit should exit totally the application? ([https://bugs.kde.org/show_bug.cgi?id=180466 Bug 180466]) Can this bug be closed?
# problems with small screens (netbooks): mainly kde-pim is not prepared for small screens like the eeepc one (some places with no scrollbar for example).
# Copy dialog start / stop buttons inoperative when panel is locked (https://bugs.kde.org/show_bug.cgi?id=183446)
# 'Full Screen' option should really be in the 'View' menu (https://bugs.kde.org/show_bug.cgi?id=106807)
# no option should require good reflex and/or mouse handling skills (https://bugs.kde.org/show_bug.cgi?id=125208)
# No indication of currently focused area (https://bugs.kde.org/show_bug.cgi?id=187537)
# Wish: Folder Icon indicates empty folder (https://bugs.kde.org/show_bug.cgi?id=153199)
# Ability to place a toolbar on the right of the menu bar (https://bugs.kde.org/show_bug.cgi?id=169043)
# Separate fonts for different languages (https://bugs.kde.org/show_bug.cgi?id=14496)
# KDE errors: Option for non-translated English version (https://bugs.kde.org/show_bug.cgi?id=170664)
# Resize windows based on drag location (https://bugs.kde.org/show_bug.cgi?id=182069)
# (Line to) indicate previous page boundary when scrolling a document (https://bugs.kde.org/show_bug.cgi?id=93196)
# Wish: Delete shows size/contents (https://bugs.kde.org/show_bug.cgi?id=156249)
# Add any button to toolbar (https://bugs.kde.org/show_bug.cgi?id=147372)
# Analog clock difficult to read with dark theme (https://bugs.kde.org/show_bug.cgi?id=165199)
# Kate's "Settings" menu bar action, should be like the rest of applications... the "Settings" should be at the bottom, Configure Shortcuts is above, and Configure Toolbars is above that. Image: http://is.gd/ptqI (sreich)
# KMail: review sort order and aggregation mode settings (the two little icon buttons at the top right). Currently a bit confusing. Problem 1: The meaning of buttons/icons itself. Problem 2: The meanings of labels are unclear e.g. "Current Activity". Problem 3: changing it for one folder always changes the default too.
# Right-clicking Desktop and picking Settings isn't the same as going to System Settings and picking Desktop (Andrew Coles, coles on IRC).

==About the Usability Meetings==

We will discuss practical usability-related issues and attempt to reach reach a resolution. Usability topics which are too large or too broad may be too much to discuss in a single meeting and should be broken up into smaller issues or schedule a dedicated meeting.

Meetings are structured and attempt to follow a preset agenda. There is a meeting leader/moderator (probably seele) who will control the flow of discussion to help keep the meeting on track.

Meeting format is as follows: An agenda item will be presented, describing the problem and a proposed solution. If the item was suggested by someone in particular, they will be asked to provide additional information about the problem. Those in attendance will then be able to discuss the issues in the problem. The meeting moderator will attempt to keep the meeting on track of the topic.

Meetings are normally at 20UTC, alternating weekday and weekend days. Meetings will last no longer than 2 hours. If we do not get through the list in 2 hours, the topics will be covered in the next meeting. If we get through the list in < 2 hours and people are still responsive, we will possibly add an additional topic from the main meeting topics list if the people necessary for discussion are in attendance.

Projects/Usability/Meetings

2009-05-13T20:37:44Z

Seele: Removed old meeting topics

This is the planning page for KDE Usability Project meetings on #kde-usability on irc.freenode.org. The purpose of the meetings is to '''Get Usability Stuff Done'''. These meetings are free for anyone to listen in on; however, they are mostly for designers and developers. For more information scroll and read About the Usability Meetings.

==Next Meeting in May ==

There will be no meeting in April. The next meeting will be Wednesday May 13 2009 at 20:00 UTC in #kde-usability.

==Previous Meetings==

* [[Projects/Usability/Meetings/2009March18|2009 March 18]]
* [[Projects/Usability/Meetings/2009Feb21|2009 Feb 21]]

===Meeting Topics===

Add meeting topics you would like to discuss. Not all of the topics will be able to be covered in a single meeting and so might be deferred until later. Please include your name/irc nick and a link to a project page or bug.

# KWin: Placement policy 'Remember' ([http://bugs.kde.org/show_bug.cgi?id=15329 Bug 15329])
# To which menu entry we should add icons, and to which one we shouldn't add icons. ( Possible UI case could by Qt application Kadu Instant Messenger: 1) http://tinyurl.com/menukadu , 2) http://tinyurl.com/menucontacts , 3) http://tinyurl.com/menuhelp2 , 4) http://tinyurl.com/menucontext2 [Too many icons] )
# Desktop Settings Dialog: Review its usability (Anne-Marie Mahfouf)
## Improve Desktop Theme: Customized (works with Desktop Theme Details kcm from System Settings)
## Add SlideShow effects options: where, how
# KDE4 KMail 1.11.1 doesnt store column order ([http://bugs.kde.org/show_bug.cgi?id=186841 Bug 186841]).
# lots of drawing glitches, mostly in tray
# DragonPlayer general usability
# Quit should exit totally the application? ([https://bugs.kde.org/show_bug.cgi?id=180466 Bug 180466]) Can this bug be closed?
# problems with small screens (netbooks): mainly kde-pim is not prepared for small screens like the eeepc one (some places with no scrollbar for example).
# Copy dialog start / stop buttons inoperative when panel is locked (https://bugs.kde.org/show_bug.cgi?id=183446)
# 'Full Screen' option should really be in the 'View' menu (https://bugs.kde.org/show_bug.cgi?id=106807)
# no option should require good reflex and/or mouse handling skills (https://bugs.kde.org/show_bug.cgi?id=125208)
# No indication of currently focused area (https://bugs.kde.org/show_bug.cgi?id=187537)
# Wish: Folder Icon indicates empty folder (https://bugs.kde.org/show_bug.cgi?id=153199)
# Ability to place a toolbar on the right of the menu bar (https://bugs.kde.org/show_bug.cgi?id=169043)
# Separate fonts for different languages (https://bugs.kde.org/show_bug.cgi?id=14496)
# KDE errors: Option for non-translated English version (https://bugs.kde.org/show_bug.cgi?id=170664)
# Resize windows based on drag location (https://bugs.kde.org/show_bug.cgi?id=182069)
# (Line to) indicate previous page boundary when scrolling a document (https://bugs.kde.org/show_bug.cgi?id=93196)
# Wish: Delete shows size/contents (https://bugs.kde.org/show_bug.cgi?id=156249)
# Add any button to toolbar (https://bugs.kde.org/show_bug.cgi?id=147372)
# Analog clock difficult to read with dark theme (https://bugs.kde.org/show_bug.cgi?id=165199)
# Kate's "Settings" menu bar action, should be like the rest of applications... the "Settings" should be at the bottom, Configure Shortcuts is above, and Configure Toolbars is above that. Image: http://is.gd/ptqI (sreich)
# KMail: review sort order and aggregation mode settings (the two little icon buttons at the top right). Currently a bit confusing. Problem 1: The meaning of buttons/icons itself. Problem 2: The meanings of labels are unclear e.g. "Current Activity". Problem 3: changing it for one folder always changes the default too.

==About the Usability Meetings==

We will discuss practical usability-related issues and attempt to reach reach a resolution. Usability topics which are too large or too broad may be too much to discuss in a single meeting and should be broken up into smaller issues or schedule a dedicated meeting.

Meetings are structured and attempt to follow a preset agenda. There is a meeting leader/moderator (probably seele) who will control the flow of discussion to help keep the meeting on track.

Meeting format is as follows: An agenda item will be presented, describing the problem and a proposed solution. If the item was suggested by someone in particular, they will be asked to provide additional information about the problem. Those in attendance will then be able to discuss the issues in the problem. The meeting moderator will attempt to keep the meeting on track of the topic.

Meetings are normally at 20UTC, alternating weekday and weekend days. Meetings will last no longer than 2 hours. If we do not get through the list in 2 hours, the topics will be covered in the next meeting. If we get through the list in < 2 hours and people are still responsive, we will possibly add an additional topic from the main meeting topics list if the people necessary for discussion are in attendance.

Projects/Usability/Meetings

2009-04-27T12:52:37Z

Seele:

This is the planning page for KDE Usability Project meetings on #kde-usability on irc.freenode.org. The purpose of the meetings is to '''Get Usability Stuff Done'''. These meetings are free for anyone to listen in on; however, they are mostly for designers and developers. For more information scroll and read About the Usability Meetings.

==Next Meeting in May ==

There will be no meeting in April. The next meeting will be Wednesday May 13 2009 at 20:00 UTC in #kde-usability.

==Previous Meetings==

* [[Projects/Usability/Meetings/2009March18|2009 March 18]]
* [[Projects/Usability/Meetings/2009Feb21|2009 Feb 21]]

===Meeting Topics===

Add meeting topics you would like to discuss. Not all of the topics will be able to be covered in a single meeting and so might be deferred until later. Please include your name/irc nick and a link to a project page or bug.

# KWin: Placement policy 'Remember' ([http://bugs.kde.org/show_bug.cgi?id=15329 Bug 15329])
# To which menu entry we should add icons, and to which one we shouldn't add icons. ( Possible UI case could by Qt application Kadu Instant Messenger: 1) http://tinyurl.com/menukadu , 2) http://tinyurl.com/menucontacts , 3) http://tinyurl.com/menuhelp2 , 4) http://tinyurl.com/menucontext2 [Too many icons] )
# Desktop Settings Dialog: Review its usability (Anne-Marie Mahfouf)
## Improve Desktop Theme: Customized (works with Desktop Theme Details kcm from System Settings)
## Add SlideShow effects options: where, how
# Amarok 2 general usability <-- Probably have a separate meeting for this
# Get hot new stuff: Paginator (currently, can't view or install any stuff).
# Make often used/primary actions (e. g. "empty trash") more prominent. NSaibot
# KDE4 KMail 1.11.1 doesnt store column order ([http://bugs.kde.org/show_bug.cgi?id=186841 Bug 186841]).
# lots of drawing glitches, mostly in tray
# DragonPlayer general usability
# Quit should exit totally the application? ([https://bugs.kde.org/show_bug.cgi?id=180466 Bug 180466]) Can this bug be closed?
# problems with small screens (netbooks): mainly kde-pim is not prepared for small screens like the eeepc one (some places with no scrollbar for example).
# Copy dialog start / stop buttons inoperative when panel is locked (https://bugs.kde.org/show_bug.cgi?id=183446)
# 'Full Screen' option should really be in the 'View' menu (https://bugs.kde.org/show_bug.cgi?id=106807)
# no option should require good reflex and/or mouse handling skills (https://bugs.kde.org/show_bug.cgi?id=125208)
# No indication of currently focused area (https://bugs.kde.org/show_bug.cgi?id=187537)
# Wish: Folder Icon indicates empty folder (https://bugs.kde.org/show_bug.cgi?id=153199)
# Ability to place a toolbar on the right of the menu bar (https://bugs.kde.org/show_bug.cgi?id=169043)
# Separate fonts for different languages (https://bugs.kde.org/show_bug.cgi?id=14496)
# KDE errors: Option for non-translated English version (https://bugs.kde.org/show_bug.cgi?id=170664)
# Resize windows based on drag location (https://bugs.kde.org/show_bug.cgi?id=182069)
# (Line to) indicate previous page boundary when scrolling a document (https://bugs.kde.org/show_bug.cgi?id=93196)
# Wish: Delete shows size/contents (https://bugs.kde.org/show_bug.cgi?id=156249)
# Add any button to toolbar (https://bugs.kde.org/show_bug.cgi?id=147372)
# Analog clock difficult to read with dark theme (https://bugs.kde.org/show_bug.cgi?id=165199)
# Kate's "Settings" menu bar action, should be like the rest of applications... the "Settings" should be at the bottom, Configure Shortcuts is above, and Configure Toolbars is above that. Image: http://is.gd/ptqI (sreich)

==About the Usability Meetings==

We will discuss practical usability-related issues and attempt to reach reach a resolution. Usability topics which are too large or too broad may be too much to discuss in a single meeting and should be broken up into smaller issues or schedule a dedicated meeting.

Meetings are structured and attempt to follow a preset agenda. There is a meeting leader/moderator (probably seele) who will control the flow of discussion to help keep the meeting on track.

Meeting format is as follows: An agenda item will be presented, describing the problem and a proposed solution. If the item was suggested by someone in particular, they will be asked to provide additional information about the problem. Those in attendance will then be able to discuss the issues in the problem. The meeting moderator will attempt to keep the meeting on track of the topic.

Meetings are normally at 20UTC, alternating weekday and weekend days. Meetings will last no longer than 2 hours. If we do not get through the list in 2 hours, the topics will be covered in the next meeting. If we get through the list in < 2 hours and people are still responsive, we will possibly add an additional topic from the main meeting topics list if the people necessary for discussion are in attendance.

Projects/Usability/Meetings

2009-03-20T14:36:25Z

Seele: rearranged items

This is the planning page for KDE Usability Project meetings on #kde-usability on irc.freenode.org. The purpose of the meetings is to '''Get Usability Stuff Done'''. These meetings are free for anyone to listen in on; however, they are mostly for designers and developers. For more information scroll and read About the Usability Meetings.

==Next Meeting in April ==

The next meeting will be some time in April.

==Previous Meetings==

* [[Projects/Usability/Meetings/2009March18|2009 March 18]]
* [[Projects/Usability/Meetings/2009Feb21|2009 Feb 21]]

===Meeting Topics===

Add meeting topics you would like to discuss. Not all of the topics will be able to be covered in a single meeting and so might be deferred until later. Please include your name/irc nick and a link to a project page or bug.

# KWin: Placement policy 'Remember' ([http://bugs.kde.org/show_bug.cgi?id=15329 Bug 15329])
# To which menu entry we should add icons, and to which one we shouldn't add icons. ( Possible UI case could by Qt application Kadu Instant Messenger: 1) http://tinyurl.com/menukadu , 2) http://tinyurl.com/menucontacts , 3) http://tinyurl.com/menuhelp2 , 4) http://tinyurl.com/menucontext2 [Too many icons] )
# Desktop Settings Dialog: Review its usability (Anne-Marie Mahfouf)
## Improve Desktop Theme: Customized (works with Desktop Theme Details kcm from System Settings)
## Add SlideShow effects options: where, how
# Amarok 2 general usability <-- Probably have a separate meeting for this
# Get hot new stuff: Paginator (currently, can't view or install any stuff).
# Make often used/primary actions (e. g. "empty trash") more prominent. NSaibot
# KDE4 KMail 1.11.1 doesnt store column order ([http://bugs.kde.org/show_bug.cgi?id=186841 Bug 186841]).
# lots of drawing glitches, mostly in tray
# DragonPlayer general usability
# Quit should exit totally the application? ([https://bugs.kde.org/show_bug.cgi?id=180466 Bug 180466]) Can this bug be closed?
# problems with small screens (netbooks): mainly kde-pim is not prepared for small screens like the eeepc one (some places with no scrollbar for example).
# Copy dialog start / stop buttons inoperative when panel is locked (https://bugs.kde.org/show_bug.cgi?id=183446)
# 'Full Screen' option should really be in the 'View' menu (https://bugs.kde.org/show_bug.cgi?id=106807)
# no option should require good reflex and/or mouse handling skills (https://bugs.kde.org/show_bug.cgi?id=125208)
# No indication of currently focused area (https://bugs.kde.org/show_bug.cgi?id=187537)
# Wish: Folder Icon indicates empty folder (https://bugs.kde.org/show_bug.cgi?id=153199)
# Ability to place a toolbar on the right of the menu bar (https://bugs.kde.org/show_bug.cgi?id=169043)
# Separate fonts for different languages (https://bugs.kde.org/show_bug.cgi?id=14496)
# KDE errors: Option for non-translated English version (https://bugs.kde.org/show_bug.cgi?id=170664)
# Resize windows based on drag location (https://bugs.kde.org/show_bug.cgi?id=182069)
# (Line to) indicate previous page boundary when scrolling a document (https://bugs.kde.org/show_bug.cgi?id=93196)
# Wish: Delete shows size/contents (https://bugs.kde.org/show_bug.cgi?id=156249)
# Add any button to toolbar (https://bugs.kde.org/show_bug.cgi?id=147372)
# Analog clock difficult to read with dark theme (https://bugs.kde.org/show_bug.cgi?id=165199)

==About the Usability Meetings==

We will discuss practical usability-related issues and attempt to reach reach a resolution. Usability topics which are too large or too broad may be too much to discuss in a single meeting and should be broken up into smaller issues or schedule a dedicated meeting.

Meetings are structured and attempt to follow a preset agenda. There is a meeting leader/moderator (probably seele) who will control the flow of discussion to help keep the meeting on track.

Meeting format is as follows: An agenda item will be presented, describing the problem and a proposed solution. If the item was suggested by someone in particular, they will be asked to provide additional information about the problem. Those in attendance will then be able to discuss the issues in the problem. The meeting moderator will attempt to keep the meeting on track of the topic.

Meetings are normally at 20UTC, alternating weekday and weekend days. Meetings will last no longer than 2 hours. If we do not get through the list in 2 hours, the topics will be covered in the next meeting. If we get through the list in < 2 hours and people are still responsive, we will possibly add an additional topic from the main meeting topics list if the people necessary for discussion are in attendance.

Projects/Usability/Meetings/2009March18

2009-03-18T22:02:52Z

Seele:

Meeting theme: Usability Bugs!

=== Proposed window bar layout (part of Bug 187233) ===

* Bug: https://bugs.kde.org/show_bug.cgi?id=187233
* Proposed layout: http://bugi.oulu.fi/~slougi/files/dolphin.png
* Action: slougi to write script to allow users to switch between their current and proposed window bar layouts, so we can test lots of users
* Action: slougi to organize meeting with KWin folks to review other issues

===Make often used/primary actions (e. g. "empty trash") more prominent===

* Issue: In context and menubar menus, the most common actions could be more prominently displayed to help users more quickly identify them, and to help them make a decision
* Action: NSaibot to coordinate with others and come up with mockups/screenshots of different design ideas to be discussed at the next meeting.

=== Konqueror's "save password" dialog is unintuitive ===

* Bug: https://bugs.kde.org/show_bug.cgi?id=168060
* I think this is in progress, I've seen new screenshots recently

=== Keyboard's "Super" key doesn't launch Kmenu ===

* Bug: http://bugs.kde.org/show_bug.cgi?id=154564
* Issue: Cannot launch Kmenu from single key because the System key is a modifier. Needs to be fixed at the kdelibs level (kdeui/dialogs/kshortcutsdialog.cpp?).
* Action: seele to contact mjansen to discuss problem

===Select/enter newly created folder/file automatically===

* Bug: http://bugs.kde.org/show_bug.cgi?id=155706
* Proposal: When a new folder is created, the user should automatically be entered in to the new folder.
* Resolution: On new folder creationg: Dolphin selects folder, File Save enters folder. New folder functionality will be removed from File Open.
* sreich to discuss with dfaure and submit patch

Projects/Usability/Meetings/2009March18

2009-03-18T21:12:34Z

Seele: New page: Meeting theme: Usability Bugs! === Proposed window bar layout (part of Bug 187233) === * Bug: https://bugs.kde.org/show_bug.cgi?id=187233 * Proposed layout: http://bugi.oulu.fi/~slougi/f...

Projects/Usability/Meetings/ActionItems

2009-03-18T19:55:53Z

Seele: Tracking page for usability meeting action items

==2009 Feb 21==

seele will write a draft guideline proposal for moving the toolbar visibility option to View, and splitting the options in Window and removing Window. She will send it to the kde-core-devel and kde-usability mailing lists for comment before committing.
No progress, hopefully by the end of March.

Plasma team is working on system tray and will address the behavior issue
In progress, expected for 4.3

agateau is to look at some applications he was concerned with and propose merging smaller toolbars together
http://techbase.kde.org/User:Agateau/TooManyToolbars

seele and agateau will look at the merges and create guidelines on how to create better toolbar groupings
In progress, depends on agateau's review

colomar and agateau will work on improving the toolbar configuration UI
Started discussions...

seele to contact jwhiting about GHNS
Spoke with jwhiting, said descriptions are fixed in SVN

colomar is working with agateau on the toolbar configuration UI and will use one of the patterns as a test, and see if they can develop a class for it.
No status update

Projects/Usability/Meetings

2009-02-22T23:34:46Z

Seele:

Projects/Usability/Meetings/2009Feb21

2009-02-22T23:34:12Z

Seele: added meeting summary/notes

The KDE Usability Project meeting took place on Feb 21 2009 at 20UTC and lasted for 1 hour 40 minutes. We discussed 5 agenda items which primarily had to do with HIG topics.

The following is a summary of meeting items discussed and their resolutions:

===Menubar: Settings vs. View menus and where to put toolbar visibility===
This discussion is about the current location of the toolbar visibility option, currently in Settings, and the proposal for moving that option to View. The discussion expanded to discuss the purpose of the View, Settings, and Window menus. Details of the discussion can be found in the meeting transcript.

'''Resolution'''
* Toolbar visibility will be moved to the View menu.
* The purpose of the Window menu was discussed and decided that it should be removed. Functionality should be split between the File and View menu, a la Dolphin
* It was also noted that some applications put statusbar, menubar, panel, etc. visiblity options in Window or Settings (e.g. Kopete). This is incorrect and all of these options should always reside in the View menu.

'''Actions'''
* seele will write a draft guideline proposal for moving the toolbar visibility option to View, and splitting the options in Window and removing Window. She will send it to the kde-core-devel and kde-usability mailing lists for comment before committing.

===System Tray: Default action of service icons===
There were some concerns about the behavior clicking on an application service icon in the systemtray. Applications are inconsistent, some will always bring the application to the foreground, others will toggle visibility in the taskbar regardless if it is in the foreground, background, or other desktop. Details of the discussion can be found in the meeting transcript.

'''Resolution'''
* Many of these problems should be resolved with the new system tray in 4.3

'''Actions'''
* Plasma team is working on system tray and will address the behavior issue

===Proposed guideline: "most applications should have only one toolbar"===
Some people had concerns about the number of individual toolbars in applications. We discussed the usability problems of toolbars and the proposal that applications should only have one toolbar that users can configure. Details of the discussion can be found in the meeting transcript.

'''Resolution'''
* It was agreed that some toolbars were in too many pieces which made it easy for users to accidentally create strange toolbar layouts
* Having a single toolbar would make it more difficult for users to customize their toolbars
* It made sense that some toolbars were probably in too small groping and so instead of a single toolbar, it might make more sense to have larger toolbar groupings
* Also, the toolbar configuration UI wasn't so great and could use improvement
* The suggestion of making sure toolbars are locked by default was also made

'''Actions'''
* agateau is to look at some applications he was concerned with and propose merging smaller toolbars together
* seele and agateau will look at the merges and create guidelines on how to create better toolbar groupings
* colomar and agateau will work on improving the toolbar configuration UI

===Get hot new stuff: Should description text be wrapped?)===
It was noted that the description in the GHNS UI is on a single line, and in order to read the entire description, you have to stretch the window. Details of the discussion can be found in the meeting transcript.

'''Resolutions'''
* Everyone agreed this is a valid issue and up to 3 wrapped lines would be an improvement

'''Actions'''
* seele to contact jwhiting about GHNS

===KDE design patterns: Are they known/useful/being used?===
Several design patterns were developed and proposed during the 2008 Season of Usability. The people who worked on the patterns wanted to see if they were useful for developers and if standardized classes could be created.

'''Actions'''
* colomar is working with agateau on the toolbar configuration UI and will use one of the patterns as a test, and see if they can develop a class for it.

==Meeting Transcript==
[20:03:39] <seele> ok, let's get this party started

[20:03:55] <seele> welcome to what i hope will become a productive and regular activity: kde usability project meetings

[20:04:11] <DreadKnight> :)

[20:04:34] <seele> my goal for these meetings are to work on specific design and usability problems

[20:04:50] <seele> and hopefully reach a conclusion or action item at the end

[20:04:59] <seele> there is a wiki page with some meeting ideas: http://techbase.kde.org/Projects/Usability/Meetings

[20:05:01] --> eean (n=ian@amarok/developer/eean) has joined #kde-usability

[20:05:04] <leinir> present

[20:05:19] -*- Nightrose will get something to eat and then join in

[20:05:24] <seele> there are several HIG-related issues, a few bugs, and then some larger design problems

[20:05:43] <seele> for this first meeting i want to talk about a few of those HIG problems and the bug issues and save the larger design problems

[20:05:58] <Peter007> erm...

[20:06:01] <seele> i think a few people couldnt make it for a saturday evening. next time we will do it in the middle of the week

[20:06:13] <seele> Peter007: question?

[20:06:16] <Peter007> yes

[20:06:28] <Peter007> could we begin with a outline of the irc itself

[20:06:37] <Peter007> the meeting format etc

[20:06:38] --> mpyne (n=kde-svn@kde/mpyne) has joined #kde-usability

[20:06:46] <DreadKnight> agree

[20:06:47] --> vandenoever (n=vandenoe@ip5657eb5b.direct-adsl.nl) has joined #kde-usability

[20:06:48] <seele> right, getting to that

[20:07:05] <seele> so for this meeting, i'm going to act as moderator/meeting master to keep discussions on track.

[20:07:09] <DreadKnight> perhaps wait 5 more minutes? people usually are a bit late on stuff

[20:07:25] <seele> the meeting wont last longer than 2 hours, esepcially since it is late on the other side of the pond

[20:07:28] <eean> in the 5 minutes seele can get the meeting started :)

[20:07:37] <DreadKnight> ok

[20:07:47] <seele> for each of these issues, i will list the issue, and any pros/cons/other information necessary for discussion

[20:07:50] --> nixternal (n=nixterna@ubuntu/member/nixternal) has joined #kde-usability

[20:08:06] <nixternal> thanks aseigo for the heads up there :)

[20:08:13] <seele> also, if there is a particular developer who is concerned about the issue in particular, or had listed the meeting topic they will be able to contribute any missing information

[20:08:25] <DreadKnight> you miss all the good stuff if you don't follow me on twitter :P

[20:08:45] <seele> if it seems like there is not enough information to maintain a useful discussion, or the problem itself is too big to discuss on IRC, i will defer it

[20:09:00] <aseigo> nixternal: yay for identi.ca huh? ;)

[20:09:06] <nixternal> yup :)

[20:09:07] -*- lfranchi says thank you seele for your iron fist

[20:09:10] <aseigo> DreadKnight: boo hiss on twitter ;)

[20:09:19] <seele> lfranchi: lol

[20:09:24] <seele> it wont be that bad

[20:09:31] <seele> but having some rules will help make the meeting more productive

[20:09:35] <lfranchi> i wasn't kidding

[20:09:43] <lfranchi> seriously, thank you, it is needed in IRC meetings :P

[20:09:48] <seele> if it is obvious we arent going anywhere, it is better to move on to an easier problem so *something* gets done

[20:09:48] <eean> unrun irc meetings suck

[20:09:50] <DreadKnight> i use kdetwitter... since it's not trunk i don't have identi.ca support, aseigo; and choqok is useless with it as well

[20:09:56] <seele> lfranchi: thank me after.. who knows how this will go..

[20:10:29] <Peter007> will the meetings be logged?

[20:10:36] <seele> so.. anyone else missing? i know agateau and annma couldnt make it today and they had two issues

[20:10:40] <seele> Peter007: are you volunteering?

[20:10:45] <-- mpyne (n=kde-svn@kde/mpyne) has left #kde-usability

[20:10:55] <Peter007> heh, I can bearly type on irc

[20:10:56] <seele> to start, if someone could volunteer to log and post the meeting to the wikipage, that would be very helpful

[20:11:15] <seele> anyone? *crickets*

[20:11:18] <DreadKnight> seele: it will go just great :) i'm sure of it

[20:11:37] <lfranchi> seele: sure

[20:11:40] <lfranchi> quassel logs it anyway

[20:11:48] <seele> lfranchi: thanks for volunteering

[20:11:52] <lfranchi> np

[20:12:02] <seele> ok, let's get started

[20:12:03] <seele> http://techbase.kde.org/Projects/Usability/Meetings

[20:12:04] --> fredrikh (n=fredrik@kde/fredrik) has joined #kde-usability

[20:12:26] <seele> the first issue is a long running discussion on the kde-usability mailing list

[20:12:40] <seele> View vs Settings in the menubar, and what should go in them

[20:12:49] <seele> specifically, where does the toolbar toggle option go

[20:12:57] <seele> i've written up more information about this issue here: http://techbase.kde.org/Projects/Usability/HIG/Menu_Bar/View_Menu

[20:13:07] <seele> The option to toggle the visibility of toolbars is currently in the Settings menu. There have been several discussions over the years about whether toolbar visibility should be in Settings or View. One of the arguments is that the configuration option for configuring toolbars resides in the Settings and so the two related options should be together. However, there are several arguments for why toolbar visibility should be in View.

[20:13:22] <seele> Conceptually, toolbars are "window elements", the same as menubar, statusbar, and panels in a window. These other window elements currently reside in the View menu. This is important to note for two reasons. One, it establishes that View seems to be a logical place to put this type of configuration options. Two, since toolbars are conceptually similar to the mentioned window elements. Users will think of them as the same and use what they have learned with

[20:13:29] <seele> Also, non-KDE applications which are often coinstalled with KDE applications, such as Firefox and OpenOffice, place the toolbar visibility controls in the View menu. The argument is not that Firefox and OpenOffice do it the "right way", simply that an added benefit of changing KDE toolbar visibility to View would increase consistency with non-KDE applications, and improve the overall experience.

[20:13:39] <seele> [end]

[20:13:52] <seele> the proposal i would like to discuss is to move the toolbar toggle option to the view menu

[20:14:02] <seele> i will give everyone a few minutes to read the arguments

[20:14:11] <eean> (thinks toolbars shouldn't be toggable :P)

[20:14:18] <seele> feel free to speak up why or why not you think moving the option to view is a good idea

[20:14:27] <Nightrose> eean: yes they should!

[20:14:34] <seele> eean: removing the functionality is not up for discussion

[20:14:35] <Nightrose> i don't need a toolbar in quassel for example

[20:14:49] <Nightrose> and it wastes a lot of space on the eeepc

[20:14:55] <seele> where the functionality goes, View or Settings is what we are talking about

[20:14:56] <eean> quassel doesn't have one

[20:15:00] <Nightrose> it does

[20:15:19] <DreadKnight> i think the menu bar is overated and too 70's

[20:15:21] <Nightrose> seele: i vote for view but it is mostly a gut feeling

[20:15:28] <seele> eean: in 0.4.0 theyve added a toolbar. but let's stay on track

[20:15:44] <DreadKnight> i think the menu bars should be killed, just like in chrome web browser

[20:15:54] <seele> DreadKnight: that isn't up for discussion at the moment either

[20:15:57] <eean> whoa lol

[20:16:14] <eean> yes I agree View makes more sense, for all the reasons you outline there.

[20:16:23] <eean> I mean if you have a 'view' thats what its for

[20:16:26] <Chani> View makes sense to me...

[20:16:27] -*- lfranchi agrees with the View, seems to fit logically

[20:16:28] <leinir> i would vote View, however we then run into the problem that not all the KDE applications have View menus

[20:16:33] <seele> anyone else? in particular does anyone not agree with the proposal?

[20:16:43] -*- aseigo reads...

[20:16:44] <colomar> Just a thought: What if we put a visibility checkbox in the "Configure toolbars" dialog in addition to an item in the view menu?

[20:16:46] <leinir> Kopete and Konversation, for example, both lack that top level menu item

[20:16:50] <lfranchi> leinir: good point

[20:16:51] <Nightrose> leinir: do you know which one doesn't?

[20:16:51] <seele> leinir: can you find some examples and put them on the page?

[20:16:57] <Chani> when I started reading my first thought was 'view'... well, second. the first was 'what happene to right-clicking the toolbar itself?'

[20:17:10] <leinir> Nightrose: Those two in particular, i don't know of any others :)

[20:17:12] <Peter007> I'm not in favour, the toolbars don't change as often as views and whatever non-kde apps do, they shold to kde, not the other way

[20:17:16] <Nightrose> k

[20:17:17] <aseigo> konversation doesn't have a view menu (he says looking at the app he's in) (doesn't have a toolbar either..)

[20:17:18] <lfranchi> colomar: checkbox to enable a toggle in a menu?

[20:17:27] <lfranchi> colomar: that seems like option overkill imho :)

[20:17:36] <colomar> no

[20:17:37] <seele> lfranchi: i think he means putting the option in two places

[20:17:42] <colomar> yes

[20:17:43] <leinir> aseigo: by default, though it does have a toolbar (i use it :) )

[20:17:46] <lfranchi> oh sorry

[20:17:49] <colomar> np

[20:18:20] <seele> colomar: i think that could be confusing, users might wonder what the difference between the two options are

[20:18:30] <aseigo> so it would mean an extra menu entry in some apps just for toolbars

[20:18:50] <eean> seele: but another user might wonder why they can't hide the toolbar in "configure toolbar" dialog

[20:19:02] <colomar> If they're labeled the same and synchronize automatically they might get it

[20:19:20] -*- Chani likes having more than one way to do it

[20:19:25] <seele> how many of those applications also have visibility settings for the statusbar and menubar? i see kopete doesnt have a View menu, but a lot of options in the settings menu ought to be in a view menu

[20:19:34] <lfranchi> personally i don't like cluttering options

[20:19:41] <Chani> people dont get confused by options that are both on hte toolbar and in a menu

[20:19:53] -*- aseigo notes that there a lot of apps with both a window and a view menu..

[20:20:02] <eean> aseigo: :|

[20:20:03] <seele> so in addition to the toolbar option, there are several additional options which are not categorized consistently in the environment

[20:20:08] <Nightrose> seele: the problem with kopete is probably that they want to keep the number of menues small due to lack of horizontal space

[20:20:08] <Chani> kopete's got a scary amount of settings, iirc ;)

[20:20:29] <aseigo> Nightrose: yes

[20:20:32] -*- DreadKnight thinks kopete is the mosts ugly app from kde

[20:20:38] <DreadKnight> *

[20:20:43] -*- Nightrose loves kopete ;-)

[20:20:46] <seele> Nightrose: the first half of their settings menu has options which are normally in a view menu too :-/

[20:20:59] -*- aseigo frowns at DreadKnight wondering what the deal is there

[20:21:31] <seele> so there seems to be yet a larger issue here, inconsistency in element visibility options

[20:21:58] <seele> there are three things we can consider:

[20:22:09] <aseigo> Nightrose: i don't think a View menu would be a horizontal burden in kopete, looking at it now

[20:22:18] <seele> 1) dont do anything about it <-- not in favor of this because inconsistency makes me itch and it reduces discoverability and learnability

[20:22:34] <seele> 2) Force apps without a View menu to use a view menu and put the proper items in there

[20:22:44] <Nightrose> aseigo: mine is wide enough for adding a view as well - dunno

[20:22:49] <seele> 3) Come up with a different solution, such as moving visiblity of window elements to Settings instead

[20:23:24] <Chani> of the apps that don't have a view menu, how many don't have one because they're abusing Settings instead?

[20:23:26] <aseigo> seele: well, 3 would be difficult for apps like onqueror

[20:23:31] <seele> the View label is very strong, and so I still think it is a good place to put elements you can toggle the visibility for, but obviously we have to consider the apps which dont have a view menu

[20:23:36] <seele> aseigo: yes

[20:23:37] <DreadKnight> why do you guys want to hang on to a 70's crappy concept while you revolutionize the rest of the desktop? "all obey HIG"?

[20:23:41] <leinir> i would most likely be for a better designed Settings menu... Make all settings (visibility, feature toggles...) sit in a Settings menu, and all other menus are feature activation

[20:23:42] <aseigo> seele: everything in its view menu could be viewed as a setting, really

[20:23:47] <seele> DreadKnight: please stay on topic or get out

[20:24:20] <aseigo> seele: so i don't think #3 is an option, tbh

[20:24:47] <seele> aseigo: that's fine and i agree

[20:25:01] <aseigo> seele: #2 is plausible, just means some work to be done ... note that the default location of the toolbar settings is actually set in kdelibs

[20:25:13] <aseigo> so for most apps it should be a fairly simple matter really

[20:25:18] <aseigo> (changing it in one place)

[20:25:26] <aseigo> then it would down to hunting all the apps that put it there manually (if any)

[20:26:09] <aseigo> personally i'm torn between the View and Window menus we have as well. there needs to be clear definitions laid down for each of the three menus; View, Settings and Window

[20:26:28] -*- Chani never uses the Window menu and isn't really sure what it's for

[20:26:42] <eean> kubuntu gets rid of the window menu

[20:26:43] <aseigo> Chani: tabs and splitting windows

[20:26:44] <seele> aseigo: can you give me an example of a window app? i dont have one option and cant think of one

[20:26:53] <eean> konqueror

[20:27:04] <aseigo> eean: so where are the split window options?

[20:27:07] <Chani> hmm. some of that stuff is duplicated in File

[20:27:16] <aseigo> seele: konqueror, konversation

[20:27:22] <eean> aseigo: I guess they didn't have them

[20:27:27] <eean> (not sure what they're doing now)

[20:27:41] <seele> ah, yes.. the window layout and tabs do make sense in window..

[20:27:45] <eean> konqueror has *a lot* of menu items. but this is off topic :)

[20:27:49] <seele> aseigo: so that would mean dolphin would get a window menu?

[20:27:56] <aseigo> eean: which is sort of a problem, yes? ;)

[20:28:25] <seele> well, currently view holds some of these "window" options as well

[20:28:38] <seele> so if we define view we might have to define window too

[20:28:42] <colomar> But at least in Konversion those are not toggles (all but "Enable notifications, which I htink should go somewhere else anyway)

[20:28:57] <eean> konqueror has some crazy stuff in the 'view' menu, include 'reload'.

[20:28:59] <Peter007> Setttings are used to set app, which affects the features and functions (i.e. toolbars), while view affects the content (find, zoom)

[20:29:23] <seele> Peter007: statusbar, panels, and menubar visibility is in View

[20:29:25] <Chani> hmm. all dolphin's panels stuff (and in my mind panels and toolbars are nearly the same) is in View. along with the split-window action (but dolphin does have much simpler splitting)

[20:29:44] <seele> and i think toolbars are perceived as the same type of window element as those mentioned, so they need to stay together

[20:29:49] <Peter007> seele: maybe they shouldn't be either

[20:30:02] <Nightrose> (hmm my konqueror on kubuntu has a window menu)

[20:30:42] <Peter007> if we keep the view clean from non content elements, we can populate it with more content orientated ones

[20:30:57] <seele> Peter007: i dont think toggling the visibility of a windowing element is on the same level as actively configuring something

[20:31:27] <seele> also, i really think users go to view before they go to settings when they think to turning off window elements like that

[20:31:29] <eean> Nightrose: its probably just changed, I was remembering from kubuntu circa kde3

[20:31:38] <Nightrose> ah k

[20:31:48] <Peter007> seele: I'm thinking about the frequency of change, the settings is seldom changed, but views more often

[20:32:28] <seele> Peter007: i dont know if everyone makes that specific distinction between the two, and also, i'm not sure what your point is

[20:32:50] <-- aseigo (n=aseigo@kde/aseigo) has quit (Read error: 54 (Connection reset by peer))

[20:32:53] <seele> toggling the status bar or menu bar should be something you can do quickly, and probably do more often than configuring an application once the first time you use it

[20:33:06] --> Godot (n=jasper@f051038051.adsl.alicedsl.de) has joined #kde-usability

[20:33:07] <Peter007> my point is the frequently used functions should be on view, the less on settings, users prefer view

[20:33:13] --> aseigo (n=aseigo@kde/aseigo) has joined #kde-usability

[20:33:29] <aseigo> gah

[20:33:35] <aseigo> what was the last thing the channel got from me?

[20:33:37] <colomar> Seems to me that Peter007 and seele actually share the same opinion, right?

[20:33:51] <seele> aseigo: 15:24 < aseigo> eean: which is sort of a problem, yes? ;)

[20:34:02] -*- aseigo sighs

[20:34:12] <seele> colomar: i think they happen to intersect but not for the same reasons :0

[20:34:16] <aseigo> seele: well ... i don't know. the "New Window", "New Tab" entries seem to be in both the File and the Window menus...

[20:34:22] <aseigo> (in other apps, that is)

[20:34:27] <aseigo> it's things like moving tabs around, splitting the window... meh

[20:34:30] <aseigo> in dolphin it treats splitting as part of the view

[20:34:36] <aseigo> and puts tabs with new window in File

[20:34:40] <aseigo> which also makes sense

[20:34:45] <aseigo> konqueror's Window menu could probably be split up and merged into File and View

[20:34:59] <aseigo> and konversation's Window menu could probably become View

[20:35:03] <seele> ok, so in that case we shouldnt use konqueror as a model to look in to

[20:35:08] <Peter007> hmm, usually the toolbars are setup once, but views more often, your point fast access is taken

[20:35:20] <seele> the way dolphin does it by splitting up the options is what we should use as example

[20:35:38] <seele> Peter007: i dont agree, especially with netbook users

[20:35:42] <eean> seele: its an example of why a HIG is needed :)

[20:35:53] <seele> they may toggle toolbars on and off in order to get an extra line or two of text

[20:36:03] <seele> but them might need the toolbars to work on something

[20:36:12] <aseigo> seele: probably; killing of the Window menu in the process of defining View properly would probably a good idea imho

[20:36:32] <seele> aseigo: noted. i'll use dolphin as the example for organizing the options in to File and View, yes?

[20:36:48] <Chani> cool.

[20:37:02] -*- seele makes a note

[20:37:04] <Chani> the ones that belong in file are already there anyways, just stop duplicating them :)

[20:37:15] <Peter007> seele: essentially that kind of toggling exposes another problem toolbars were not designed to solve

[20:37:39] <aseigo> seele: sounds good

[20:37:50] <Chani> hrm, n/m, only two are duplicatd

[20:38:20] <seele> Peter007: regardless, this issue has come up over the past few years because experienced users have failed to remember that toolbars are in Settings, not View and continually make mistakes

[20:38:37] -*- Chani nevr uses the menu options for tabs, there are easier ways, like keyboard shortcuts and buttons and doubleclicking and dragging

[20:38:47] <seele> this is because you have a very active label "View" and within it related options, that's probably why the error occurs

[20:39:27] <DreadKnight> i added a button for new tab in dolphin

[20:39:29] -*- Chani actually hardly ever uses menus at all. I used to hide all hte ones that would let me, buut that's too buggy in kde4 and my screen's not as cramped

[20:39:33] <seele> i'm not suggesting we change something for the sake of changing it, people are making mistakes. that is a very real reason to fix something

[20:39:39] <Peter007> hmm, I don't see that as a problem with the design, or HIG

[20:40:05] <Peter007> I see that as a lack of standardisation

[20:40:20] <seele> Peter007: i'm still not sure what you mean

[20:40:35] <seele> all kde apps have the toolbar visibility option in settings

[20:40:37] <Peter007> Some toolbars are in view, others who knows?

[20:40:41] <seele> no

[20:40:47] <seele> afaik there are no toolbar options in veiw

[20:40:50] <seele> however that brings up another point

[20:40:54] <Peter007> firefox

[20:41:02] <seele> firefox and openoffice, two very popular open source applications, put toolbars in view

[20:41:07] <seele> Peter007: yes, getting to that

[20:41:12] <Peter007> heh

[20:42:06] <seele> so following what they do just for the sake that it is firefox and openoffice is not what i suggest, nor do i think we should change the option just because we can't change the option in firefox and openoffie

[20:42:09] <aseigo> while i'm cool with that argument in this case, since it's not something that moves around much and makes sense for other reasons as well, following other app's guidelines isn't great

[20:42:22] <seele> yes i agree

[20:42:23] <aseigo> seele: :)

[20:42:39] <seele> that's why i didnt bring it up until now

[20:42:48] <seele> (although i think it is on the wiki page)

[20:42:50] -*- eean thinks following other apps makes a lot of sense when its somewhat arbitrary anyways

[20:43:03] <Peter007> I don't think the HIG can reach into other apps, so there will always be this kind of situation

[20:43:16] <seele> Peter007: i wasn't suggesting changing those apps, they have nothing to do with kde

[20:43:28] <seele> this is simply for kde

[20:43:50] <seele> regardless of what the option apps do, i still think it would be good to group all of the similar objects together and put them in the same place

[20:44:03] <Peter007> I understand, my point is, that where other apps change other things, exp users will again make mistakes

[20:44:03] <seele> and i think toolbars go with the menubar, statusbar, panels, etc.

[20:44:24] <seele> Peter007: relearning and cognitive dissonance are two different issues

[20:44:41] <seele> relearning is a small cost, having something in a place that doesnt make sense is a higher cost

[20:45:04] <seele> so this discussion is also dragining on

[20:45:07] <Peter007> Sorry, I am questioning the worth of HIG here, based on users exposure to other apps

[20:45:20] <seele> i want to wrap this up in 5 minutes, with or without a solution

[20:45:45] <seele> final comments: who does not think the toolbar visibility option should be moved in to the view menu and why

[20:46:39] <DreadKnight> i think it should be in view... because i go to there if i want to "VIEW" something or stop viewing it; it's going the same way of thinking like kickoff menu

[20:46:47] <seele> ok, so i will take it that either a) people don't care where the option goes or b) they would like it to be in view

[20:46:50] <Peter007> I think should stay, I haven't made the mistakes referred to

[20:47:06] <seele> hmm. next time 3 minutes fo silence instead of 2 :P

[20:47:24] -*- lfranchi votes View

[20:47:35] <seele> anyone else NOT comfortable with the proposed change (and why)

[20:47:40] <DreadKnight> "to view or not to view.... that is the question!"

[20:47:47] <eean> well we're not Quakers we don't have to be in complete agreement :)

[20:48:14] <seele> eean: sure, but it is still good ot know if someone has a good reason not to do something :)

[20:48:40] <seele> ok. Peter007 your opinion is noted, but i think the proposed change will be beneficial, although minor

[20:48:49] <Chani> ok. next item?

[20:48:54] <Peter007> ok

[20:49:01] <seele> i will write up a summary and send it to the kde-core-devel mailing list and followup with whoever needs to make the change

[20:49:17] <seele> Aurelian is not here so we will skip item 2

[20:49:26] <DreadKnight> "Most applications should have only one toolbar"

[20:49:30] <DreadKnight> argh

[20:49:32] -*- Peter007 sighs loudly and lights another ....

[20:49:44] <seele> Item 3: Default actions of service icons (application icons running in the system tray)

[20:50:19] -*- Peter007 coughs and turns red

[20:50:34] <seele> two issues here, we might want to discuss only one

[20:50:55] <seele> the first is what the default behavior should be for all service applications because currently it is not

[20:51:06] <Chani> hmm. the dreaded system tray.

[20:51:07] <seele> however, what i would like to talk about first (which is the second issue) is what happens when you click on the icon

[20:51:34] <seele> currently it acts as a toggle. if the application is in the foreground and you click on the icon, it disappears to the system tray

[20:51:45] <seele> if the application is in the background and you click on the icon, it disappears to the system tray

[20:51:58] <seele> if the application is in the system tray and you click on the icon, it appears in the foreground

[20:52:15] <seele> a problem with this behavior has presented with our new panels, they can hide

[20:52:34] <Nightrose> also it is inconsistent across apps

[20:52:36] <colomar> Hm since the tray is somewhat standardized by freedesktop.org, isn't that behavior standardized as well?

[20:52:38] <seele> and with the new ideas for the system tray, it is usually more available than the task bar

[20:52:42] <aseigo> colomar: no

[20:52:51] <Chani> seele: are you referring to the systray icons that act as a secondary taskbar for an app with a mainwindow (like kopete), or the systray apps that are their own apps (like rsibreak), or system service ones, or all of them, or what?

[20:52:57] <aseigo> colomar: the only thing standardized in the fd.o spec is how to get an entry into a tray

[20:52:59] <seele> the problem is when the panel is hidden and you dont know if the application is in the task bar or hidden in the systray

[20:53:06] <aseigo> colomar: it says exactly zero about interaction policy

[20:53:18] <aseigo> seele: why does that matter exactly?

[20:53:25] <seele> if you click on the systray icon, if the application is in the taskbar but not in focus, nothing happens visually (the application disappears to the systemtray)

[20:53:39] <Nightrose> seele: you also need to distinguish and think about what happens if you clock

[20:53:41] <Nightrose> *click

[20:53:50] <seele> aseigo: apparently a lot of people click on the systemtray icon twice because they forget/miss that the application is already open in the taskbar

[20:54:05] <seele> because they are hiding panels

[20:54:06] -*- Chani thinks that if you click hte systray icon when the app isn't visible, it should, ideally, become visible somehow.

[20:54:10] <Nightrose> if it were like in amarok it would always come to the foreground no matter if it is in the systray or taskbar

[20:54:19] <Chani> seele: or it's on another desktop?

[20:54:32] <colomar> aseigo: Oh :( Than maybe it should be since it might be confusing to have different icons from different desktop apps behave differently...

[20:54:35] <seele> Chani: that too, i didnt ask about if the problem was another desktop or not

[20:54:40] <faemir> Sorry, what is wrong with if it's in the background then clicking on it brings it to the foreground?

[20:54:44] <Nightrose> Chani: yes that is what amarok does and i think kopete or ktorrent

[20:54:44] <aseigo> seele: ah.. ok.. so this whole conversation needs to shift a little i think.

[20:54:54] <seele> aseigo: i may not have explained it well :)

[20:55:04] <Nightrose> faemir: not all apps do it

[20:55:06] <Nightrose> ;-)

[20:55:06] <seele> faemir: the problem is when it is in the background and you click the icon and it disappears to the system tray

[20:55:08] <aseigo> because it's not a problem that will be solved imho by sticking with the current system

[20:55:14] <seele> faemir: the intent was to bring the application in to focus

[20:55:35] <seele> faemir: so you have to click the icon twice in order to bring the application in to focus

[20:55:51] <aseigo> seele: hm. that's only true if the window is the currently active window, of course

[20:56:12] <aseigo> if it's not the active window or another desktop (same thing really) it makes the window the active window

[20:56:14] <eean> the way amarok does it makes sense to me. clicking on the icon only hides amarok when its the top window. Otherwise its brings amarok forward.

[20:56:26] <aseigo> eean: that's the standard functionality in kdelibs

[20:56:37] <Nightrose> aseigo: try amarok/ktorrent against kopete/skype

[20:56:40] <eean> well this makes sense. I guess I miss what the problem is?

[20:56:41] <Chani> oh, that's already standard?

[20:56:44] <seele> aseigo: for kopete it always brings it to the foreground. for kmail it toggles the taskbar

[20:56:53] <eean> oh I see

[20:57:02] <eean> well people should be like amarok/ktorrent :)

[20:57:07] <Chani> ok, so kmail is doing it wrong

[20:57:14] <leinir> The biggest problem i've run into with this is the icons for the elements in Kontact

[20:57:15] <DreadKnight> i really like how apple guys unified shortcuts with open applications and system tray....

[20:57:36] <DreadKnight> an easier to understand concept for the average people...

[20:57:39] <leinir> (in particular akregator and kmail)

[20:57:42] <seele> so this is more of a verification so something can get written down

[20:58:13] <seele> If you click on the systemtray icon, if an application is not in the foreground it should appear in the foreground, regardless if it is hidden, on another desktop, or in the background?

[20:58:20] <seele> does this make sense? are there any cases where it wouldnt?

[20:58:23] <eean> seele: yes

[20:58:28] <Peter007> If the window is focused it should hide, otherwise focus

[20:58:33] <Nightrose> makes sense to me

[20:58:40] <seele> this seems like the most favored behaviro, but there are some apps which do not do this so i would like to write it down

[20:58:47] --> kuadrosx (n=kuadrosx@190.68.219.168) has joined #kde-usability

[20:58:50] <eean> good plan

[20:59:01] <aseigo> seele: ah, well, yes. that's due to whether the tray icon has an associated parent window or not

[20:59:06] <seele> Peter007: right, so the opposite would be if it is in focus, clicking on the icon will make it disappear to the system tray

[20:59:21] <leinir> Yes, something like "do not override the kdelibs policy on systray icon click"?

[20:59:30] <seele> aseigo: is that something that is fixable or is it a bigger problem?

[20:59:42] <aseigo> seele: and in turn, that's dictated by whether it's the sort of app that's a "service" and which you'd expect to show up whenever you ask for it (e.g. IM), or if it's an application that you really don't want relocating from one desktop to another (kmail)

[20:59:44] <Peter007> seele: ok, head is spinning, correct

[20:59:51] <aseigo> so there's the "bring it to me" scenario an the "take me to it" scenario

[21:00:05] <Chani> hmm.

[21:00:13] <seele> aseigo: ah, good case

[21:00:17] <aseigo> this stems, imho, from the problem that we put all such status icons in the system tray

[21:00:24] <aseigo> really, the "take me to it" icons belong in the taskbar

[21:01:00] <aseigo> if we bolted the system tray and task bar widgets together, we could sort of make that happen now, though it would still lead to false positives (kopete being a good example there)

[21:01:03] <Chani> ok, so when the systray icon is clicked, if the app is open elsewhere you should be taken to it. if the app isn't in hte taskbar at all...

[21:01:04] <Peter007> Actually, my problem is that I don't expect a focused systray item to hide when I click it, I expect it to close

[21:01:21] <aseigo> Peter007: close?

[21:01:28] <eean> o.O

[21:01:35] -*- Chani would be fine with the app reopening on whatever desktop it was last on, and me being taken there to see it

[21:01:38] <Peter007> The only place the window appears is on the systray

[21:01:50] -*- aseigo goes looking for the whiteboard photo of this from tokamak

[21:02:11] <eean> you can't focus systray items

[21:02:11] <aseigo> Chani: even for, say, kmix? :)

[21:02:15] <seele> Peter007: disappear to systray might be what you are thinking of as "close" minimize to the taskbar is what most applications do

[21:02:17] <Peter007> erm, the only icon control is on the systray

[21:02:30] <Chani> aseigo: oh... kmix counts as a window?

[21:02:51] <Peter007> seele: yes, you can minimise, but that isn't a good idea - to me anyway

[21:02:53] <Chani> aseigo: when I click the kmix icon and the little volume slider pops up, I don't think of that as an application...

[21:03:19] <DreadKnight> aseigo: false positives in what way?

[21:03:35] <Peter007> somehow systray items are distinct beasts to normal windows

[21:03:38] <aseigo> DreadKnight: how would it differentiate between kopete and kmail?

[21:03:54] <DreadKnight> aseigo: ever usen mac os?

[21:03:58] <DreadKnight> used*

[21:04:00] <Peter007> They seem always active and therefore no need to minimise

[21:04:06] <aseigo> DreadKnight: yes. why?

[21:04:34] <seele> Peter007: macos has an "always on" policy. applications are never closed or open, they jsut are

[21:05:14] <seele> that is a great idea, but doesnt make sense for the current environment -- yet

[21:05:19] <DreadKnight> aseigo: we can have the icons actually differentiate; running apps for example have a dot or something under them compared to the ones that are not running; we could have a green dot for running ones and a red one for things like kopete like for when receiving a msg.. or just have the icon change like it does now or have it bounce

[21:05:22] <seele> it makes sense when applications can start in a second or two

[21:05:33] <Peter007> to me the systray runs servers, or similar, while taskbar are transitory windows

[21:05:52] <DreadKnight> seele: how come they are never closed? they have a mark in the dock :P

[21:05:53] <seele> but when an app takes longer than a few seconds to load, then the cost of closing is too high, and users begin thinking of resources

[21:06:12] <seele> DreadKnight: if an application is not running, clicking on the application will start it

[21:06:22] <seele> DreadKnight: if an application is running, it will bring you to the open window

[21:06:35] <DreadKnight> seele: yes, it's like a shortcut like a mentioned a while ago

[21:06:52] <DreadKnight> like the silly ubuntu's configuration leaves a lot of room on the top panel for shortcuts

[21:06:59] <Chani> there are also some apps that lose state when you close them. less and less, thankfully

[21:07:10] <DreadKnight> some people don't even make use of that space; makes sense with things like gnome-do etc

[21:07:41] <Chani> so.... where were we going with this?

[21:07:51] <aseigo> hm.. ok, so i can't find the photo atm, but here's a mostly-complete round up:

[21:07:52] <seele> DreadKnight: what is your point? i think moving to an "always on" concept like macosx is beyond the scope of this meeting

[21:07:53] <aseigo> http://techbase.kde.org/Projects/Plasma/NewSystemTray

[21:07:59] <DreadKnight> i say brinde the stuff into a single panel;

[21:08:05] <DreadKnight> bridge* argh

[21:08:07] <aseigo> DreadKnight: that's a completely different issue

[21:08:11] <seele> DreadKnight: and intersting idea, but i dont think here and now is appropriate

[21:08:18] <aseigo> not even related in the least

[21:08:35] <DreadKnight> it's related to the system tray :P

[21:08:46] <aseigo> no, it's not

[21:08:48] <DreadKnight> it's taking one step back and seeing the whole picture

[21:08:53] --> yaroslav__ (n=yaroslav@ool-4355d73d.dyn.optonline.net) has joined #kde-usability

[21:08:58] <Nightrose> seele: let's go on?

[21:09:00] <DreadKnight> :)

[21:09:02] <Peter007> DreadKnight: you want to remove the systray completely?

[21:09:04] <seele> to refocus, we are discussing the behavior of clicking on an icon which happens to be in the systemtray

[21:09:10] <aseigo> you're talking about active launcher icons, or taskbar as launcher, which is not at all related to the tray

[21:09:10] <seele> Nightrose: yest

[21:09:12] <DreadKnight> Peter007: yes

[21:09:18] <aseigo> so: http://techbase.kde.org/Projects/Plasma/NewSystemTray

[21:09:26] <leinir> DreadKnight: It is doing what seele mentioned earlier as "delaying the larger design issues" :)

[21:09:31] <leinir> So, not for tonight :)

[21:09:43] <aseigo> with the new system we're implemnting for 4.3, the idea is to have 4 categories of icons

[21:09:52] <aseigo> Indicators of application status

[21:09:54] <aseigo> Communications

[21:09:55] <aseigo> System services

[21:09:57] <aseigo> Hardware

[21:10:08] <aseigo> app status indicator will move into the taskbar and be associated with their entries there

[21:10:22] <Nightrose> like?

[21:10:28] <DreadKnight> cool

[21:10:30] <aseigo> communication (IM, e.g.) will stay in the tray for now, but hopefully will move into a communications specific area

[21:10:44] <-- yaroslav_ (n=yaroslav@ool-4355c41e.dyn.optonline.net) has quit (Read error: 104 (Connection reset by peer))

[21:10:44] --> yaroslav (n=yaroslav@ool-4355c41e.dyn.optonline.net) has joined #kde-usability

[21:11:07] --> agateau (n=quassel@78.115.12.217) has joined #kde-usability

[21:11:12] <seele> aseigo: ok, so should we punt this issue then? it seems like youre on your way to fixing it in 4.3

[21:11:14] <DreadKnight> i like the areas idea, just hit my mind we could have the panel with just icons, roughly the same size, so only the areas will distinguish them

[21:11:23] <agateau> hello

[21:11:31] -*- Chani forgets what makes communication apps different from other app status icons.

[21:11:34] <agateau> i am very late for the meeting

[21:11:36] <Chani> but anyways...

[21:11:37] <agateau> is it over ?

[21:11:39] <seele> agateau: hi! we can talk about your issue next if you like

[21:11:44] <seele> agateau: no, probably for another hour ;)

[21:11:46] <aseigo> system services will remain in the tray

[21:11:52] <DreadKnight> gimmie project did this stuff for gnome; some even proposed having it default in ubuntu

[21:11:53] <aseigo> hardware items should be replaced by plasmoids

[21:11:55] <aseigo> that's sort of the idea

[21:11:57] <agateau> seele: great

[21:12:19] <Chani> ok, so what was agateau's item?

[21:12:26] <seele> Chani: one moment

[21:12:30] <Nightrose> aseigo: can you give an exapmle for app status indicator?

[21:12:47] <seele> aseigo: so i can write a note that plasma team is working on it, however you decide to implement and set the behavior?

[21:12:50] <agateau> Chani: i would like to propose this guideline "most applications should have only one toolbar"

[21:13:13] <-- yaroslav__ (n=yaroslav@ool-4355d73d.dyn.optonline.net) has quit (Read error: 104 (Connection reset by peer))

[21:13:14] <aseigo> Nightrose: kmail

[21:13:20] <Nightrose> ah ok

[21:13:24] <agateau> i wanted to prepare some shots to show guilty (imho) apps, but I was too busy today

[21:13:27] <agateau> :/

[21:13:34] <Chani> oh

[21:13:41] <Nightrose> agateau: parley iirc

[21:13:51] <eean> agateau: I don't see how that would work with amarok at all

[21:13:53] <Chani> what I like aabout multiple toolbars is that it's easy to turn things on & off

[21:13:56] <aseigo> seele: i think we can come back to this once the new system is in place yes

[21:14:04] <Chani> eg. the bookmarks toolbar in konq

[21:14:08] <seele> agateau: do you want describe what you think is the issue with multiple toolbars and why you think one toolbar is better

[21:14:11] <seele> aseigo: ok

[21:14:14] <aseigo> seele: but we are aware of this "annoyance" and are working on it

[21:14:17] <agateau> seele: yes

[21:14:25] <aseigo> reason being that it's not really 100% fixable with the current system

[21:14:40] <aseigo> we just don't get enough information about applications with the current system to know what to do, and we can't set policy in the tray

[21:14:54] <agateau> first i would like to say it should not be a 100% rule, but I think a lot of apps use multiple toolbars without a good reason

[21:15:00] <agateau> examples : konqueror

[21:15:06] --> juan--d-_-b (n=juan--d-@unaffiliated/juan--d--b/x-561435) has joined #kde-usability

[21:15:07] --> yaroslav_ (n=yaroslav@ool-4355d73d.dyn.optonline.net) has joined #kde-usability

[21:15:11] <agateau> not the bookmark bar,

[21:15:19] <agateau> but the buttons + url

[21:15:26] <agateau> should be only one bar imho

[21:15:43] <agateau> other example : akregator

[21:15:48] <Chani> why?

[21:16:07] <agateau> 1. multiple bars add visual clutter

[21:16:22] -*- eean doesn't see multiple toolbars in akregator

[21:16:38] <agateau> 2. it's easy for a not so tech savvy user to get a weird toolbar layout

[21:16:44] <agateau> eean: let me post a shot

[21:16:59] <aseigo> agateau: agreed ... getting those down in number would be good

[21:18:25] <eean> oh I found them for akregator

[21:18:28] <Chani> hmm. I dunno.

[21:18:39] <leinir> Now, i am not entirely sure that i see the defaults, but does KDE ship with locked toolbars?

[21:18:40] <agateau> eean: just when I press the upload button :)

[21:18:47] <seele> agateau: is this by default or technically limit?

[21:19:11] <Peter007> I think a one toolbar is good, provided it is customisable, the current situation is to use multiple tb to do that

[21:19:16] <agateau> seele: in most case, it's a deliberate choice i think

[21:19:29] <Chani> I have a vague memory of back when the location *was* on hte same toolbar, and sometimes this would force the entire toolbar onto a second line... but maybe that's fixed now?

[21:19:30] <agateau> Peter007: toolbars are customisable

[21:19:32] <aseigo> leinir: no

[21:19:47] <Peter007> cool

[21:20:03] <leinir> In that case, my question would be wether there is any reason for KDE to ship with the toolbars unlocked?

[21:20:28] <agateau> Chani: never happened to me (which does not me it never happened :)

[21:20:38] <agateau> s/not me/not mean/

[21:20:40] <seele> leinir: i think locking them could provide the benefit of preventing users from messing them up by accident :)

[21:20:47] -*- Chani had a lot of trouble with konq's toolbars in kde3

[21:20:58] <seele> agateau: are we waiting for a screenshot?

[21:21:08] <leinir> Since i've been silly enough to have a couple of beers tonight, i am not sure my reasoning is entirely sound, and as such would rather bring it up for discussion in this context than immediately suggest it as a solution ;)

[21:21:23] <agateau> seele: hmm no, I was about to upload one for eean, but he found out what I was talking about

[21:21:35] <leinir> seele: But yes, that was my reasoning (and i do believe that i've reasoned that way without alcoholic assistance before ;) )

[21:21:52] <eean> agateau: well there's the browser toolbar, but it kind of makes sense for that to be seperate

[21:21:55] <Chani> having multiple toolbars does make it a lot easier to do simple customisation. if I want to put a group elsewhere or delete a whole group I don't have to remove or move icons one by one (and moving things is a pita in the toolbar config dialog)

[21:22:22] <Peter007> chani: agree

[21:22:39] <leinir> Chani: An example is my toolbar layout in Konqueror, where i've got a few more icons in the navigation toolbar than there's room for, which then folds out to allow for extra actions...

[21:22:50] <leinir> not too well described, but i hope you get the idea :)

[21:22:59] <Chani> actualy, I think my biggest problem with toolbars is those weird <merge> things. I can't move them to another toolbar, I can't always get rid of them, and if I do get rid of them they're gone forever which might not be what I want :/

[21:23:10] <seele> so maybe the issue is more that many applications just have too many unnecessary toolbars that should be combined, and not that all applications should have one toolbar?

[21:23:18] <agateau> Chani: the toolbar config dialog could be improved, but I would argue this is something you don't do often, this does not sound like a reason to impose multiple toolbars to everyone

[21:23:20] <seele> because koffice is another example where multiple toolbars make sense

[21:23:36] <Chani> which applications have unnecessary toolbars?

[21:23:39] <agateau> seele: yes I believe it makes sense here

[21:23:54] <agateau> Chani: let me gather some

[21:23:56] <Nightrose> Chani: parley should be looked at imho

[21:23:57] <agateau> konqueror (imho)

[21:24:02] <agateau> akregator

[21:24:09] <agateau> kopete

[21:24:18] <Chani> agateau: I guess I don't see it as much of an imposition. like applet handles; if you don't like it, lock them.

[21:24:19] <colomar> So wee need - at least relatively - clear rules for when multiple toolbars make sense and when they don't

[21:24:54] <Peter007> erm... would it be possible for apps to ship with a default tb, and allow users to create their own?

[21:25:05] <seele> colomar: yes, i think that is probably the more practical solution.

[21:25:13] <-- juan--d-_-b (n=juan--d-@unaffiliated/juan--d--b/x-561435) has left #kde-usability

[21:25:17] <agateau> Peter007: I believe it can be done, if you are not afraid of xml editing

[21:25:18] <seele> i'm sure a lot of toolbars could be merged, but there are a lot of cases where separate toolbars make sense

[21:25:38] <agateau> seele: yes, that's how I feel

[21:25:43] <seele> has anyone seen how mac osx does it's toolbar configuration?

[21:25:48] <seele> with the drag n drop?

[21:25:53] <Peter007> agateau: not what I had in mind, more like a tn creator:)

[21:25:54] <agateau> like firefox iirc

[21:25:56] <Chani> agateau: I AM afraid of xml editing.

[21:26:03] <seele> any libs/qt experts know how impossible that is?

[21:26:16] <agateau> Chani: this is where the toolbar config dialog could be improved, maybe :)

[21:26:19] <Peter007> s/tn/tb/g

[21:26:24] <Chani> agateau: true.

[21:26:35] --> michaelrudolph (n=mr@p4FD1E6B4.dip.t-dialin.net) has joined #kde-usability

[21:26:38] <seele> ok, so that begins to lead in to another topic which is sortof related

[21:26:50] <seele> and i have a feeling i'm going to assign agateau and colomar to work together on this if they would like :)

[21:26:56] <Chani> my biggest fear here is of multiple <merge> thingies all in one toolbar, and I don't want them, but don't want to delete them forever either...

[21:27:04] <agateau> :)

[21:27:16] <seele> colomar (Thomas Pfeiffer) was one of our SoU students this past year, and he worked on some ui patterns for things like configuring lists

[21:27:18] <Chani> actually, the one akregator has is outright broken anyways

[21:27:18] <leinir> seele: Yes, the macos x toolbar editing feels extremely powerful and pleasant to use - also with the defailt layout pseudo-token, very nifty :)

[21:27:28] <seele> an application of this could be the toolbar configuration tool

[21:27:35] -*- Chani has no buttons on hte browse toolbar :( and can't do anything because it's a <merge>

[21:27:49] <-- yaroslav (n=yaroslav@ool-4355c41e.dyn.optonline.net) has quit (Read error: 110 (Connection timed out))

[21:28:03] <-- yaroslav_ (n=yaroslav@ool-4355d73d.dyn.optonline.net) has quit ("Konversation terminated!")

[21:28:13] <agateau> colomar: didn't you present your work at akademy?

[21:28:17] <seele> he did

[21:28:26] <agateau> ok, was there :)

[21:28:30] <seele> so. i dont think "one toolbar" is a practical solution, but the problem does exist

[21:28:41] <seele> agateau: you have sortof volunteered yourself for this one because you brought it up

[21:28:47] <Peter007> having suggested creating tb, I am very lazy and leave the tb as is, so I don't like my own idea;)

[21:28:48] <seele> if anyone else is intersted in this, please speak up

[21:28:53] <agateau> i would say, "one toolbar unless you have a good reason"

[21:28:54] <colomar> agateau: Cool, people actually rembered that :)

[21:29:01] <leinir> Well, one toolbar may not be a practical solution, but making it *look* like a single toolbar...

[21:29:05] <seele> but perhaps agateau and anyone else could get together and find toolbars that could be merged

[21:29:07] <leinir> i.e. shipping with toolbars locked

[21:29:14] <seele> leinir: yes

[21:29:23] --> yaroslav_ (n=yaroslav@ool-4355d73d.dyn.optonline.net) has joined #kde-usability

[21:29:24] <agateau> seele: I can do this, yes

[21:29:33] <Chani> leinir: makes sense to me

[21:29:36] <seele> once the toolbars are fixed, we can look at what existed as problems, and write down guidelines on how to create toolbar groupings

[21:29:59] <seele> also, agateau if you want to work with colomar on this (or anyone else), colomar designed some patterns for list administration

[21:30:12] <leinir> That could even be used as a hack to provide those different size buttons...

[21:30:17] <seele> so maybe there is a way to improve the existing toolbar UI so that if people want to configure their now larger toolbars, they can do that easily

[21:30:21] <leinir> But that's for another day :)

[21:30:21] --> heowHoew (n=heow@p5790E374.dip.t-dialin.net) has joined #kde-usability

[21:30:26] <agateau> seele: you are thinking about the toolbar config i guess

[21:30:30] <seele> agateau: yes

[21:30:43] <seele> colomar: are you ok with this, i just volunteered you :)

[21:31:02] <agateau> seele: i would like to give a try to the macosx/firefox config style

[21:31:03] <colomar> Uhm, I

[21:31:11] <agateau> to see if it's technically possible

[21:31:21] <colomar> am not exactly sure what to do yet, but I'm okay with it I guess ;)

[21:31:27] <agateau> it feels the most natural way to configure the bar

[21:31:29] -*- Peter007 wonders about auto adding a toolbutton based on user usage, and removal of unused buttons

[21:31:31] <seele> ok great

[21:31:33] <seele> agateau: sounds good

[21:31:47] <Chani> agateau: what's that?

[21:31:59] <leinir> Peter007: That's the same as personalised menus, the single most hated (mis-)feature in Windows XP ;)

[21:32:00] <seele> so agateau and colomar are going to work on the toolbar issue and i will follow up with them after a bit

[21:32:16] <agateau> seele: fine with me

[21:32:24] <Peter007> leinir: lol, my bad

[21:32:28] --> notmart (n=user@host54-220-dynamic.8-87-r.retail.telecomitalia.it) has joined #kde-usability

[21:32:37] <DreadKnight> perhaps we should have the application send data to a server about the most used/clicked actions and such

[21:32:41] <agateau> Chani: start firefox, then right click a toolbar and select "customize"

[21:32:43] <seele> ok, let's see where we are on the list..

[21:32:56] <Chani> oh right. I have firefox installed now...

[21:33:12] <seele> colomar: did you want to talk anymore about the design patterns? or do you want to focus on working with agateau on the toolbar UI and formalize that pattern first?

[21:33:14] <leinir> Peter007: Hey, someone has to suggest it at least once during every discussion on usability, it's something like a rule ;) Kinda like the whole basic/expert settings thing, someone has to bring it up so someone can hit them over the head with a brick ;)

[21:33:31] <seele> colomar: (maybe you guys can create a standardized class for list editing out of it.. *g*)

[21:33:41] <Peter007> leinir: yea but why me, you the one drinking;)

[21:33:52] <leinir> i've been doing it for a while ;)

[21:34:00] <seele> oh, the next one is colomar's too

[21:34:02] <leinir> (not the drinking, the usability thing ;) )

[21:34:05] <seele> # Get hot new stuff: Should description text be wrapped? (Thomas Pfeiffer)

[21:34:09] <agateau> Peter007: throwing brick is easier when drunk, maybe?

[21:34:10] <leinir> Right, sorry, shutting up now :)

[21:34:16] <seele> colomar: do you want to describe the issue and how you suggest to fix it?

[21:34:22] <colomar> Yes

[21:35:02] <Chani> agateau: ooh, that firefox things deals with the bookmark toolbar items in a way that I can actually use! no horrid <merge> beasts :)

[21:35:14] <agateau> :)

[21:35:27] <colomar> The issue is that in the ghns dialog long descriptions do net get wrapped so one has to make the dialog very wide to be able to read them.

[21:35:39] <agateau> TBH, I guess Firefox does not have to implement <merge> beasts :)

[21:36:28] <Nightrose> colomar: any reason not to do it?

[21:36:32] <Chani> colomar: wordwrap is a pretty obvious feature to me... any reason *not* to have it?

[21:36:41] <colomar> So i'd suggest to apply wrapping there so that long descriptions go over multiple lines instead

[21:36:53] <agateau> colomar: agreed

[21:36:57] <seele> anyone working on ghns?

[21:37:12] <seele> hmm.. i dont see jeremy online

[21:37:32] <seele> is a change like this easy enough to make or is there a technical reason we can't do it?

[21:37:45] <Nightrose> he has a new gf since a few days

[21:37:52] <Nightrose> don't expect him to show up on irc

[21:38:00] <Nightrose> email will do probably

[21:38:02] <seele> also to consider is can we limit the number of lines. so while having 2 or 3 lines of description would be good, having a very long description would be bad

[21:38:25] <Peter007> wrap and scroll?

[21:38:29] <agateau> seele: the tricky thing is rows will have different heights, but this should not be a blocker

[21:38:32] <seele> and so we would need something that can show 1 > n < 4 lines of text

[21:39:10] <seele> ok

[21:39:25] <agateau> anyone now where ghns code is in svn?

[21:39:45] <agateau> s/now/know/

[21:39:55] <seele> not sure. is jeremy whiting still maintaining ghns?

[21:40:12] <Nightrose> yes

[21:40:12] <agateau> nevermind I found it (kdelibs/knewstuff)

[21:40:21] <-- notmart (n=user@host54-220-dynamic.8-87-r.retail.telecomitalia.it) has quit ("Leaving")

[21:40:41] <seele> ok. so no one seems opposed to this design suggestion

[21:40:53] <seele> i will make a note to talk to jeremy about it

[21:41:02] --> notmart (n=diau@host54-220-dynamic.8-87-r.retail.telecomitalia.it) has joined #kde-usability

[21:41:14] <colomar> cool. Finally I can read whole descriptions ;)

[21:41:29] <colomar> or will be, once it gets done

[21:41:39] <seele> ok. so we've gotten through 4 items today, which i think it pretyt productive

[21:41:49] <seele> we havent hit the 2 hour mark, but i think this is a good stopping point for today

[21:42:05] <leinir> *nods* People are slowly drifting, i would agree yes :)

[21:42:06] <seele> i will post the summary of actions on the wiki page and probably to the usability mailing list

[21:42:17] <seele> the next meeting will probably be in the middle of the week for those of you who go out on the weekend

[21:42:20] <DreadKnight> ghns is a bit scary because of the thumbnails.. no actuall quick preview of plasma themes or desktop wallpapers without actually installing /trying them out for yourself, which takes more energy and time

[21:42:27] <Peter007> thanks seele, good job

[21:42:29] <seele> thank you everyone to coming to the meeting and participating, i think we were very productive

[21:42:32] <leinir> Cheers! :)

[21:42:38] <seele> i'm thinking another meeting in one month

[21:42:44] <seele> until then, feel free to add items to the meeting page

[21:42:47] <DreadKnight> linux mint even provides screenies for packages from the package manager (add/remove thingy)

[21:42:47] <seele> cheers everyone!

[21:42:57] <DreadKnight> bye!

[21:42:59] -*- notmart sad having missed it

[21:43:06] <notmart> phew, damn real life :p

[21:43:16] <seele> notmart: someone should be posting logs and i will provide a summary of what happened :)

[21:43:28] <notmart> :)

[21:43:44] <Chani> seele: I was surprised that this meeting was at noon for me. normally I have to put up with awkward meeting times

[21:43:46] <Peter007> notmart: not the same, is it?

[21:44:33] <notmart> Peter007: no, indeed, until one can go back in time to be able to argue :p

[21:44:35] <seele> Chani: better than at 6am :)

[21:45:03] <Peter007> notmart: next month I'll let you make up for it

[21:46:22] <Peter007> so is this summary going to be posted on kde-usability list?

Projects/Usability/Meetings

2009-02-22T23:32:23Z

Seele: added more information about meetings

Projects/Usability/Meetings

2009-02-21T19:57:30Z

Seele: add link to sou hig patterns

This is the planning page for the first KDE Usability IRC Meeting in #kde-usability on irc.freenode.org.

==Next Meeting Feb 21 20UTC==

The following are the planned topics for the next meeting. If we do not get through the list in 2 hours, the topics will be covered in the next meeting. If we get through the list in < 2 hours, we will add an additional topic from the main meeting topics list if the people necessary are in attendance.

# Menubar: Settings vs. More information on [[Projects/Usability/HIG/Menu_Bar/View_Menu|View Menu]] page. (CelesteLynPaul)
# Proposed guideline: "most applications should have only one toolbar" (Agateau)
# default action of service icons
# Get hot new stuff: Should description text be wrapped? (Thomas Pfeiffer)
# KDE design patterns: Are they known/useful/being used? [[Projects/Usability/HIG/SOU_Workspace|See SoU Workspace]] (Thomas Pfeiffer)
# KWin: Placement policy 'Remember' ([http://bugs.kde.org/show_bug.cgi?id=15329 Bug 15329])
# Dolphin/Konqueror: Select/enter newly created folder/file ([http://bugs.kde.org/show_bug.cgi?id=155706 Bug 155706])
# Keyboard's "Super" key doesn't launch Kickoff ([http://bugs.kde.org/show_bug.cgi?id=154564 Bug 154564])
# To which menu entry we should add icons, and to which one we shouldn't add icons. ( Possible UI case could by Qt application Kadu Instant Messenger: 1) http://tinyurl.com/menukadu , 2) http://tinyurl.com/menucontacts , 3) http://tinyurl.com/menuhelp2 , 4) http://tinyurl.com/menucontext2 [Too many icons] )

==Meeting Topics==

Add meeting topics you would like to discuss. Not all of the topics will be able to be covered in a single meeting and so might be deferred until later. Please include your name/irc nick and a link to a project page or bug.

# Desktop Settings Dialog: Review its usability (Anne-Marie Mahfouf)
## Improve Desktop Theme: Customized (works with Desktop Theme Details kcm from System Settings)
## Add SlideShow effects options: where, how
# Amarok 2 general usability <-- Probably have a separate meeting for this

User:Seele

2009-02-21T16:21:53Z

Seele:

* Email: [mailto:celeste(at)kde(dot)org| celeste(at)kde(dot)org]
* IRC: seele@irc.freenode.net
* Blog: [http://weblog.obso1337.org| weblog.obso1337.org]
* Website: [http://www.celestelynpaul.com| celestelynpaul.com]

Projects/Usability/Meetings

2009-02-21T16:15:47Z

Seele: rearranged items

This is the planning page for the first KDE Usability IRC Meeting in #kde-usability on irc.freenode.org.

==Next Meeting Feb 21 20UTC==

The following are the planned topics for the next meeting. If we do not get through the list in 2 hours, the topics will be covered in the next meeting. If we get through the list in < 2 hours, we will add an additional topic from the main meeting topics list if the people necessary are in attendance.

# Menubar: Settings vs. More information on [[Projects/Usability/HIG/Menu_Bar/View_Menu|View Menu]] page. (CelesteLynPaul)
# Proposed guideline: "most applications should have only one toolbar" (Agateau)
# default action of service icons
# KWin: Placement policy 'Remember' ([http://bugs.kde.org/show_bug.cgi?id=15329| Bug 15329])
# Dolphin/Konqueror: Select/enter newly created folder/file ([http://bugs.kde.org/show_bug.cgi?id=155706| Bug 155706])
# Keyboard's "Super" key doesn't launch Kickoff ([http://bugs.kde.org/show_bug.cgi?id=154564| Bug 154564])
# To which menu entry we should add icons, and to which one we shouldn't add icons. ( Possible UI case could by Qt application Kadu Instant Messenger: 1) http://tinyurl.com/menukadu , 2) http://tinyurl.com/menucontacts , 3) http://tinyurl.com/menuhelp2 , 4) http://tinyurl.com/menucontext2 [Too many icons] )

==Meeting Topics==

Add meeting topics you would like to discuss. Not all of the topics will be able to be covered in a single meeting and so might be deferred until later. Please include your name/irc nick and a link to a project page or bug.

# Desktop Settings Dialog: Review its usability (Anne-Marie Mahfouf)
## Improve Desktop Theme: Customized (works with Desktop Theme Details kcm from System Settings)
## Add SlideShow effects options: where, how
# Amarok 2 general usability <-- Probably have a separate meeting for this

Projects/Usability/Meetings

2009-02-21T15:49:12Z

Seele: add links to bugs

This is the planning page for the first KDE Usability IRC Meeting in #kde-usability on irc.freenode.org.

'''Next Meeting'''

Feb 21st 20 UTC

If you have a design, topic, or question you would like to discuss, please include it in the list. We may not be able to get through all the topics in one meeting.

'''Meeting Topics'''

# Menubar: Settings vs. More information on [[Projects/Usability/HIG/Menu_Bar/View_Menu|View Menu]] page. (CelesteLynPaul)
# Proposed guideline: "most applications should have only one toolbar" (Agateau)
# Desktop Settings Dialog: Review its usability (Anne-Marie Mahfouf)
## Improve Desktop Theme: Customized (works with Desktop Theme Details kcm from System Settings)
## Add SlideShow effects options: where, how
# Amarok 2 general usability
# default action of service icons
# KWin: Placement policy 'Remember' ([http://bugs.kde.org/show_bug.cgi?id=15329| Bug 15329])
# Dolphin/Konqueror: Select/enter newly created folder/file ([http://bugs.kde.org/show_bug.cgi?id=155706| Bug 155706])
# Keyboard's "Super" key doesn't launch Kickoff ([http://bugs.kde.org/show_bug.cgi?id=154564| Bug 154564])
# To which menu entry we should add icons, and to which one we shouldn't add icons. ( Possible UI case could by Qt application Kadu Instant Messenger: 1) http://tinyurl.com/menukadu , 2) http://tinyurl.com/menucontacts , 3) http://tinyurl.com/menuhelp2 , 4) http://tinyurl.com/menucontext2 [Too many icons] )

Projects/Usability/Meetings

2009-02-21T15:42:23Z

Seele: add link to view menu page

This is the planning page for the first KDE Usability IRC Meeting in #kde-usability on irc.freenode.org.

'''Next Meeting'''

Feb 21st 20 UTC

If you have a design, topic, or question you would like to discuss, please include it in the list. We may not be able to get through all the topics in one meeting.

'''Meeting Topics'''

# Menubar: Settings vs. More information on [[Projects/Usability/HIG/Menu_Bar/View_Menu|View Menu]] page. (CelesteLynPaul)
# Proposed guideline: "most applications should have only one toolbar" (Agateau)
# Desktop Settings Dialog: Review its usability (Anne-Marie Mahfouf)
## Improve Desktop Theme: Customized (works with Desktop Theme Details kcm from System Settings)
## Add SlideShow effects options: where, how
# Amarok 2 general usability
# default action of service icons
# KWin: Placement policy 'Remember' (Bug 15329)
# Dolphin/Konqueror: Select/enter newly created folder/file (Bug 155706)
# Keyboard's "Super" key doesn't launch Kickoff (Bug 154564)
# To which menu entry we should add icons, and to which one we shouldn't add icons. ( Possible UI case could by Qt application Kadu Instant Messenger: 1) http://tinyurl.com/menukadu , 2) http://tinyurl.com/menucontacts , 3) http://tinyurl.com/menuhelp2 , 4) http://tinyurl.com/menucontext2 [Too many icons] )

Projects/Usability/HIG/Menu Bar/View Menu

2009-02-21T15:38:44Z

Seele: new page on view menu

The View menu is a place for options which configure various content and display settings. Many of these options are toggles, such as turning on and off

Options that should be listed in the View menu:
* Show/hide menubar, statusbar, panels, toolboxes
* Show/hide information elements such as previews
* Alternate window layouts such as splitting
* List sorting options
* Full screen mode
* Zooming controls

==Toolbars in Settings or View?==
The option to toggle the visibility of toolbars is currently in the Settings menu. There have been several discussions over the years about whether toolbar visibility should be in Settings or View. One of the arguments is that the configuration option for configuring toolbars resides in the Settings and so the two related options should be together. However, there are several arguments for why toolbar visibility should be in View.

Conceptually, toolbars are "window elements", the same as menubar, statusbar, and panels in a window. These other window elements currently reside in the View menu. This is important to note for two reasons. One, it establishes that View seems to be a logical place to put this type of configuration options. Two, since toolbars are conceptually similar to the mentioned window elements. Users will think of them as the same and use what they have learned with the other window elements ("I cam configure the menubar visibility here") and apply it to toolbars ("I assume I can also configure the toolbar visibility here since it is similar to the menubar"). There is anecdotal evidence that even users who have used and learned the position of the toolbar visibility option continue to make the mistake of looking in View for the option.

Also, non-KDE applications which are often coinstalled with KDE applications, such as Firefox and OpenOffice, place the toolbar visibility controls in the View menu. The argument is not that Firefox and OpenOffice do it the "right way", simply that an added benefit of changing KDE toolbar visibility to View would increase consistency with non-KDE applications, and improve the overall experience.

==Other View Inconsistencies==
* In most KDE4 applications, toggle menubar is in View, but in Dolphin it is in Settings
* Page navigation controls (back, forward, stop, refresh) live in view, which seems strange because they are not related to the display. What is a alternative for these types of controls?

Projects/Usability

2009-02-09T23:14:44Z

Seele: remove toc

__NOTOC__

The KDE Usability Project aims to improve KDE usability and user experience through:

* Educating developers about usability practices
* Conducting usability activities to help gather feedback from users
* Working with projects and help design usable user interfaces

Learn more at the [http://usability.kde.org KDE Usability Project] website.

[[Projects/Usability/Meetings | KDE Usability Project Meetings]]

= [[Projects/Usability/HIG|KDE4 Human Interface Guidelines]] =

If you have questions about guidelines or want to request a missing guideline or change to a guideline, please put it on the [http://techbase.kde.org/Projects/Usability/HIG_Questions HIG Questions] page. We will refer to this page during the [http://season.openusability.org Season of Usability] KDE4 HIG project.

= User Research Profiles =

The purpose of this template is to provide a place to document an application's user research information for reference during development. Top level items are information everyone in the project should be aware of. Some of the details in the lower sections may take some work and discussion within the project to complete.

[http://techbase.kde.org/index.php?title=Projects/Usability/Project_User_Research_Template Project User Research Template]

== Projects ==

These projects have been called to work on their user research profiles:

* [[Projects/Gwenview/User_Research_Profile|Gwenview]]
* [[Projects/Kopete/User_Research_Profile|Kopete]]
* [[Projects/Okular/User_Research_Profile|Okular]]
* [[Projects/Plasma/PURP|Plasma]]

= Case Studies and Reports =

[[Projects/Usability/Case_Studies | Case Studies]]

[[Projects/Usability/Reports | Reports]]

[[Category:Usability]]

Projects/Usability

2009-02-09T23:13:30Z

Seele: add link to meetings

The KDE Usability Project aims to improve KDE usability and user experience through:

* Educating developers about usability practices
* Conducting usability activities to help gather feedback from users
* Working with projects and help design usable user interfaces

Learn more at the [http://usability.kde.org KDE Usability Project] website.

[[Projects/Usability/Meetings | KDE Usability Project Meetings]]

= [[Projects/Usability/HIG|KDE4 Human Interface Guidelines]] =

If you have questions about guidelines or want to request a missing guideline or change to a guideline, please put it on the [http://techbase.kde.org/Projects/Usability/HIG_Questions HIG Questions] page. We will refer to this page during the [http://season.openusability.org Season of Usability] KDE4 HIG project.

= User Research Profiles =

The purpose of this template is to provide a place to document an application's user research information for reference during development. Top level items are information everyone in the project should be aware of. Some of the details in the lower sections may take some work and discussion within the project to complete.

[http://techbase.kde.org/index.php?title=Projects/Usability/Project_User_Research_Template Project User Research Template]

== Projects ==

These projects have been called to work on their user research profiles:

* [[Projects/Gwenview/User_Research_Profile|Gwenview]]
* [[Projects/Kopete/User_Research_Profile|Kopete]]
* [[Projects/Okular/User_Research_Profile|Okular]]
* [[Projects/Plasma/PURP|Plasma]]

= Case Studies and Reports =

[[Projects/Usability/Case_Studies | Case Studies]]

[[Projects/Usability/Reports | Reports]]

[[Category:Usability]]

Projects/Usability

2009-02-09T23:09:32Z

Seele: add space to link

The KDE Usability Project aims to improve KDE usability and user experience through:

* Educating developers about usability practices
* Conducting usability activities to help gather feedback from users
* Working with projects and help design usable user interfaces

Learn more at the [http://usability.kde.org KDE Usability Project] website.

= [[Projects/Usability/HIG|KDE4 Human Interface Guidelines]] =

If you have questions about guidelines or want to request a missing guideline or change to a guideline, please put it on the [http://techbase.kde.org/Projects/Usability/HIG_Questions HIG Questions] page. We will refer to this page during the [http://season.openusability.org Season of Usability] KDE4 HIG project.

= User Research Profiles =

The purpose of this template is to provide a place to document an application's user research information for reference during development. Top level items are information everyone in the project should be aware of. Some of the details in the lower sections may take some work and discussion within the project to complete.

[http://techbase.kde.org/index.php?title=Projects/Usability/Project_User_Research_Template Project User Research Template]

== Projects ==

These projects have been called to work on their user research profiles:

* [[Projects/Gwenview/User_Research_Profile|Gwenview]]
* [[Projects/Kopete/User_Research_Profile|Kopete]]
* [[Projects/Okular/User_Research_Profile|Okular]]
* [[Projects/Plasma/PURP|Plasma]]

= Case Studies and Reports =

[[Projects/Usability/Case_Studies | Case Studies]]

[[Projects/Usability/Reports | Reports]]

[[Category:Usability]]

Projects/Usability

2009-02-09T23:09:05Z

Seele: add link to reports

The KDE Usability Project aims to improve KDE usability and user experience through:

* Educating developers about usability practices
* Conducting usability activities to help gather feedback from users
* Working with projects and help design usable user interfaces

Learn more at the [http://usability.kde.org KDE Usability Project] website.

= [[Projects/Usability/HIG|KDE4 Human Interface Guidelines]] =

If you have questions about guidelines or want to request a missing guideline or change to a guideline, please put it on the [http://techbase.kde.org/Projects/Usability/HIG_Questions HIG Questions] page. We will refer to this page during the [http://season.openusability.org Season of Usability] KDE4 HIG project.

= User Research Profiles =

The purpose of this template is to provide a place to document an application's user research information for reference during development. Top level items are information everyone in the project should be aware of. Some of the details in the lower sections may take some work and discussion within the project to complete.

[http://techbase.kde.org/index.php?title=Projects/Usability/Project_User_Research_Template Project User Research Template]

== Projects ==

These projects have been called to work on their user research profiles:

* [[Projects/Gwenview/User_Research_Profile|Gwenview]]
* [[Projects/Kopete/User_Research_Profile|Kopete]]
* [[Projects/Okular/User_Research_Profile|Okular]]
* [[Projects/Plasma/PURP|Plasma]]

= Case Studies and Reports =

[[Projects/Usability/Case_Studies | Case Studies]]
[[Projects/Usability/Reports | Reports]]

[[Category:Usability]]

Projects/Usability/Reports

2009-02-09T20:18:19Z

Seele: update page with stats

==Usability Reports==

* [[Projects/Usability/Reports/2008|2008]] (6 Reports)
* [[Projects/Usability/Reports/2007|2007]] (7 Reports)
* [[Projects/Usability/Reports/2006|2006]] (7 Reports)
* [[Projects/Usability/Reports/2005|2005]] (7 Reports)
* [[Projects/Usability/Reports/2004|2004]] (2 Reports)

===Statistics (as of 2008)===
{|
|-
! Total number of reports
| 29 reports
|-
! Average reports a year
| 6.8 reports/year
|-
! Total number of contributors
| 19 contributors
|-
! Most active contributors
| Ellen Reitmayr (11), Celeste Lyn Paul (9), Florian Graessle (4)
|-
! Longest active contributors
| Ellen Reitmayr (2004-2008), Celeste Lyn Paul (2004-2008)
|-
! Newest contributors
| Pallavi Damera (KMyMoney), Becca Scollan (KDE HIG), Thomas Pfeiffer (KDE HIG), Neha Pawa (KOffice)
|-
! Total number of single report contributors
| 14
|-
|}

Projects/Usability/Reports/2007

2009-02-09T20:01:30Z

Seele:

=KPresenter Review and Mockup=
There are many, many bad presentations out there. Really bad presentations. Presentations that bore, presentations that confuse but more importantly, presentations that simply fail to function as a communication medium. But it's not always the presenter's fault, quite often it's just because they've just never learnt how to properly organise a presentation and they aren't able to recognise their mistakes. Other times it's because they've only ever seen other bad examples of presentations. To most people many of these problems are obvious, others are extremely subtle but all of them were of course allowed and often encouraged by mainstream presentation software. I've attempted to prevent or reduce some of these common problems by re-organising several aspects of the typical presentation software interface.

I have nothing to do with the KOffice project (although I would like to in the future), and I don't pretend that herin lies The Answer. I would however like to throw this into the public and see if it can be improved on and eventually implemented in an extremely usable presentation software package. I have far more confidence in the combined skills of the KDE community and the rest of the world, than I do of my own creativity and problem solving.

{|
|-
! Report Date
| February 2007
|-
! Usability Engineer
| Will Hardy
|-
! Software Version
| KPresenter from SVN February 2007
|-
! Download Document
| Link to file...
|}

=Usability Testing of Kubuntu Installation Process=
We conducted task-based usability testing on the Kubuntu installation processes using 9 participants of various computer skill. We found major issues in the partitioning process and interface which prevented all of the participants from successfully installing Kubuntu without help. Also included are suggestions on how to improve the various usability issues we observed.

{|
|-
! Report Date
| June 2007
|-
! Usability Engineer
| Celeste Lyn Paul and graduate students from the University of Baltimore
|-
! Software Version
| Kubuntu Gutsy
|-
! Download Document
| Link to file...
|}

=Report on Printer Dialogs=
This report was done as part of a Google Summer of Code project with the KDE print dialog. This report examines and discusses printing dialogs used by other major desktop environments, operating systems, and applications. The result are mockup suggestions for a new KDE print dialog.

{|
|-
! Report Date
| July 2007
|-
! Usability Engineer
| Rutger Claes
|-
! Software Version
| KPrint from SVN July 2007
|-
! Download Document
| Link to file...
|}

=KGet Usability Review=
The KGet download manager for KDE is being rewritten for the upcoming KDE 4.0 and its developers Urs Wolfer and Manolo Valdes were looking for someone to do a usability review of their work so far. Two KDE usability evaluators, Florian Graessle and Tina Trillitzsch, agreed to do a Heuristic Evaluation of KGet. Before the review, the reviewers researched the current user base of KGet and that of competing download managers and determined their goals and needs. Together with KGet’s developers, a target user base was defined and the reviewers created a number of frequent tasks to guide their evaluation. During the evaluation the reviewers went through the interface separately, with the help of a few common usability principles (“heuristics”), noting down any problems they perceived for potential users. Later they agreed on a severity rating for each issue and devised a suggestion to solve it. The results were put into a wiki and presented to the developers in KGet’s irc channel. The reviewers discussed the issues and suggestions with the developers, who then almost immediately began solving some issues, so that these could quickly be marked as solved in the wiki. Overall 37 usability issues were found, most of which have already been fixed.

The findings showed a lot of promise: the browser integration is very well executed and KGet often offers very good feedback when adding downloads. There are some very innovative ideas for finding files to download on a web page. Most negative issues were minor, and only really significant in the main window, especially concerning the presentation and management of download groups and download details.

{|
|-
! Report Date
| August 2007
|-
! Usability Engineers
| Florian Graessle and Tina Trilliztsch
|-
! Software Version
| KGet from SVN July 2007
|-
! Download Document
| Link to file...
|}

=KDE Toolbars=
This report describes some thoughts and suggestions regarding the toolbars in KDE.

{|
|-
! Report Date
| August 2007
|-
! Usability Engineer
| Hans Chen
|-
! Software Version
| KDE 3.5.8
|-
! Download Document
| Link to file...
|}

=Basket Season of Usability Project=
BasKet Note Pads is a multi-purpose note-taking application for the K Desktop Environment (KDE). The goal of the student project was to do a complete usability-development cycle with direct impact on the further development of BasKet Note Pads.

{|
|-
! Report Date
| September 2007
|-
! Usability Engineers
| Frank Ploss and Björn Balazs
|-
! Software Version
| Unknown
|-
! Download Document
| [[http://season.openusability.org/index.php/2007/09/30/success-stories-07-basket/ | Season of Usability Report ]]
|}

=Okular Season of Usability Project=
Okular is the default document viewer for the next major version of the K Desktop Environment. As it is capable of displaying various document and image formats, a major challenge is the design of the toolbar to facilitate browsing, zooming and selecting text passages of the displayed document.

Consequently the objective of the Okular student, Sharad Baliyan, was to develop an alternative toolbar layout. This was to be accomplished by applying parts of the interaction design life cycle. The planned milestones for the student included user and task research, a best-practice and comparative analysis, prototype development and lastly designing the actual alternative toolbar.

{|
|-
! Report Date
| September 2007
|-
! Usability Engineers
| Sharad Baliyan and Florian Grässle
|-
! Software Version
| Unknown
|-
! Download Document
| [[http://season.openusability.org/index.php/2007/09/30/success-stories-07-okular/ | Season of Usability Report ]]
|}

Projects/Usability/Reports

2009-02-09T19:50:58Z

Seele:

Projects/Usability/Reports/2008

2009-02-09T19:50:41Z

Seele:

=KDE for Windows Installer Expert Review=
Expert review of the KDE for Windows installation process.

{|
|-
! Report Date
| January 2008
|-
! Usability Engineer
| Celeste Lyn Paul
|-
! Software Version
| KDE for Windows Installer0.8.5
|-
! Download Document
| Link...
|}

=Usability Reviews for KMyMoney=
Multiple usability reviews and design recommendations for KMyMoney

{|
|-
! Report Date
| March to August 2008
|-
! Usability Engineer
| Pallavi Damera
|-
! Software Version
| Unknown
|-
! Download Document
| [[http://usabilitykmymoney.blogspot.com/ KMyMoney Usability Website]]
|}

=Modified-Delphi Interviews to Discover Plasma User Types=
A set of modified-delphi interviews were conducted on key Plasma developers to discover and document primary user groups of the KDE Desktop and Plasma Widgets.

{|
|-
! Report Date
| April 2008
|-
! Usability Engineer
| Celeste Lyn Paul
|-
! Software Version
| KDE 4.0
|-
! Download Document
| Link...
|}

=Guidelines and Design Patterns for KDE4=
Human Interface Guidelines (later referred to as Guidelines) are documented guidelines based on usability standards for people developing or designing user interfaces for applications within a certain environment. The guideline goals are to enhance consistency among applications and to make knowledge from the user experience field easily accessible to developers. Half of our project involved picking up from where the KDE4 community left off on a collection of Human Interface Guidelines by adding to them and revising what existed.
For the other half of the project, we collaborated on several Interaction Design Patterns (later referred to as Patterns) for KDE4. Patterns offer solutions to recurring design problems by examining both successful and problematic examples in various applications.

{|
|-
! Report Date
| October 2008
|-
! Usability Engineers
| Becca Scollan, Thomas Pfeiffer, Celeste Lyn Paul, and Ellen Reitmayr
|-
! Software Version
| KDE 4.1
|-
! Download Document
| [[http://season.openusability.org/index.php/2008/10/04/success-stories-08-guidelines-and-design-patterns-for-kde4/ | Season of Usability Report ]]
|}

=Toolbox and Palette Interaction for KOffice=
The goal of this project was to improve the toolbox and palette interaction for KOffice, the office suite of the K Desktop Environment. We identified the major interaction problems and created first paper mockups for an improved tool interaction in KOffice.

{|
|-
! Report Date
| October 2008
|-
! Usability Engineers
| Neha Pawa, Celeste Lyn Paul, Ellen Reitmayr
|-
! Software Version
| KOffice 2
|-
! Download Document
| [[http://season.openusability.org/index.php/2008/10/04/success-stories-08-toolbox-and-palette-interaction-for-koffice/ | Season of Usability Report ]]
|}

=Quassel Usability Review=
A usability review was conducted on Quassel, a Qt-based IRC client for multiple platforms. Recommendations were made for how Quassel can improve it's usability for a larger audience and integrate better in to the KDE environment.

{|
|-
! Report Date
| December 2008
|-
! Usability Engineers
| Celeste Lyn Paul
|-
! Software Version
| Quassel 0.3.1
|-
! Download Document
| Link...
|}

Projects/Usability/Reports/2008

2009-02-09T19:50:10Z

Seele: 2008 reports

=KDE for Windows Installer Expert Review=
Expert review of the KDE for Windows installation process.

{|
|-
! Report Date
| January 2008
|-
! Usability Engineer
| Celeste Lyn Paul
|-
! Software Version
| KDE for Windows Installer0.8.5
|-
! Download Document
| Link...
|}

=Usability Reviews for KMyMoney=
Multiple usability reviews and design recommendations for KMyMoney

{|
|-
! Report Date
| March to August 2008
|-
! Usability Engineer
| Pallavi Damera
|-
! Software Version
| Unknown
|-
! Download Document
| [[http://usabilitykmymoney.blogspot.com/ KMyMoney Usability Website]]
|}

=Modified-Delphi Interviews to Discover Plasma User Types=
A set of modified-delphi interviews were conducted on key Plasma developers to discover and document primary user groups of the KDE Desktop and Plasma Widgets.

{|
|-
! Report Date
| April 2008
|-
! Usability Engineer
| Celeste Lyn Paul
|-
! Software Version
| KDE 4.0
|-
! Download Document
| Link...
|}

=Guidelines and Design Patterns for KDE4=
Human Interface Guidelines (later referred to as Guidelines) are documented guidelines based on usability standards for people developing or designing user interfaces for applications within a certain environment. The guideline goals are to enhance consistency among applications and to make knowledge from the user experience field easily accessible to developers. Half of our project involved picking up from where the KDE4 community left off on a collection of Human Interface Guidelines by adding to them and revising what existed.
For the other half of the project, we collaborated on several Interaction Design Patterns (later referred to as Patterns) for KDE4. Patterns offer solutions to recurring design problems by examining both successful and problematic examples in various applications.

{|
|-
! Report Date
| October 2008
|-
! Usability Engineers
| Becca Scollan, Thomas Pfeiffer, Celeste Lyn Paul, and Ellen Reitmayr
|-
! Software Version
| KDE 4.1
|-
! Download Document
| [[http://season.openusability.org/index.php/2008/10/04/success-stories-08-guidelines-and-design-patterns-for-kde4/ | Season of Usability Report ]]
|}

=Toolbox and Palette Interaction for KOffice=
The goal of this project was to improve the toolbox and palette interaction for KOffice, the office suite of the K Desktop Environment. We identified the major interaction problems and created first paper mockups for an improved tool interaction in KOffice.

{|
|-
! Report Date
| October 2008
|-
! Usability Engineers
| Neha Pawa, Celeste Lyn Paul, Ellen Reitmayr
|-
! Software Version
| KOffice 2
|-
! Download Document
| [[http://season.openusability.org/index.php/2008/10/04/success-stories-08-toolbox-and-palette-interaction-for-koffice/ | Season of Usability Report ]]
|}

=Quassel=
A usability review was conducted on Quassel, a Qt-based IRC client for multiple platforms. Recommendations were made for how Quassel can improve it's usability for a larger audience and integrate better in to the KDE environment.

{|
|-
! Report Date
| December 2008
|-
! Usability Engineers
| Celeste Lyn Paul
|-
! Software Version
| Quassel 0.3.1
|-
! Download Document
| Link...
|}

Projects/Usability/Reports/2004

2009-02-09T19:33:12Z

Seele: fix link

=KDE 3.2.0 Expert Inspection=
The major concern of this inspection was to evaluate if the problems that were identified in the usability study were improved in the KDE 3.2.0 release.

The evaluation was conducted on the basis of the use cases that were utilised in the linux usability study.

{|
|-
! Report Date
| March 2004
|-
! Usability Engineers
| Ellen Reitmayr and Jutta Horstmann
|-
! Software Version
| KDE 3.2.0
|-
! Download Document
| [[http://www.linux-usability.de/download/usabilityreport_kde3.2.0.pdf| PDF (German) via relevantive.de]]
|}

=Usability Review of KHangMan=
This usability review of KHangMan identifies usability issues in the game and suggestions on how to fix them.

{|
|-
! Report Date
| March 2004
|-
! Usability Engineer
| Celeste Lyn Paul
|-
! Software Version
| KDE 3.2.0
|-
! Download Document
| Link...
|}

Projects/Usability/Reports/2004

2009-02-09T19:32:39Z

Seele:

=KDE 3.2.0 Expert Inspection=
The major concern of this inspection was to evaluate if the problems that were identified in the usability study were improved in the KDE 3.2.0 release.

The evaluation was conducted on the basis of the use cases that were utilised in the linux usability study.

{|
|-
! Report Date
| March 2004
|-
! Usability Engineers
| Ellen Reitmayr and Jutta Horstmann
|-
! Software Version
| KDE 3.2.0
|-
! Download Document
| [http://www.linux-usability.de/download/usabilityreport_kde3.2.0.pdf| PDF (German) via relevantive.de]
|}

=Usability Review of KHangMan=
This usability review of KHangMan identifies usability issues in the game and suggestions on how to fix them.

{|
|-
! Report Date
| March 2004
|-
! Usability Engineer
| Celeste Lyn Paul
|-
! Software Version
| KDE 3.2.0
|-
! Download Document
| Link...
|}

Projects/Usability/Reports/2004

2009-02-09T19:32:17Z

Seele: new page

=KDE 3.2.0 Expert Inspection=
The major concern of this inspection was to evaluate if the problems that were identified in the usability study were improved in the KDE 3.2.0 release.

The evaluation was conducted on the basis of the use cases that were utilised in the linux usability study.

{|
|-
! Report Date
| March 2004
|-
! Usability Engineers
| Ellen Reitmayr and Jutta Horstmann
|-
! Software Version
| KDE 3.2.0
|-
! Download Document
| [[http://www.linux-usability.de/download/usabilityreport_kde3.2.0.pdf|PDF (German) via relevantive.de]]
|}

=Usability Review of KHangMan=
This usability review of KHangMan identifies usability issues in the game and suggestions on how to fix them.

{|
|-
! Report Date
| March 2004
|-
! Usability Engineer
| Celeste Lyn Paul
|-
! Software Version
| KDE 3.2.0
|-
! Download Document
| Link...
|}

Projects/Usability/Reports/2005

2009-02-09T19:25:05Z

Seele: 2005 reports

=KMail Recipients=
In a short usability test, three users executed typical tasks concerning the composer's recipient fields. Two versions of the recipients area and the Select Recipients dialog were compared. Even if the number of users is not representative, a number of bugs and potential usage problems within both versions were discovered.

With respect to the composer's recipient area, users tended to prefer the new interface. Even if they were faced several problems (merely caused by the prototypical state of the interface) and they were not used to the new behaviour, they stated that they could imagine to become faster and more effective by using it.

With respect to the Select Recipients dialog, users tended to prefer the former dialog as it provided a better management and a better overview over selected contacts. They stated that both dialogs showed several usage problems, but the former one clearly provided a better and more reliable overview. This impression may be reduced by implementing the suggestions given in the following. However, at its current state, it is not advisable to release the new Select Recipients dialog as users were faced severe problems while using it.

{|
|-
! Report Date
| January 2005
|-
! Usability Engineers
| Ellen Reitmayr and Florian Graessle
|-
! Software Version
| KMail 1.7.91 versus CVS HEAD from January 2005
|-
! Download Document
| Link to file...
|}

=KPrinter=
The print dialog in KDE 3.4 has several usability problems which potentially make it hard to be used efficiently by average users. In this document, the major problems are described, and possible ways to solve them are sketched up.

{|
|-
! Report Date
| April 2005
|-
! Usability Engineer
| Ellen Reitmayr
|-
! Software Version
| KPrinter KDE 3.4.0
|-
! Download Document
| Link to file...
|}

=KPDF=
Usability review of KPDF.

{|
|-
! Report Date
| April 2005
|-
! Usability Engineer
| Florian Graessle
|-
! Software Version
| KPDF 0.5 CVS
|-
! Download Document
| Link to file...
|}

=KOrganizer=
In this document, a proposal for KOrganizer's menu structure is illustrated. On the left, the Kontact 1.1 using KDE 3.4 menus are displayed, on the right, mockups of the possible future menus are shown.

{|
|-
! Report Date
| May 2005
|-
! Usability Engineer
| Ellen Reitmayr
|-
! Software Version
| Kontact 1.1 using KDE 3.4.0
|-
! Download Document
| Link to file...
|}

=Kopete=
In this short usability test of the Kopete setup and first steps, potential users had to set up and configure either an ICQ or a Jabber account.
We tested three users, one adrium (MacOSX) user, and two gaim (gnome) users. All of them were very experienced, both regarding IM and general computer experience (two developers, one designer).

{|
|-
! Report Date
| July 2005
|-
! Usability Engineer
| Ellen Reitmayr
|-
! Software Version
| Kopete 0.10.90
|-
! Download Document
| Link to file...
|}

=KBruch=
There are a wide range of minor to major issues with KBruch, most of which have to do with the interaction and usability of the application. There are also a number of suggestions in game play and interface to help improve the application.

Most of the interface rework is for the general interface. Some of it is suggestion, in particular moving the mode buttons to the toolbar. It may end up the most effective way to present the user navigation of the different application modes is with the left document menu as previously designed. This type of navigation is commonly used throughout KDE. The major concern was the three-column layout of the document space, however there may be other ways of redesigning the mode options and displaying the user score.

It is, however strongly recommended to consider the individual task mode changes. These screenshots are implementations of possible fixes for the usability issues found in the interface.

There are no suggestions for the Factorization Task mode at this time. The general interface suggestions would apply to this mode.

{|
|-
! Report Date
| October 2005
|-
! Usability Engineer
| Celeste Lyn Paul
|-
! Software Version
| KBruch from KDE 3.4
|-
! Download Document
| Link to file...
|}

=KOffice Startup=
Although the test of KOffice Starter had been made on a very early version, the results detect problematic elements. The findings reveal problems like template description and the preview area in the starter as well as incomprehensible icons in a crowded icon bar.

{|
|-
! Report Date
| December 2005
|-
! Usability Engineer
| Katrin Gotzer
|-
! Software Version
| Kword 1.4 and KPresenter 1.4
|-
! Download Document
| Link to file...
|}

Projects/Usability/Reports

2009-02-09T19:16:34Z

Seele: broken link

==Usability Reports==

* 2008
* [[Projects/Usability/Reports/2007|2007]]
* [[Projects/Usability/Reports/2006|2006]]
* 2005
* 2004

Projects/Usability/Reports

2009-02-09T19:11:52Z

Seele: add 2006 reports

==Usability Reports==

* 2008
* [[Projects/Usability/Reports/2007|2007]]
* [[Projects/Usability/Reports/20086|2006]]
* 2005
* 2004

Projects/Usability/Reports/2006

2009-02-09T19:11:12Z

Seele: new page

=Filebrowser Screening Test=
In a screening test on file browsing behaviour, 21 participants were interviewed on their habits and preferences regarding file management. Six out of the 21 participants then conducted a usability test with Konqueror, the KDE file manager.

{|
|-
! Report Date
| January 2006
|-
! Usability Engineer
| Ellen Reitmayr
|-
! Software Version
| Konqueror from KDE 3.4
|-
! Download Document
| Link to file...
|}

=Accessibility Meets Usability Weekend=
In user tests with three partially sighted and two blind users, the accessibility features of KDE and Gnome were tested. As a general conclusion we found that while both KDE and Gnome provide very good tools to make the Linux desktop usable for partially sighted and blind users, they are lacking consistent support among the major desktop applications. In KDE, key applications like the text editor Kate or the shell Konsole did not apply high contrast colour schemes; in Gnome, the contents of crucial tools like the software installation (Ubuntu) could not be read by Gnopernicus and were therefore "invisible" for the blind users.

The Accessibility meets Usability Weekend strengthened the collaboration between accessibility and usability in KDE and resulted in a number of guidelines and concepts.

{|
|-
! Report Date
| May 2006
|-
! Usability Engineers
| Ellen Reitmayr and Tina Trillitzsch
|-
! Software Version
| KDE 3.5 in Ubuntu 5.10
|-
! Download Document
| Link to file...
|}

=Amarok Usability Report=
After a short heuristic evaluation of Amarok, a total of 41 usability issues were found. Only 8 issues of low severity were found, 11 were marked medium, and the remaining 22 issues considered highly severe.

Most of the issues were related to design flaws. The application was not tested for task-oriented usability. Even though the application functioned properly from a technical perspective, attention should be given to a more aesthetic user interface design in the future.

{|
|-
! Report Date
| May 2006
|-
! Usability Engineer
| Chi Shang Cheng
|-
! Software Version
| Amarok in SVN May 2006
|-
! Download Document
| Link to file...
|}

=Kivio User Research=
The purpose of this user survey was to get insights into Kivio's major user base, their tasks and needs. Learning more about the usage of diagramming tools, the context of diagram creation and application, as well as the required preciseness were important questions in this scope.
Based on this information, the survey should allow us to illustrate typical usage patterns, and to learn about feature relevance and priorities. It should help us to determine if the features planned in the scope of Kivio's redesign are important to users.

Also, the survey aimed at determining the users' opinions about Kivio and evaluate the differences to other diagramming applications. Reasons for prominence and gaps should be identified and considered in the future work on Kivio. Finally, the survey should give us widespread information about users of diagramming applications which may be used for persona creation. This includes where they live, their age and gender, education and how experienced they are with computers and with creating diagrams.

Based on the survey, the major use cases for Kivio were validated, and Personas for the four major user groups were created by means of a cluster analysis.

{|
|-
! Report Date
| May 2006
|-
! Usability Engineers
| Ellen Reitmayr and Tina Trillitzsch
|-
! Software Version
| Not Applicable
|-
! Download Document
| Link to file...
|}

=KDE4 Human Interface Guidelines Document Research=
The KDE4 Human Interface Guidelines (HIG) is a document which is meant to be a reference guide to developers and usability specialists. It has a unique audience: developers who are very analytical, adept with technology, and sometimes skeptical about ideas opposite of their own; and usability specialists and designers who know a lot of about users but not so much about code.

A survey and card sorting activity were conducted to gather information about the target users of the document, and their mental model for organizing guidelines-related content.

{|
|-
! Report Date
| June and July 2006
|-
! Usability Engineer
| Celeste Lyn Paul
|-
! Software Version
| Not Applicable
|-
! Download Document
| Link to file...
|}

=Kaffeine Usability Report=
After a short heuristic evaluation of Kaffeine, a total of 40 usability issues were found. Only 5 issues of high severity were found, 20 were marked medium, and the remaining 15 issues considered lowly severe.
Most of the issues were related to unnecessary complexity of the user interface. The application was not tested for task-oriented usability. Even though the application functioned properly from a technical perspective, attention should be given to a more aesthetic user interface design in the future.

{|
|-
! Report Date
| July 2006
|-
! Usability Engineer
| Chi Shang Cheng
|-
! Software Version
| Kaffeine 0.8.1 with the Polyester theme7 and the nuoveXT icon set
|-
! Download Document
| Link to file...
|}

=Ideas for a Redesign of What's This Help=
The What's This Help is planned to be redesigned for KDE 4. The concept described in this document summarises the considerations of accessibility, documentation and usability people regarding the requirements of a What's This help which is both accessible, discoverable and usable for future users.

{|
|-
! Report Date
| July 2006
|-
! Usability Engineers
| Ellen Reitmayr, Olaf Schmidt and Philip Rodrigues
|-
! Software Version
| Not Applicable
|-
! Download Document
| Link to file...
|}

Projects/Usability/Reports

2009-02-09T18:32:03Z

Seele: add 2007

==Usability Reports==

* 2008
* [[Projects/Usability/Reports/2007|2007]]
* 2006
* 2005
* 2004

Projects/Usability/Reports/2007

2009-02-09T18:30:52Z

Seele: 2007 report page

=KPresenter Review and Mockup=
There are many, many bad presentations out there. Really bad presentations. Presentations that bore, presentations that confuse but more importantly, presentations that simply fail to function as a communication medium. But it's not always the presenter's fault, quite often it's just because they've just never learnt how to properly organise a presentation and they aren't able to recognise their mistakes. Other times it's because they've only ever seen other bad examples of presentations. To most people many of theseproblems are obvious, others are extremely subtle but all of them were of course allowed and often encouraged by mainstream presentation software. I've attempted to prevent or reduce some of these common problems by re-organising several aspects of the typical presentation software interface.

I have nothing to do with the KOffice project (although I would like to in the future), and I don't pretend that herin lies The Answer. I would however like to throw this into the public and see if it can be improved on and eventually implemented in an extremely usable presentation software package. I have far more confidence in the combined skills of the KDE community and the rest of the world, than I do of my own creativity and problem solving.

{|
|-
! Report Date
| February 2007
|-
! Usability Engineer
| Will Hardy
|-
! Software Version
| KPresenter from SVN February 2007
|-
! Download Document
| Link to file...
|}

=Usability Testing of Kubuntu Installation Process=
We conducted task-based usability testing on the Kubuntu installation processes using 9 participants of various computer skill. We found major issues in the partitioning process and interface which prevented all of the participants from successfully installing Kubuntu without help. Also included are suggestions on how to improve the various usability issues we observed.

{|
|-
! Report Date
| June 2007
|-
! Usability Engineer
| Celeste Lyn Paul and graduate students from the University of Baltimore
|-
! Software Version
| Kubuntu Gutsy
|-
! Download Document
| Link to file...
|}

=Report on Printer Dialogs=
This report was done as part of a Google Summer of Code project with the KDE print dialog. This report examines and discusses printing dialogs used by other major desktop environments, operating systems, and applications. The result are mockup suggestions for a new KDE print dialog.

{|
|-
! Report Date
| July 2007
|-
! Usability Engineer
| Rutger Claes
|-
! Software Version
| KPrint from SVN July 2007
|-
! Download Document
| Link to file...
|}

=KGet Usability Review=
The KGet download manager for KDE is being rewritten for the upcoming KDE 4.0 and its developers Urs Wolfer and Manolo Valdes were looking for someone to do a usability review of their work so far. Two KDE usability evaluators, Florian Graessle and Tina Trillitzsch, agreed to do a Heuristic Evaluation of KGet. Before the review, the reviewers researched the current user base of KGet and that of competing download managers and determined their goals and needs. Together with KGet’s developers, a target user base was defined and the reviewers created a number of frequent tasks to guide their evaluation. During the evaluation the reviewers went through the interface separately, with the help of a few common usability principles (“heuristics”), noting down any problems they perceived for potential users. Later they agreed on a severity rating for each issue and devised a suggestion to solve it. The results were put into a wiki and presented to the developers in KGet’s irc channel. The reviewers discussed the issues and suggestions with the developers, who then almost immediately began solving some issues, so that these could quickly be marked as solved in the wiki. Overall 37 usability issues were found, most of which have already been fixed.

The findings showed a lot of promise: the browser integration is very well executed and KGet often offers very good feedback when adding downloads. There are some very innovative ideas for finding files to download on a web page. Most negative issues were minor, and only really significant in the main window, especially concerning the presentation and management of download groups and download details.

{|
|-
! Report Date
| August 2007
|-
! Usability Engineers
| Florian Graessle and Tina Trilliztsch
|-
! Software Version
| KGet from SVN July 2007
|-
! Download Document
| Link to file...
|}

=KDE Toolbars=
This report describes some thoughts and suggestions regarding the toolbars in KDE.

{|
|-
! Report Date
| August 2007
|-
! Usability Engineer
| Hans Chen
|-
! Software Version
| KDE 3.5.8
|-
! Download Document
| Link to file...
|}

Projects/Usability/Reports/2007

2009-02-09T18:19:38Z

Seele: 2007 report page

=KPresenter Review and Mockup=

=Usability Testing of Kubuntu Installation Process=

=KGet Usability Review=

=Report on Printer Dialogs=

=KDE Toolbars=
This report describes some thoughts and suggestions regarding the toolbars in KDE.

{|
|-
| Report Date | August 2007
|-
| Usability Engineer | Hans Chen
|-
| Software Version | KDE 3.5.8
|-
| Document | FILE
|}

Projects/Usability/Reports

2009-02-09T18:12:05Z

Seele: new reports page

==Usability Reports==

* 2008
* 2007
* 2006
* 2005
* 2004

Projects/Usability/Meetings

2009-02-09T15:45:04Z

Seele: new meetings page

This is the planning page for the first KDE Usability IRC Meeting in #kde-usability on irc.freenode.org (time and date to be determined).

If you have a design, topic, or question you would like to discuss, please include it in the list. We may not be able to get through all the topics in one meeting.

'''Meeting Topics'''

* Menubar: Settings vs. View (CelesteLynPaul)
* Topic...

Projects/Usability

2009-01-25T16:23:13Z

Seele: Protected "Projects/Usability": only registered users may edit kde usability project content [edit=autoconfirmed:move=autoconfirmed]

The KDE Usability Project aims to improve KDE usability and user experience through:

* Educating developers about usability practices
* Conducting usability activities to help gather feedback from users
* Working with projects and help design usable user interfaces

Learn more at the [http://usability.kde.org KDE Usability Project] website.

= [[Projects/Usability/HIG|KDE4 Human Interface Guidelines]] =

If you have questions about guidelines or want to request a missing guideline or change to a guideline, please put it on the [http://techbase.kde.org/Projects/Usability/HIG_Questions HIG Questions] page. We will refer to this page during the [http://season.openusability.org Season of Usability] KDE4 HIG project.

= User Research Profiles =

The purpose of this template is to provide a place to document an application's user research information for reference during development. Top level items are information everyone in the project should be aware of. Some of the details in the lower sections may take some work and discussion within the project to complete.

[http://techbase.kde.org/index.php?title=Projects/Usability/Project_User_Research_Template Project User Research Template]

== Projects ==

These projects have been called to work on their user research profiles:

* [[Projects/Gwenview/User_Research_Profile|Gwenview]]
* [[Projects/Kopete/User_Research_Profile|Kopete]]
* [[Projects/Okular/User_Research_Profile|Okular]]
* [[Projects/Plasma/PURP|Plasma]]

= Case Studies and Reports =

[[Projects/Usability/Case_Studies | Case Studies]]

[[Category:Usability]]

Projects/Usability/HIG/Keyboard Shortcuts

2009-01-13T17:27:31Z

Seele: change "may not" to "will not" for Ctrl W

Keyboard shortcuts help users perform common actions quickly through the keyboard instead of accessing the functionality in the UI with a mouse.

=== Global Keyboard Shortcuts ===

{| border="1" cellpadding="5"
|- style="height:40px"
! width="200" | Action !! width="50" | Key !! width="50" | Altern. !! width="250" | Comment
|- style="height:40px"
| colspan="4" | File Menu
|- style="height:40px"
| New || Ctrl+N || || Create a new document
|- style="height:40px"
| Open || Ctrl+O || || Open a document
|- style="height:40px"
| Save || Ctrl+S || || Save the current document
|- style="height:40px"
| Save As || Ctrl+Shift+S || ||Save the current document
|- style="height:40px"
| Reload || F5 || || Reload the current document/view
|- style="height:40px"
| Print || Ctrl+P || || Print the current document
|- style="height:40px"
| Close || Ctrl+W || || Close the current document. If there is only one document open, this shortcut '''will not''' Close the window or Quit the application.
|- style="height:40px"
| Quit || Ctrl+Q || || Quit the application
|- style="height:40px"
| colspan="4" | Edit menu
|- style="height:40px"
| Undo || Ctrl+Z || || Undo the last operation
|- style="height:40px"
| Redo || Ctrl+Y || Shift+Ctrl+Z || Redo the last undone operation
|- style="height:40px"
| Cut || Ctrl+X || Shift+Delete || Cut the selected area and store it in the clipboard
|- style="height:40px"
| Copy || Ctrl+C || Ctrl+Insert || Copy the selected area into the clipboard
|- style="height:40px"
| Paste || Ctrl+V || Shift+Insert || Paste contents of clipboard at mouse/cursor position
|- style="height:40px"
| Select All || Ctrl+A || || Select everything in the contents area
|- style="height:40px"
| Deselect || Ctrl+Shift+A || || Deselect everything in the contents area
|- style="height:40px"
| Find || Ctrl+F || || Find
|- style="height:40px"
| Find Next || F3 || || Find the next match
|- style="height:40px"
| Find Previous || Shift+F3 || || Find previous match
|- style="height:40px"
| Replace || Ctrl+R || || Find and replace matches
|- style="height:40px"
| Delete word forward || Ctrl+Delete || || Delete word from current cursor location to the end.
|- style="height:40px"
| Delete word backward || Ctrl+Backspace || || Delete word from beginning to current cursor location.
|- style="height:40px"
| Go to line... || Ctrl+G || || Move cursor to the corresponding line.
|- style="height:40px"
| colspan="4" | View Menu
|- style="height:40px"
| Full Screen Mode || Ctrl+Shift+F || || Toggle full screen mode
|- style="height:40px"
| colspan="4" | Zoom menu
|- style="height:40px"
| Zoom In || Ctrl++ || Ctrl+= || Zoom in to the document (magnify)
|- style="height:40px"
| Zoom Out || Ctrl+- || || Zoom out of the document
|- style="height:40px"
| Zoom to 100% || Ctrl+0 ||
|- style="height:40px"
| colspan="4" | Bookmarks menu
|- style="height:40px"
| Add Bookmark || Ctrl+B || || Add a bookmark for the current location
|- style="height:40px"
| colspan="4" | Help menu
|- style="height:40px"
| Help || F1 || || Obtain help and documentation for the application
|- style="height:40px"
| What's This || Shift+F1 || || Obtain a short help for the currently visible interface elements.
|- style="height:40px"
| colspan="4" | Navigation
|- style="height:40px"
| Focus to Menu || F10 || || Focus the menu bar.
|- style="height:40px"
| Show Context Menu || Ctrl+F10 || Menu || Show the context menu.
|- style="height:40px"
| Toggle Menu bar || Ctrl+M || || Toggle the appearance of the menu bar.
|- style="height:40px"
| Page Down || Space || PageDown || Scroll down one Screen, displaying the next page if the application normally displays a page at a time.
|- style="height:40px"
| Page Up || Shift+space || PageUp || Scroll up one Screen, displaying the previous page if the application normally displays a page at a time.
|- style="height:40px"
| Forward || Alt+Right || || Go to next page.
|- style="height:40px"
| Back || Alt+Left || || Go to previous page.
|- style="height:40px"
| Next Tab || Ctrl+PageUp || || Activate the next Tab.
|- style="height:40px"
| Previous Tab || Ctrl+PageDown || || Activate the previous Tab.
|- style="height:40px"
| Next Major Panel || F6 || || Switches focus to the next major panel, e.g. sidebar or content panel in a file manager. Useful to get focus from dockers back to the main window when.
|- style="height:40px"
| Resize Split Pane || F8 || || Switches focus from one split pane to another to resize them via the arrow keys.
|- style="height:40px"
| colspan="4" | Text Navigation
|- style="height:40px"
| Beginning of line || Home || || Move cursor to the beginning of the line.
|- style="height:40px"
| End of line || End || || Move cursor to the beginning of the line.
|- style="height:40px"
| End || Ctrl+End ||
|- style="height:40px"
| Forward Word || Ctrl+Right || || Move cursor to the beginning of the next word.
|- style="height:40px"
| Backward Word || Ctrl+Left || || Move cursor to the beginning of the previous word.
|- style="height:40px"
| colspan="4" | Text Completion
|- style="height:40px"
| Substring completion || Ctrl+T || || Toggle substring completion.
|- style="height:40px"
| Text Completion || Ctrl+E || || Toggle text completion.
|- style="height:40px"
| Next item in list || Down || || Select the next item in the completion list.
|- style="height:40px"
| Previous item in list || Up || || Select the previous item in the completion list.
|- style="height:40px"
| Next completion match || Ctrl+Down || || Select the next completion match.
|- style="height:40px"
| Previous completion match || Ctrl+Up || || Select the previous completion match.
|}

F8 and F6 may still be used differently, if the window has no split panes (F8) or the definition of main panels is not required, e.g. if there are no dockers (F6). 

=== Standard System Shortcuts ===

{| border="1" cellpadding="5"
|- style="height:40px"
! width="50" | Key !! width="250" | Comment
|- style="height:40px"
| colspan="2" | Navigation
|- style="height:40px"
| Alt+Tab || Walk through windows
|- style="height:40px"
| Alt+Shift+Tab || Walk through windows (reverse)
|- style="height:40px"
| Ctrl+Tab || Focus to next widget (e.g. to get focus out of text fields).
|- style="height:40px"
| Ctrl+Shift+Tab || Focus to previous widget (e.g. to get focus out of text fields).
|- style="height:40px"
| Ctrl+F1 – F4 || Switch to desktop 1 to 4
|- style="height:40px"
| Ctrl+Alt+Tab || Switch focus between panel and desktop
|- style="height:40px"
| Ctrl+Alt+Right || Switch to next desktop
|- style="height:40px"
| Ctrl+Alt+Left || Switch to previous desktop
|- style="height:40px"
| Ctrl+Alt+Shift+Tab || Switch focus between panel and desktop (reverse)
|- style="height:40px"
| colspan="2" | Windows
|- style="height:40px"
| Alt+F3 || Window operations menu
|- style="height:40px"
| Alt+F4 || Close Window
|- style="height:40px"
| colspan="2" | Miscellaneous
|- style="height:40px"
| Alt+F12 || Mouse Emulation
|- style="height:40px"
| Ctrl+Alt+Escape || Kill window
|- style="height:40px"
| Alt+Print || Window screenshot
|- style="height:40px"
| Ctrl+Print || Desktop screenshot
|- style="height:40px"
| colspan="2" | Panel
|- style="height:40px"
| Alt+F1 || Popup launch menu
|- style="height:40px"
| Ctrl+Alt+D || Toggle showing (empty) desktop
|- style="height:40px"
| colspan="2" | Desktop
|- style="height:40px"
| Alt+F2 || Run command
|- style="height:40px"
| Ctrl+Escape || Show taskmanager
|- style="height:40px"
| Alt+F5 || Show windowlist
|- style="height:40px"
| Alt+Ctrl+L || Lock session
|- style="height:40px"
| colspan="2" | Clipboard
|- style="height:40px"
| Ctrl+Alt+V || Show Klipper popup menu
|- style="height:40px"
| Ctrl+Alt+R || Manually invoke action on current clipboard
|- style="height:40px"
| Ctrl+Alt+X || Enable/disable clipboard actions
|- style="height:40px"
| colspan="2" || Keyboard
|- style="height:40px"
| Ctrl+K || Switch to next keyboard layout
|}

=== Implementation Notes ===

Keyboard accelerators - classes helping to establish consistent key bindings throughout the desktop.
* [http://api.kde.org/3.5-api/kdelibs-apidocs/kdecore/html/classKAccel.html KAccel] - collection of keyboard shortcuts.
* [http://api.kde.org/3.5-api/kdelibs-apidocs/kdecore/html/classKStdAccel.html KStdAccel] - easy access to the common keyboard shortcut keys.
* [http://api.kde.org/3.5-api/kdelibs-apidocs/kdecore/html/classKGlobalAccel.html KGlobalAccel] - collection of system-wide keyboard shortcuts

Projects/Usability/HIG/Keyboard Shortcuts

2009-01-12T14:32:08Z

Seele: added an exception to Ctrl+W

Keyboard shortcuts help users perform common actions quickly through the keyboard instead of accessing the functionality in the UI with a mouse.

=== Global Keyboard Shortcuts ===

{| border="1" cellpadding="5"
|- style="height:40px"
! width="200" | Action !! width="50" | Key !! width="50" | Altern. !! width="250" | Comment
|- style="height:40px"
| colspan="4" | File Menu
|- style="height:40px"
| New || Ctrl+N || || Create a new document
|- style="height:40px"
| Open || Ctrl+O || || Open a document
|- style="height:40px"
| Save || Ctrl+S || || Save the current document
|- style="height:40px"
| Save As || Ctrl+Shift+S || ||Save the current document
|- style="height:40px"
| Reload || F5 || || Reload the current document/view
|- style="height:40px"
| Print || Ctrl+P || || Print the current document
|- style="height:40px"
| Close || Ctrl+W || || Close the current document. If there is only one document open, this shortcut '''may not''' Close the window or Quit the application.
|- style="height:40px"
| Quit || Ctrl+Q || || Quit the application
|- style="height:40px"
| colspan="4" | Edit menu
|- style="height:40px"
| Undo || Ctrl+Z || || Undo the last operation
|- style="height:40px"
| Redo || Ctrl+Y || Shift+Ctrl+Z || Redo the last undone operation
|- style="height:40px"
| Cut || Ctrl+X || Shift+Delete || Cut the selected area and store it in the clipboard
|- style="height:40px"
| Copy || Ctrl+C || Ctrl+Insert || Copy the selected area into the clipboard
|- style="height:40px"
| Paste || Ctrl+V || Shift+Insert || Paste contents of clipboard at mouse/cursor position
|- style="height:40px"
| Select All || Ctrl+A || || Select everything in the contents area
|- style="height:40px"
| Deselect || Ctrl+Shift+A || || Deselect everything in the contents area
|- style="height:40px"
| Find || Ctrl+F || || Find
|- style="height:40px"
| Find Next || F3 || || Find the next match
|- style="height:40px"
| Find Previous || Shift+F3 || || Find previous match
|- style="height:40px"
| Replace || Ctrl+R || || Find and replace matches
|- style="height:40px"
| Delete word forward || Ctrl+Delete || || Delete word from current cursor location to the end.
|- style="height:40px"
| Delete word backward || Ctrl+Backspace || || Delete word from beginning to current cursor location.
|- style="height:40px"
| Go to line... || Ctrl+G || || Move cursor to the corresponding line.
|- style="height:40px"
| colspan="4" | View Menu
|- style="height:40px"
| Full Screen Mode || Ctrl+Shift+F || || Toggle full screen mode
|- style="height:40px"
| colspan="4" | Zoom menu
|- style="height:40px"
| Zoom In || Ctrl++ || Ctrl+= || Zoom in to the document (magnify)
|- style="height:40px"
| Zoom Out || Ctrl+- || || Zoom out of the document
|- style="height:40px"
| Zoom to 100% || Ctrl+0 ||
|- style="height:40px"
| colspan="4" | Bookmarks menu
|- style="height:40px"
| Add Bookmark || Ctrl+B || || Add a bookmark for the current location
|- style="height:40px"
| colspan="4" | Help menu
|- style="height:40px"
| Help || F1 || || Obtain help and documentation for the application
|- style="height:40px"
| What's This || Shift+F1 || || Obtain a short help for the currently visible interface elements.
|- style="height:40px"
| colspan="4" | Navigation
|- style="height:40px"
| Focus to Menu || F10 || || Focus the menu bar.
|- style="height:40px"
| Show Context Menu || Ctrl+F10 || Menu || Show the context menu.
|- style="height:40px"
| Toggle Menu bar || Ctrl+M || || Toggle the appearance of the menu bar.
|- style="height:40px"
| Page Down || Space || PageDown || Scroll down one Screen, displaying the next page if the application normally displays a page at a time.
|- style="height:40px"
| Page Up || Shift+space || PageUp || Scroll up one Screen, displaying the previous page if the application normally displays a page at a time.
|- style="height:40px"
| Forward || Alt+Right || || Go to next page.
|- style="height:40px"
| Back || Alt+Left || || Go to previous page.
|- style="height:40px"
| Next Tab || Ctrl+PageUp || || Activate the next Tab.
|- style="height:40px"
| Previous Tab || Ctrl+PageDown || || Activate the previous Tab.
|- style="height:40px"
| Next Major Panel || F6 || || Switches focus to the next major panel, e.g. sidebar or content panel in a file manager. Useful to get focus from dockers back to the main window when.
|- style="height:40px"
| Resize Split Pane || F8 || || Switches focus from one split pane to another to resize them via the arrow keys.
|- style="height:40px"
| colspan="4" | Text Navigation
|- style="height:40px"
| Beginning of line || Home || || Move cursor to the beginning of the line.
|- style="height:40px"
| End of line || End || || Move cursor to the beginning of the line.
|- style="height:40px"
| End || Ctrl+End ||
|- style="height:40px"
| Forward Word || Ctrl+Right || || Move cursor to the beginning of the next word.
|- style="height:40px"
| Backward Word || Ctrl+Left || || Move cursor to the beginning of the previous word.
|- style="height:40px"
| colspan="4" | Text Completion
|- style="height:40px"
| Substring completion || Ctrl+T || || Toggle substring completion.
|- style="height:40px"
| Text Completion || Ctrl+E || || Toggle text completion.
|- style="height:40px"
| Next item in list || Down || || Select the next item in the completion list.
|- style="height:40px"
| Previous item in list || Up || || Select the previous item in the completion list.
|- style="height:40px"
| Next completion match || Ctrl+Down || || Select the next completion match.
|- style="height:40px"
| Previous completion match || Ctrl+Up || || Select the previous completion match.
|}

F8 and F6 may still be used differently, if the window has no split panes (F8) or the definition of main panels is not required, e.g. if there are no dockers (F6). 

=== Standard System Shortcuts ===

{| border="1" cellpadding="5"
|- style="height:40px"
! width="50" | Key !! width="250" | Comment
|- style="height:40px"
| colspan="2" | Navigation
|- style="height:40px"
| Alt+Tab || Walk through windows
|- style="height:40px"
| Alt+Shift+Tab || Walk through windows (reverse)
|- style="height:40px"
| Ctrl+Tab || Focus to next widget (e.g. to get focus out of text fields).
|- style="height:40px"
| Ctrl+Shift+Tab || Focus to previous widget (e.g. to get focus out of text fields).
|- style="height:40px"
| Ctrl+F1 – F4 || Switch to desktop 1 to 4
|- style="height:40px"
| Ctrl+Alt+Tab || Switch focus between panel and desktop
|- style="height:40px"
| Ctrl+Alt+Right || Switch to next desktop
|- style="height:40px"
| Ctrl+Alt+Left || Switch to previous desktop
|- style="height:40px"
| Ctrl+Alt+Shift+Tab || Switch focus between panel and desktop (reverse)
|- style="height:40px"
| colspan="2" | Windows
|- style="height:40px"
| Alt+F3 || Window operations menu
|- style="height:40px"
| Alt+F4 || Close Window
|- style="height:40px"
| colspan="2" | Miscellaneous
|- style="height:40px"
| Alt+F12 || Mouse Emulation
|- style="height:40px"
| Ctrl+Alt+Escape || Kill window
|- style="height:40px"
| Alt+Print || Window screenshot
|- style="height:40px"
| Ctrl+Print || Desktop screenshot
|- style="height:40px"
| colspan="2" | Panel
|- style="height:40px"
| Alt+F1 || Popup launch menu
|- style="height:40px"
| Ctrl+Alt+D || Toggle showing (empty) desktop
|- style="height:40px"
| colspan="2" | Desktop
|- style="height:40px"
| Alt+F2 || Run command
|- style="height:40px"
| Ctrl+Escape || Show taskmanager
|- style="height:40px"
| Alt+F5 || Show windowlist
|- style="height:40px"
| Alt+Ctrl+L || Lock session
|- style="height:40px"
| colspan="2" | Clipboard
|- style="height:40px"
| Ctrl+Alt+V || Show Klipper popup menu
|- style="height:40px"
| Ctrl+Alt+R || Manually invoke action on current clipboard
|- style="height:40px"
| Ctrl+Alt+X || Enable/disable clipboard actions
|- style="height:40px"
| colspan="2" || Keyboard
|- style="height:40px"
| Ctrl+K || Switch to next keyboard layout
|}

=== Implementation Notes ===

Keyboard accelerators - classes helping to establish consistent key bindings throughout the desktop.
* [http://api.kde.org/3.5-api/kdelibs-apidocs/kdecore/html/classKAccel.html KAccel] - collection of keyboard shortcuts.
* [http://api.kde.org/3.5-api/kdelibs-apidocs/kdecore/html/classKStdAccel.html KStdAccel] - easy access to the common keyboard shortcut keys.
* [http://api.kde.org/3.5-api/kdelibs-apidocs/kdecore/html/classKGlobalAccel.html KGlobalAccel] - collection of system-wide keyboard shortcuts

Projects/Usability/HIG/Form Label Alignment

2009-01-12T13:34:28Z

Seele:

One of the new changes in KDE 4.x since KDE 3.x is the alignment of form and widget labels. In KDE 3.x, labels were aligned to the left and widgets were aligned to the left. In KDE 4, form labels are now aligned to the right and widgets are aligned to the left, making a group of form widgets appear to be center aligned.

[[Image:Wiki-alignment-1.png|frame|Example of KDE 3 form alignment]]

[[Image:Wiki-alignment-3.png|frame|Example of KDE4 form alignment]]

== Dialog Alignment ==

In OSX, a group of widgets is center aligned. In KDE4, a group of widgets is left aligned. This aligns the labels closer to the left edge and makes use of space more efficiently.

[[Image:Wiki-alignment-2.png|frame|Example of OSX form alignment]]

[[Image:Wiki-alignment-3.png|frame|Example of KDE4 form alignment]]

The alignment of groups of widgets is independent, and so you may have different sized groups with different "centered" lines. A group of widgets consists of widgets within some type of natural separation such as a group box or separator bar.

[[Image:Wiki-alignment-4.png|frame|Example of multiple group alignment in KDE4]]

== Checkboxes ==

=== Problems with QT 4 ===

The checkbox widget in QT 4 is the input click box on the left and the label on the right. Unfortunately, it difficult to create a checkbox with a label on the right of the input click box. This is a problem because there are common cases when the label on the left of the input click box is better usability. Until there is a resolution that makes configuring the checkbox label to the left of the input click box easier, use the default checkbox alignment (right aligned label), or if possible, put a right-aligned label next to the checkbox, and set the label of the checkbox to "Enabled", "On", or similar.

[[Image:Wiki-alignment-5.png|frame|Example of aligning checkboxes until there Qt offers an option to align the checkbox label to the left.]]

== Aligning Sub-Options ==

When options are subordinate to a checkbox or radiobutton (e.g. Audio level can only be set if the Activate Audio option is selected), this relation should be visualized by indenting the sub-options. There are two options to do so:

# When you are using a left-aligned checkbox or radio button, indent the sub-options by using a horizontal spacer of SizeType "Minimum".

[[Image:Wiki-alignment-7.png|frame|Example of aligning sub-options with a horizontal spacer of SizeType "Minimum".]]

# When you are using a checkbox that is placed right to its label, indent the sub-options in the same vertical axis as the checkbox.

[[Image:Wiki-alignment-5.png|frame|Example of aligning sub-options with the same vertical axis as the checkbox itself.]]

'''The contents of this guideline are under discussion. Please request guidance in #kde-usability if you have any questions regardling Form Label Alignment'''

== Grouping related options within a GroupBox ==

In some cases it may be useful to visually separate groups of related options within one GroupBox to facilitate scanning of the dialog.

In that case, put a vertical fixed size spacer of 16px height between the options.

[[Image:Wiki-alignment-6.png|frame|Example of separating groups of related options with a vertical spacer.]]

== Examples ==

[Screenshots of example dialog layouts simple and complex]

== More Information ==

[http://www.uxmatters.com/MT/archives/000107.php Label Placement in Forms]

Projects/Usability/HIG/Date Time

2009-01-12T13:32:20Z

Seele: cleanup.. still needs screenshots and some guidelines

== Date and Time ==

'''Date / Time Widget:'''
* When a user must select a single date and time use the KDE Date/Time widget

''' Start and End Date/Time:'''
* When users must select a start and end date/time, make the default end date/time aware of the start date/time (i.e. when the user sets a start date, switch the end date at least to the same date)

Projects/Usability/HIG/Capitalization

2009-01-12T13:29:26Z

Seele:

There are two types of capitalization, title capitalization and sentence style capitalization.

This Is an Example of Title Capitalization

This is an example of sentence capitalization

==Title Capitalization==

Title capitalization is when every word in a sentence, statement, phrase, or label are capitalized except for certain words. Capitalize all words except for:
* Prepositions having less than five letters, (e.g. "for", "in", "with" or "to", but "From" or "Under")
* Conjunctions ("and", "or" and "but")
* Articles ("the", "a" and "an")

Use '''title capitalization''' in the following cases:
* Window and dialog box titles
* Group box / group line labels
* Button labels
* Tab labels
* Listview column headers
* Menu titles / menu items
* Derivatives of KCommand
* Combobox items
* Listbox items
* Tree list items
* Other heading/title text

==Sentence Style Capitalization==

Sentence style capitalization is when the first letter of the sentence, statement, phrase, or label is capitalized and all other words are lower case. The only exception to this is proper nouns which are always capitalized.

Use '''sentence style capitalization''' in the following cases:
* Edit box labels
* List box labels
* Combo box labels
* Spin box labels
* Check box labels
* Option button labels
* Spin box labels
* Slider labels
* Pop-up hint text
* Dialog header/description
* Other non heading/title text

[[Category:HIG]]

Projects/Usability/KDE4.3 Defaults

2008-10-29T16:00:38Z

Seele:

Some ideas/recommendations for changes to defaults for 4.3

* Toolbars
** Global toolbar settings fixed. This may be due to bugs in applications and not the settings. In some apps, half of the toolbar icons will be configured correctly and the other half do not obey the configured option
** Lock toolbars so they can't be dragged and moved
** Tiny toolbar icons plus label beside icon
*** Icons only for certain applications such as KOffice (#icons on toolbar > label usability) and Konqueror (navigation controls are easily learned)
* Close button on Konq tabs
* Modified logout menu where only the selected option is listed (a la Kubuntu Intrepid)
* Settings vs. View -- What goes in here?
* Default window size
** A number of applications need fixed (e.g. Ktorrent, System Monitor)

Projects/Usability/KDE4.3 Defaults

2008-10-29T14:51:31Z

Seele:

Some ideas/recommendations for changes to defaults for 4.3

* Lock toolbars
* Close button on Konq tabs
* Tiny toolbar icons plus label beside icon
** Icons only for certain applications such as KOffice (#icons on toolbar > label usability) and Konqueror (navigation controls are easily learned)

Projects/Usability/KDE4.3 Defaults

2008-10-29T14:49:27Z

Seele: New page: Some ideas/recommendations for changes to defaults for 4.3 * Lock toolbars * Close button on Konq tabs * Tiny toolbar icons plus label beside icon

Some ideas/recommendations for changes to defaults for 4.3

* Lock toolbars
* Close button on Konq tabs
* Tiny toolbar icons plus label beside icon

Projects/Mobile/KDE4 on n810

2008-10-22T16:37:10Z

Seele: New page: ==Flash your n810 with the R&D version of Nokia OS== * Optional: Create backup on internal storage device (original state) * Download [http://tablets-dev.nokia.com/d3.php flasher-3.0] and ...

==Flash your n810 with the R&D version of Nokia OS==
* Optional: Create backup on internal storage device (original state)
* Download [http://tablets-dev.nokia.com/d3.php flasher-3.0] and [http://tablets-dev.nokia.com/nokia_N810.php Nokia OS2008] to the computer you will be flashing the n810 from
* You will need your Product ID (MAC address) to download the Nokia OS. It can be found on your n810 in the Control Panel in About the product, or printed on your battery.
* Turn off your n810 and unplug the power supply; be sure it is fully charged
* Attach the USB cable to your n810 and computer.
* Flash with diablo
sudo ./flasher-3.0 -F RX-44_DIABLO_4.2008.23-14_PR_COMBINED_MR0_ARM.bin -f -R
* When you get the message "Suitable USB device not found, waiting", plug the power supply in to the n810. The flashing will commence.
* When prompted, reboot the n810. You can also disconnect the USB cable.

==Setup Partitions and Boot Menu==
* After booting in to the freshly flashed system...
* Setup networking on the device; this may involve typing your WPA key if it is a secure network.
* '''Do NOT''' install the Nokia Operating System update that's offered by the flashing button in the top bar, that will cause a mismatch in the initfs version and you won't get the boot menu
* Open the Application manager and enable the maemo Extras repository
* Install openssh and set root password
* Optional: Create another backup (mainly as shortcut for enabling the extras repository
* As root, ssh into the n810. /sbin/ifconfig will tell you the associated IP address if you don't know it.
* Install wget and download install-tools-N810e.deb in to /root
apt-get install wget
cd /root
wget http://penguinbait.com/install-tools-N810e.deb
* Unmount your external media card; if they are not already mounted you don't have to do this
umount /media/mmc1
umount /media/mmc2
* Install the n810 install tools. You cannot access the internal or external memory card in this process, otherwise you'll get an error from the clone package. Installing the package will repartition and formatsyour SD card and will '''ERASE''' all the data on it, so be careful when doing it. This process also clones the maemo system on the flash onto the SD card. When run successfully.
dpkg -i install-tools-N810e.deb
* If this process fails, it is probably because you didn't umount your external media. The medial is unmounted during this process so just try installing the install tools again.
* Reboot the n810

==Install KDE4==
* During the boot up, hold the memory key (lower left on the drawer keyboard, right under the direction pad) and you'll get a boot menu. Choose the third option (External MMC card) to boot from SD, the first one will boot from flash.
* From your computer, use Kwrite or Kate, and point it to sftp://root@192.168.1.14/etc/apt/sources.list.d/hildon-application-manager.list and add Marijn's repos. Alternatively you can ssh in to the n810 and edit the file with vi. Here is my complete list of repositories:

deb http://catalogue.tableteer.nokia.com/certified/ diablo user
deb http://catalogue.tableteer.nokia.com/non-certified/ diablo user
deb http://catalogue.tableteer.nokia.com/updates/diablo/ ./
deb http://repository.maemo.org/extras/ diablo free non-free
deb http://repository.maemo.org/extras-devel/ diablo free non-free
deb http://93.157.1.37/~marijn/maemo binary/
deb http://qt4.garage.maemo.org/ diablo extras

* SSH in to the n810 and update the package list
apt-get update,
* Remove the install tools since you don't need them anymore
dpkg --purge install-tools-n810e
* Install KDE4. This should pull in all the necessary dependencies (75MB of packages) as well. I had to force install kdebase-workspace to start plasma on the device. You can do that from a remote ssh session with su user and setting the display export DISPLAY=:0.
apt-get install kdebase-workspace kdebase-runtime kdeplasma-addons
* If that all works, you can replace the hildon desktop with plasma. At the moment it crashes and reboots the n810, so you might not want to do this.
cd /usr/bin/ && mv hildon-desktop hildon-desktop-real && ln -s plasma hildon-desktop
* Have fun!

This is an updated version of [http://vizzzion.org/stuff/howto-dualboot.txt Sebas' HowTo].

Projects/Usability/HIG/Menu Bar

2008-09-13T23:56:53Z

Seele: added guideline in response to bug 143119

The menubar appears at the top of a main window and provides access to all commands and most of the settings available in an application. It contains menu titles which describe the content of each menu. Each menu title is accessible by accelerator keys, which must be set by the developer.

=== Guidelines ===

* Group menus in consistency with the KDE standard menu bar.
* Provide a menubar in every application main window
* Menu item titles should be listed in a standard order
* Menu titles on a menubar appear as a single word with the first letter capitalized
* Provide accelerator keys for every menu title in the menubar
* Turning "on" an item in the menu should always enable the option. Negative options create a double negative which can be confusing. For example, use "Show hidden files" instead of "Hide hidden files".
* '''Don't''' display menubars in secondary or internal windows
* '''Don't''' disable menu titles even if no items under that menu are available
* '''Don't''' use compound words (e.g. ToolOptions), and hyphens (e.g. Tool-Options) in label names; they make words harder to read and recognize
* '''Don't''' make the menubar 'hideable', users may not easily be able to make the menubar viewable again

====Example: Standard Menu Bar====

This is the order of menu items in a standard menu bar. If an application does not have options under one of the standard menu items, do not include it in the menu. At the minimum, all windows should have a File (or File equivalent, such as in the case if Konqueror and Amarok) and Help menu.

| File | Edit | View | Insert | Format | ''Application Specific Menus'' | Go | Bookmarks | Tools | Settings | Window | Help |

Projects/Usability/HIG/Dialogs

2008-09-13T23:32:30Z

Seele:

== Dialogs ==
'''Reduce the dialog flood'''
* Do not nest dialogs more than two levels deep. For example "Configuration dialog > Advanced dialog" is ok, "Configuration dialog > Advanced dialog > Further settings dialog" is too deep.
* Avoid dialogs that contain only one or two options. If possible, use [[Design_and_Layout:Interaction:Input#Inline Editing|inline-editing]] instead.
* Do not use dialogs to display non-critical messages which do not require any further user interaction (typically dialogs with a single "OK" or "Close" button). Use [[Guidelines:Info Panel|info panels]] instead.

'''Position of dialogs'''
* Always keep dialogs on top of their parent. This is usually taken care of by the window manager. But in composed applications, focus problems may occur. Check carefully in this case.
* If reference in the parent window is required, make sure your dialog does not cover relevant parts. For example a find dialog should neither be centered, nor cover a search result.

'''Interaction'''
* Set input focus on confirmation button.

'''Only use modal dialogs when''':
* Use modal dialogs only if allowing interaction with other parts of the application while the window is open could cause data loss or some other serious problem.
Provide a clear way of leaving the modal dialog, such as a Cancel button in an alert.

== Dialog Layout ==

* Design dialogs not to be bigger than 800x600 Pixels and should always be resizable
* Make sure there is at least one third white space, do not overload the panel.
* The reading direction in dialogs is left to right, top to bottom.
* Dialogs are grouped in meaningful sections. The actions are grouped along their context of use, not along technical relations.
* Each section has a title.
* Labels are right-aligned, input widgets are left aligned.
* Provide one or two major vertical axis in your dialog that guide the user's attention. The vertical line where the right aligned labels and the left aligned input widgets meet is one such example.
* Widgets which are subordinate to another widget are indented. If their enabled state depends on the parent widget, create an appropriate slot.

Otherwise, follow the guidelines described in [[Projects/Usability/HIG/Form_Label_Alignment|Form: Label Alignment]]

=== See Also ===
* [[Projects/Usability/HIG/Tabs_Pages|Tabs and Pages in Dialogs]]
* [[Projects/Usability/HIG/Form_Label_Alignment|Form: Label Alignment]]

Projects/Usability/HIG/Dialogs

2008-09-13T23:32:04Z

Seele:

== Dialogs ==
'''Reduce the dialog flood'''
* Do not nest dialogs more than two levels deep. For example "Configuration dialog > Advanced dialog" is ok, "Configuration dialog > Advanced dialog > Further settings dialog" is too deep.
* Avoid dialogs that contain only one or two options. If possible, use [[Design_and_Layout:Interaction:Input#Inline Editing|inline-editing]] instead.
* Do not use dialogs to display non-critical messages which do not require any further user interaction (typically dialogs with a single "OK" or "Close" button). Use [[Guidelines:Info Panel|info panels]] instead.

'''Position of dialogs'''
* Always keep dialogs on top of their parent. This is usually taken care of by the window manager. But in composed applications, focus problems may occur. Check carefully in this case.
* If reference in the parent window is required, make sure your dialog does not cover relevant parts. For example a find dialog should neither be centered, nor cover a search result.

'''Interaction'''
* Set input focus on confirmation button.

'''Only use modal dialogs when''':
* Use modal dialogs only if allowing interaction with other parts of the application while the window is open could cause data loss or some other serious problem.
Provide a clear way of leaving the modal dialog, such as a Cancel button in an alert.

== Dialog Layout ==

* Design dialogs not to be bigger than 800x600 Pixels and should always be resizable
* Make sure there is at least one third white space, do not overload the panel.
* The reading direction in dialogs is left to right, top to bottom. In a row, related options may be positioned next to each other, like "Access" and "Show time as" like in the example screenshot.
* Dialogs are grouped in meaningful sections. The actions are grouped along their context of use, not along technical relations.
* Each section has a title.
* Labels are right-aligned, input widgets are left aligned.
* Provide one or two major vertical axis in your dialog that guide the user's attention. The vertical line where the right aligned labels and the left aligned input widgets meet is one such example.
* Widgets which are subordinate to another widget are indented. If their enabled state depends on the parent widget, create an appropriate slot.

Otherwise, follow the guidelines described in [[Projects/Usability/HIG/Form_Label_Alignment|Form: Label Alignment]]

=== See Also ===
* [[Projects/Usability/HIG/Tabs_Pages|Tabs and Pages in Dialogs]]
* [[Projects/Usability/HIG/Form_Label_Alignment|Form: Label Alignment]]

Projects/Usability/HIG/Tabs Pages

2008-08-11T20:06:44Z

Seele:

==Tabs and Pages in Dialogs==

'''General Guidelines'''

If a control affects only one tab or page in the dialog, place it on that tab/page. If it affects every tab/page in the dialog, place it outside, for example beside the window's OK and Cancel buttons.

Make sure changes on one tab will not change options on another tab.

===Tabbed Dialogs===

'''When to Use'''

Use tabbed dialogs when you have a limited number of tabs (max. 6).
If you cannot see all the tabs without scrolling or splitting them into multiple rows, you are probably using too many and should use a paged dialog instead.

===Paged Dialogs===

'''When to Use'''

Always use paged dialogs for configuration dialogs - assuming that there is more than one section of options to be configured.
For other dialogs, use paged dialogs if there are too many tabs to put them into a tabbed dialog.

===Accessibility===
Do not assign accelerator keys to tab and paged dialog labels. Assign an access key to every other control on each page, however.

=== See Also ===
* [[Projects/Usability/HIG/Dialogs|Dialogs]]

Projects/Usability/HIG/Labels

2008-08-11T20:04:44Z

Seele: update formatting

==Labels==

'''Spacing and Alignment'''

See [[Projects/Usability/HIG/Form_Label_Alignment|Form Label Alignment]]

'''Language'''

Keep labels short - Be aware that translated English text can expand up to 30% in some languages.

Do not shorten your labels to the point of losing meaning, however.
A three-word label that provides clear information is better than a one-word label that is ambiguous or vague. Try to find the fewest possible words to satisfactorily convey the meaning of your label.

'''Capitalization'''

See [[Projects/Usability/HIG/Capitalization|Captitalization]]

'''Keyboard Accelerators'''

See [[Projects/Usability/HIG/Keyboard_Accelerators|Keyboard Accelerators]]

Projects/Usability/HIG/Labels

2008-08-11T20:02:45Z

Seele: update link

==Labels==

'''Spacing and Alignment:'''
See [[Projects/Usability/HIG/Form_Label_Alignment|Form Label Alignment]]

'''Language:'''
Keep labels short - Be aware that translated English text can expand up to 30% in some languages.

Do not shorten your labels to the point of losing meaning, however.
A three-word label that provides clear information is better than a one-word label that is ambiguous or vague. Try to find the fewest possible words to satisfactorily convey the meaning of your label.

'''Capitalization:'''
See [[Projects/Usability/HIG/Capitalization|Captitalization]]

'''Keyboard Accelerators:'''
See [[Projects/Usability/HIG/Keyboard_Accelerators|Keyboard Accelerators]]

Projects/Usability/HIG/Messages

2008-08-11T20:00:38Z

Seele: update formatting

== Messages ==

Messages include warnings, error messages, confirmation dialogs, and info messages.

===Language===

Messages should be:
* ''Understandable''. Phrase your messages clearly, in non-technical terms and avoid obscure error codes.
* ''Specific instead of general''. If the message is reporting a problem concerning a specific object or application, use the object or application name when referring to it.
* ''Informative and constructive''. Tell the user the reason for a problem and help on how to solve the problem.
* ''Polite, non-terrifying and non-blaming''. Avoid wording that terrifies the user ("fatal", "illegal"), blames him for his behavior, and be polite.

=== Confirmation Button Labels ===
When no further input is required:
* To close a warning or error message that does not require further user interaction, provide a Close button. '''Do not use an OK button.''' Users may get confused if they are asked to confirm an error.

When further interaction is required:
* Use buttons which '''match the type of statement or question''' made in the warning or error message. For example, do no ask a Yes/No question but then provide OK/Cancel buttons.

* When the user must choose between two actions to continue, use '''descriptive button labels''' instead of standard Yes/No or OK/Cancel buttons. For example, if the user must choose to continue or stop an action, provide the buttons "Continue" and "Cancel".

=== Details ===
* Provide only a short error message and complement it by a Details button that provides more a detailed explanation in the same error dialog.

* If it makes sense for this kind of error, link from the error dialog to the corresponding page in the help system. Provide a Help button then.

=== Dialog vs. Info Panel ===
* Use dialogs for critical error messages, and when you need to make sure that the user sees the message.

* Use info panels for non-critical messages which do not require any further user interaction (typically dialogs with a single "OK" or "Close" button).

Projects/Usability/HIG

2008-08-11T13:22:14Z

Seele: add label alignment

__NOTOC__
Please add any guidelines questions or requests to the [[Projects/Usability/HIG_Questions|HIG Questions]] page.

Also see the [http://developer.kde.org/documentation/standards/kde/style/basics/index.html KDE3 User Interface Guidelines] and the draft notes for the [http://wiki.openusability.org/guidelines/ KDE4 Human Interface Guidelines].

==Index==
===C===
* [[Projects/Usability/HIG/Capitalization|Capitalization]]
* [[Projects/Usability/HIG/Check_Box|Check Box]]
* [[Projects/Usability/HIG/Combo_Box|Combo Box]]

===D===
* [[Projects/Usability/HIG/Date_Time|Date and Time]]
* [[Projects/Usability/HIG/Dialogs|Dialogs]]

===E===
* [[Projects/Usability/HIG/Ellipsis|Ellipsis]]

===F===
* [[Projects/Usability/HIG/Form_Label_Alignment|Forms: Label Alignment]]

===K===
* [[Projects/Usability/HIG/Keyboard_Accelerators|Keyboard Accelerators]]
* [[Projects/Usability/HIG/Keyboard_Shortcuts|Keyboard Shortcuts]]

===L===
* [[Projects/Usability/HIG/Labels|Labels]]
* [[Projects/Usability/HIG/Lists_Rich_Lists|Lists and Rich Lists]]

===M===
* [[Projects/Usability/HIG/Menu_Bar|Menu Bar]]
* [[Projects/Usability/HIG/Messages|Messages]]
===R===
* [[Projects/Usability/HIG/Radio Buttons|Radio Buttons]]
===S===
* [[Projects/Usability/HIG/Slider|Slider]]
* [[Projects/Usability/HIG/Spin_Box|Spin Box]]

===T===
* [[Projects/Usability/HIG/Tabs_Pages|Tabs and Pages in Dialogs]]

===W===
* [[Projects/Usability/HIG/Wording|Wording]]

[[Category:Usability]]

Projects/Usability/HIG/Form Label Alignment

2008-08-11T13:21:08Z

Seele: new content

File:Wiki-alignment-4.png

2008-08-11T12:32:41Z

Seele: Example of multiple group alignment in KDE4

Example of multiple group alignment in KDE4

File:Wiki-alignment-3.png

2008-08-11T12:05:01Z

Seele: Example of KDE4 form alignment

Example of KDE4 form alignment

File:Wiki-alignment-2.png

2008-08-11T12:03:02Z

Seele: Example of OSX form alignment

Example of OSX form alignment

File:Wiki-alignment-1.png

2008-08-11T12:00:12Z

Seele: Example of KDE 3 form alignment

Example of KDE 3 form alignment

Projects/Usability/HIG Questions

2008-08-11T08:47:43Z

Seele: update status

= KDE4 HIG Questions and Requests =

Developer, please use this page to add questions and requests about the KDE4 Human Interface Guidelines (HIG)

* Please list questions about the KDE4 HIG here
* Also include your name/IRC nick/email if you want to be contacted for follow up questions
* Be as specific as possible and include a screenshot if applicable. [http://lists.kde.org/?l=kde-usability&m=120955187622753&w=2 This email on the kde-usability mailing list] is a '''good''' example of a HIG question/request.

* Which buttons have icons and when should we use/not use icons on buttons?
* The growth policy: are widgets supposed to grow and take all the available (horizontal) space, even in case of widgets that don't have a size policy for expanding?
* Description of alignment rule. See: http://lists.kde.org/?l=kde-core-devel&m=121639074230037&w=2 and (IN PROGRESS)
* Should the horizontal alignment of the layout be left- or center-? (eg: [http://img186.imageshack.us/img186/33/formlayoutalignxv0.png sample screenshot])
* Some musing about [[Projects/Usability/HIG_Questions/Standard_Shortcuts | Standard Shortcuts]]
* <s>Remove or Delete for a button label?</s>
* Order of Add Copy Remove/Delete in forms
* <s>Options or Settings for a label?</s>
* Reorder buttons (Move up down top bottom), icons, icons with text, or buttons with text labels? (IN PROGRESS)
* Listviews: http://ktown.kde.org/~fredrik/listviews/ (IN PROGRESS)
* Visual style of notes/instructions in System Setting modules ([http://techbase.kde.org/Image:Systemsettings-information1.png Screenshot])
* when should tooltips be used? when is it too annoying and should be replaced by a "whats this?" function?
* Will the HIG specify a standard format and functions for the status bar?--[[User:JRT|JRT]] 03:02, 17 June 2008 (CEST)
* Will the HIG specify a minimum set of Zoom & View functions and specify which of these should be on the status bar and which should be in the Menu &/| Toolbars?--[[User:JRT|JRT]] 03:02, 17 June 2008 (CEST) (PLANNING)
* <s>I suggest adding a guideline to the checkboxes section saying that checkbox labels should always be "positively" formulated such as "enable ...". Never "disable ..." or even "Hide ..." (use "Show ..." instead. This contradicts what is currently in [[Projects/Usability/HIG/Check_Box | Check Box]]). If the user has to activate a checkbox to disactivate something this is like a double negation and induces unnecessary cognitive load. Also see: http://lists.kde.org/?l=kde-usability&m=121651903819214&w=2</s>
* [[Projects/Usability/HIG/Keyboard_Accelerators|Keyboard Accelerators page needs reformatted and updated]]

Projects/Usability/HIG/Wording

2008-08-11T08:42:45Z

Seele: new content

== Delete, Move to Trash, Remove, and Uninstall ==

When a file or object is completely removed from the system, use '''Delete''' .

When a file or object can be recovered, use '''Move to Trash''' for files and '''Remove''' for list objects etc.

When a file or object can be removed and was originally installed, use '''Uninstall'''.

== Settings, Options, and Properties ==

Use '''Settings''' for a configuration dialog which allows you to set specific properties or functionality. This usually applies to application configuration tools. For example, Konqueror Settings.

Use '''Options''' for a configuration dialog which provide. This usually applies to object configuration tools.

Use '''Properties''' for a list of metadata or details that are associated with a particular object which cannot be edited or interacted with in any way. For example, file "properties" dialog in Dolphin.

Projects/Usability/HIG

2008-08-11T08:42:31Z

Seele: add wording page

Projects/Usability/HIG Questions

2008-08-10T12:28:26Z

Seele: status update

= KDE4 HIG Questions and Requests =

Developer, please use this page to add questions and requests about the KDE4 Human Interface Guidelines (HIG)

* Please list questions about the KDE4 HIG here
* Also include your name/IRC nick/email if you want to be contacted for follow up questions
* Be as specific as possible and include a screenshot if applicable. [http://lists.kde.org/?l=kde-usability&m=120955187622753&w=2 This email on the kde-usability mailing list] is a '''good''' example of a HIG question/request.

* Which buttons have icons and when should we use/not use icons on buttons?
* The growth policy: are widgets supposed to grow and take all the available (horizontal) space, even in case of widgets that don't have a size policy for expanding?
* Description of alignment rule. See: http://lists.kde.org/?l=kde-core-devel&m=121639074230037&w=2 and (IN PROGRESS)
* Should the horizontal alignment of the layout be left- or center-? (eg: [http://img186.imageshack.us/img186/33/formlayoutalignxv0.png sample screenshot])
* Some musing about [[Projects/Usability/HIG_Questions/Standard_Shortcuts | Standard Shortcuts]]
* Remove or Delete for a button label?
* Order of Add Copy Remove/Delete in forms
* Options or Settings for a label?
* Reorder buttons (Move up down top bottom), icons, icons with text, or buttons with text labels?
* Listviews: http://ktown.kde.org/~fredrik/listviews/ (IN PROGRESS)
* Visual style of notes/instructions in System Setting modules ([http://techbase.kde.org/Image:Systemsettings-information1.png Screenshot])
* when should tooltips be used? when is it too annoying and should be replaced by a "whats this?" function?
* Will the HIG specify a standard format and functions for the status bar?--[[User:JRT|JRT]] 03:02, 17 June 2008 (CEST)
* Will the HIG specify a minimum set of Zoom & View functions and specify which of these should be on the status bar and which should be in the Menu &/| Toolbars?--[[User:JRT|JRT]] 03:02, 17 June 2008 (CEST) (PLANNING)
* <s>I suggest adding a guideline to the checkboxes section saying that checkbox labels should always be "positively" formulated such as "enable ...". Never "disable ..." or even "Hide ..." (use "Show ..." instead. This contradicts what is currently in [[Projects/Usability/HIG/Check_Box | Check Box]]). If the user has to activate a checkbox to disactivate something this is like a double negation and induces unnecessary cognitive load. Also see: http://lists.kde.org/?l=kde-usability&m=121651903819214&w=2</s>
* [[Projects/Usability/HIG/Keyboard_Accelerators|Keyboard Accelerators page needs reformatted and updated]]

Projects/Usability/HIG/Messages

2008-08-01T16:45:16Z

Seele:

Warning and error messages appear when a problem or error has occurred.

===Guidelines===
Warning and error messages should be:
* ''Understandable''. Phrase your messages clearly, in non-technical terms and avoid obscure error codes.
* ''Specific instead of general''. If the message is reporting a problem concerning a specific object or application, use the object or application name when referring to it.
* ''Informative and constructive''. Tell the user the reason for a problem and help on how to solve the problem.
* ''Polite, non-terrifying and non-blaming''. Avoid wording that terrifies the user ("fatal", "illegal"), blames him for his behavior, and be polite.

==== Confirmation Button Labels ====
* To close a warning or error message that does not require further user interaction, provide a Close button. '''Do not use an OK button.''' Users may get confused if they are asked to confirm an error.
* Use buttons which match the type of statement or question made in the warning or error message. For example, do no ask a Yes/No question but then provide OK/Cancel buttons.
* When the user must choose between two actions to continue, use descriptive button labels instead of standard Yes/No or OK/Cancel buttons. For example, if the user must choose to continue or stop an action, provide the buttons "Continue" and "Cancel".

==== Error Details ====
* Provide only a short error message and complement it by a Details button that provides more a detailed explanation in the same error dialog.
* If it makes sense for this kind of error, link from the error dialog to the corresponding page in the help system. Provide a Help button then.

==== Dialog vs. Info Panel ====
* Use dialogs for critical error messages, and when you need to make sure that the user sees the message.
* Use info panels for non-critical messages which do not require any further user interaction (typically dialogs with a single "OK" or "Close" button).

Projects/Usability/HIG/Spin Box

2008-08-01T16:44:34Z

Seele:

A spin box is a text box that accepts a range of values. It incorporates two arrow buttons that allow the user to increase or decrease the current value by a fixed amount.

===Guidelines===
* Use spin boxes for numerical input only. Use a list or option menu when you need the user to select from fixed data sets of other types.
* Use a spin box if the numerical value is meaningful or useful for the user to know, and the valid input range is unlimited or fixed at one end only. For example, a control for specifying the number of iterations of some action, or a timeout value. If the range is fixed at both ends, or the numerical values are arbitrary (for example, a volume control), use a slider control instead.
* Label the spin box with a text label above it or to its left, using sentence capitalization. Provide an access key in the label that allows the user to give focus directly to the spin box.
* Right-justify the contents of spin boxes, unless the convention in the user's locale demands otherwise. This is useful in windows where the user might want to compare two numerical values in the same column of controls. In this case, ensure the right edges of the relevant controls are also aligned.

Projects/Usability/HIG/Slider

2008-08-01T16:43:45Z

Seele:

(From GNOME guidelines)

A slider allows the user to quickly select a value from a fixed, ordered range, or to increase or decrease the current value. The control looks like the type of slider that you might find on an audio mixing desk or a hi-fi's graphic equalizer.

=== Guidelines ===
* Use a slider when adjusting the value relative to its current value is more important than choosing an absolute value. For example, a volume control: the average user will usually think about turning the volume up or down to make a sound louder or quieter, rather than setting the peak output to a specific decibel value.
* Use a slider when it is useful for the user to control the rate of change of the value in real time. For example, to monitor the effects of a color change in a live preview window as they drag the RGB sliders.
* Label the slider with a text label above it or to its left, using sentence capitalization. Provide an access key in the label that allows the user to give focus directly to the slider.
* Mark significant values along the length of the slider with text or tick marks. For example the left, right and center points on an audio balance control in Figure 6.7, “A simple slider control”.
* For large ranges of integers (more than about 20), and for ranges of floating point numbers, consider providing a text box or spin box that is linked to the slider's value. This allows the user to quickly set or fine-tune the setting more easily than they could with the slider control alone.

Projects/Usability/HIG/Slider

2008-08-01T16:42:47Z

Seele:

(From GNOME guidelines)

A slider allows the user to quickly select a value from a fixed, ordered range, or to increase or decrease the current value. The control looks like the type of slider that you might find on an audio mixing desk or a hi-fi's graphic equalizer.

Use a slider when:
* Adjusting the value relative to its current value is more important than choosing an absolute value. For example, a volume control: the average user will usually think about turning the volume up or down to make a sound louder or quieter, rather than setting the peak output to a specific decibel value.
* It is useful for the user to control the rate of change of the value in real time. For example, to monitor the effects of a color change in a live preview window as they drag the RGB sliders.

=== Guidelines ===
* Label the slider with a text label above it or to its left, using sentence capitalization. Provide an access key in the label that allows the user to give focus directly to the slider.
* Mark significant values along the length of the slider with text or tick marks. For example the left, right and center points on an audio balance control in Figure 6.7, “A simple slider control”.
* For large ranges of integers (more than about 20), and for ranges of floating point numbers, consider providing a text box or spin box that is linked to the slider's value. This allows the user to quickly set or fine-tune the setting more easily than they could with the slider control alone.

Projects/Usability/HIG/Radio Buttons

2008-08-01T16:41:14Z

Seele:

Radio buttons offer the user a choice of two or more mutually exclusive options. Try to limit the number of radio buttons and radio button groups in a dialog. Offering a high number of radio buttons consumes screen space and adds to visual clutter. At the same time, showing all available options at once is an advantage if users are likely not to know possible alternatives.

=== Guidelines ===
* Use radio buttons for 2 to 3 mutually exclusive options. If there are more than three options, use a combo box or list instead.
* Use radio buttons if the user should see the choices without further interaction.
* Provide a descriptive label above or left to a group of radio buttons in [[Projects/Usability/HIG/Capitalization|sentence style capitalization]].
* Use [[Projects/Usability/HIG/Capitalization|title style capitalization]] the radio button options.
* Align groups of radio buttons vertically rather than horizontally, as this makes them easier to scan visually. Use horizontal or rectangular alignments only if they greatly improve the layout of the window.
* Radio buttons are not dynamic; their content or labels should not change depending on the context.
* If toggling a radio button affects the enabled state of other controls, place the controls that it affects next to the radio button or below and indented.
* '''Don't''' initiate an action when the user clicks a radio button.

Projects/Usability/HIG/Menu Bar

2008-08-01T16:40:49Z

Seele:

The menubar appears at the top of a main window and provides access to all commands and most of the settings available in an application. It contains menu titles which describe the content of each menu. Each menu title is accessible by accelerator keys, which must be set by the developer.

=== Guidelines ===

* Group menus in consistency with the KDE standard menu bar.
* Provide a menubar in every application main window
* Menu item titles should be listed in a standard order
* Menu titles on a menubar appear as a single word with the first letter capitalized
* Provide accelerator keys for every menu title in the menubar
* '''Don't''' display menubars in secondary or internal windows
* '''Don't''' disable menu titles even if no items under that menu are available
* '''Don't''' use compound words (e.g. ToolOptions), and hyphens (e.g. Tool-Options) in label names; they make words harder to read and recognize
* '''Don't''' make the menubar 'hideable', users may not easily be able to make the menubar viewable again

====Example: Standard Menu Bar====

This is the order of menu items in a standard menu bar. If an application does not have options under one of the standard menu items, do not include it in the menu. At the minimum, all windows should have a File (or File equivalent, such as in the case if Konqueror and Amarok) and Help menu.

| File | Edit | View | Insert | Format | ''Application Specific Menus'' | Go | Bookmarks | Tools | Settings | Window | Help |

Projects/Usability/HIG/Ellipsis

2008-08-01T16:39:41Z

Seele:

An ellipsis is used after menu items and button labels which the user is either required or is able to provide input. An ellipsis is not used when the label implies and action and user input is not required to complete the activity. Configuration dialogs are a good example of this, the label already implies action and making changes is not necessary to complete an activity such as checking a setting.

=== Guidelines ===

* Use an ellipsis after menu items and button labels which require user’s input before completing their action.
* '''Don't''' use an ellipsis if user input is not required
* '''Don't''' use an ellipsis for selections which result in actions (such as Save or Print) or do not require user input (such as configuration dialogs).
* '''Don't''' use an ellipsis for an action which may require confirmation before it is completed (such as a Deletion confirmation).

'''Do''' use an ellipsis for the following menu items and buttons:
* Find...
* Find and Replace...
* Open...
* Print...
* Replace...
* Save As...
* Send To...

'''Do not''' use an ellipsis for the following menu items and buttons:
* About
* Advanced Options
* Check Spelling
* Close or Quit
* Configure [something]
* Delete or Remove
* Help
* Preferences
* Print Preview
* Properties
* Toolboxes

Projects/Usability/HIG/Combo Box

2008-08-01T16:38:54Z

Seele:

Combo boxes (also known as a dropdown box) offer the user a choice of two or more mutually exclusive options. Their disadvantage compared to related controls like radio buttons or lists is that the options are not visible without further interaction.

=== Guidelines ===

* For 3 or fewer options, use a set of [[Projects/Usability/HIG/Radio_Buttons|radio buttons]].
* For 4 to 10 options, use a combo box instead of radio buttons.
* For more than 10 options, use a list.
* Label the combo box with a descriptive label to the left of the combo box.
* Use sentence style capitalization for the label and the options.
* If activating a choice affects the appearance or the enabled state of other controls, place them next to the combo box or below the combo box with a space indentation.
* Make sure the items are easily accessible via keyboard by moving distinctive letters to the beginning of each option. For example, in a list of countries on continents, write ''Germany (Europe)'' instead of ''Europe/Germany''.
* '''Don't''' initiate an action when the user selects an item from a drop-down list.
* '''Don't''' forget to create a buddy relation so access keys are assigned.

Controls that show the options without further user interaction are preferable, except for the following cases:

* the list of options may change over time,
* the contents are obvious from the label and the one selected item, for example ''Month'' and ''January''
* the combo box is part of a related sequence of controls. For example, to set a reminder to ring 5 hours or minutes before or after an event.

Projects/Usability/HIG/Combo Box

2008-08-01T16:38:35Z

Seele:

Combo boxes (also known as a dropdown box) offer the user a choice of two or more mutually exclusive options. Their disadvantage compared to related controls like radio buttons or lists is that the options are not visible without further interaction.

=== Guidelines ===

* For 3 or fewer options, use a set of [[Projects/Usability/HIG/Radio_Buttons|radio buttons]].
* For 4 to 10 options, use a combo box instead of radio buttons.
* For more than 10 options, use a list.
* Label the combo box with a descriptive label to the left of the combo box.
* Use sentence style capitalization for the label and the options.
* If activating a choice affects the appearance or the enabled state of other controls, place them next to the combo box or below the combo box with a space indentation.
* Make sure the items are easily accessible via keyboard by moving distinctive letters to the beginning of each option. For example, in a list of countries on continents, write ''Germany (Europe)'' instead of ''Europe/Germany''.

* Don't initiate an action when the user selects an item from a drop-down list.
* Don't forget to create a buddy relation so access keys are assigned.

Controls that show the options without further user interaction are preferable, except for the following cases:

* the list of options may change over time,
* the contents are obvious from the label and the one selected item, for example ''Month'' and ''January''
* the combo box is part of a related sequence of controls. For example, to set a reminder to ring 5 hours or minutes before or after an event.

Projects/Usability/HIG/Combo Box

2008-08-01T16:38:19Z

Seele:

Combo boxes (also known as a dropdown box) offer the user a choice of two or more mutually exclusive options. Their disadvantage compared to related controls like radio buttons or lists is that the options are not visible without further interaction.

=== Guidelines ===

* For 3 or fewer options, use a set of [[Projects/Usability/HIG/Radio_Buttons|radio buttons]].
* For 4 to 10 options, use a combo box instead of radio buttons.
* For more than 10 options, use a list.
* Label the combo box with a descriptive label to the left of the combo box.
* Use sentence style capitalization for the label and the options.
* If activating a choice affects the appearance or the enabled state of other controls, place them next to the combo box or below the combo box with a space indentation.
* Make sure the items are easily accessible via keyboard by moving distinctive letters to the beginning of each option. For example, in a list of countries on continents, write ''Germany (Europe)'' instead of ''Europe/Germany''.

* Don't initiate an action when the user selects an item from a drop-down list.
* Don't forget to create a buddy relation so access keys are assigned.
Controls that show the options without further user interaction are preferable, except for the following cases:

* the list of options may change over time,
* the contents are obvious from the label and the one selected item, for example ''Month'' and ''January''
* the combo box is part of a related sequence of controls. For example, to set a reminder to ring 5 hours or minutes before or after an event.

Projects/Usability/HIG/Combo Box

2008-08-01T16:38:03Z

Seele:

Combo boxes (also known as a dropdown box) offer the user a choice of two or more mutually exclusive options. Their disadvantage compared to related controls like radio buttons or lists is that the options are not visible without further interaction.

=== Guidelines ===

* For 3 or fewer options, use a set of [[Projects/Usability/HIG/Radio_Buttons|radio buttons]].
* For 4 to 10 options, use a combo box instead of radio buttons.
* For more than 10 options, use a list.
* Label the combo box with a descriptive label to the left of the combo box.
* Use sentence style capitalization for the label and the options.
* If activating a choice affects the appearance or the enabled state of other controls, place them next to the combo box or below the combo box with a space indentation.
* Make sure the items are easily accessible via keyboard by moving distinctive letters to the beginning of each option. For example, in a list of countries on continents, write ''Germany (Europe)'' instead of ''Europe/Germany''.

* Don't initiate an action when the user selects an item from a drop-down list.
* Don't forget to create a buddy relation so access keys are assigned.

Controls that show the options without further user interaction are preferable, except for the following cases:

* the list of options may change over time,
* the contents are obvious from the label and the one selected item, for example ''Month'' and ''January''
* the combo box is part of a related sequence of controls. For example, to set a reminder to ring 5 hours or minutes before or after an event.

Projects/Usability/HIG/Radio Buttons

2008-08-01T16:37:12Z

Seele:

Radio buttons offer the user a choice of two or more mutually exclusive options. Try to limit the number of radio buttons and radio button groups in a dialog. Offering a high number of radio buttons consumes screen space and adds to visual clutter. At the same time, showing all available options at once is an advantage if users are likely not to know possible alternatives.

=== Guidelines ===
* Use radio buttons for 2 to 3 mutually exclusive options. If there are more than three options, use a combo box or list instead.
* Use radio buttons if the user should see the choices without further interaction.
* Provide a descriptive label above or left to a group of radio buttons in [[Projects/Usability/HIG/Capitalization|sentence style capitalization]].
* Use [[Projects/Usability/HIG/Capitalization|title style capitalization]] the radio button options.
* Align groups of radio buttons vertically rather than horizontally, as this makes them easier to scan visually. Use horizontal or rectangular alignments only if they greatly improve the layout of the window.
* Radio buttons are not dynamic; their content or labels should not change depending on the context.
* If toggling a radio button affects the enabled state of other controls, place the controls that it affects next to the radio button or below and indented.

* Don't initiate an action when the user clicks a radio button.

Projects/Usability/HIG/Radio Buttons

2008-08-01T16:37:01Z

Seele:

Radio buttons offer the user a choice of two or more mutually exclusive options. Try to limit the number of radio buttons and radio button groups in a dialog. Offering a high number of radio buttons consumes screen space and adds to visual clutter. At the same time, showing all available options at once is an advantage if users are likely not to know possible alternatives.

=== Guidelines ===
* Use radio buttons for 2 to 3 mutually exclusive options. If there are more than three options, use a combo box or list instead.
* Use radio buttons if the user should see the choices without further interaction.
* Provide a descriptive label above or left to a group of radio buttons in [[Projects/Usability/HIG/Capitalization|sentence style capitalization]].
* Use [[Projects/Usability/HIG/Capitalization|title style capitalization]] the radio button options.
* Align groups of radio buttons vertically rather than horizontally, as this makes them easier to scan visually. Use horizontal or rectangular alignments only if they greatly improve the layout of the window.
* Radio buttons are not dynamic; their content or labels should not change depending on the context.
* If toggling a radio button affects the enabled state of other controls, place the controls that it affects next to the radio button or below and indented.

* Don't initiate an action when the user clicks a radio button.

Projects/Usability/HIG/Menu Bar

2008-08-01T16:32:18Z

Seele:

The menubar appears at the top of a main window and provides access to all commands and most of the settings available in an application. It contains menu titles which describe the content of each menu. Each menu title is accessible by accelerator keys, which must be set by the developer.

=== Guidelines ===

* Group menus in consistency with the KDE standard menu bar.
* Provide a menubar in every application main window
* Do not display menubars in secondary or internal windows
* Menu item titles should be listed in a standard order
* Provide accelerator keys for every menu title in the menubar
* Do not disable menu titles even if no items under that menu are available
* Menu titles on a menubar appear as a single word with the first letter capitalized
* Do not use compound words (e.g. ToolOptions), and hyphens (e.g. Tool-Options) in label names; they make words harder to read and recognize
* Never make the menubar 'hideable', users may not easily be able to make the menubar viewable again

====Example: Standard Menu Bar====

This is the order of menu items in a standard menu bar. If an application does not have options under one of the standard menu items, do not include it in the menu. At the minimum, all windows should have a File (or File equivalent, such as in the case if Konqueror and Amarok) and Help menu.

| File | Edit | View | Insert | Format | ''Application Specific Menus'' | Go | Bookmarks | Tools | Settings | Window | Help |

Projects/Usability/HIG/Keyboard Shortcuts

2008-08-01T16:29:04Z

Seele:

Keyboard shortcuts help users perform common actions quickly through the keyboard instead of accessing the functionality in the UI with a mouse.

=== Global Keyboard Shortcuts ===
<table border="0" cellspacing="0" cellpadding="0" class="ta1"><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce1">Action </td><td style="text-align:left;width:1.1835in; " class="ce1">Key Binding </td><td style="text-align:left;width:1.1835in; " class="ce22" /><td style="text-align:left;width:4.1965in; " class="ce1">Comment </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td colspan="4" style="text-align:left;width:1.3807in; " class="ce13">File menu </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">New </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+N </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Create a new document </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Open </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+O </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Open a document </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Save </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+S </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Save the current document </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Save As </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Shift+S </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Save the current document </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Reload </td><td style="text-align:left;width:1.1835in; " class="ce18">F5 </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Reload the current document/view </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Print </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+P </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Print the current document </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Close </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+W </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Close the current document </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Quit </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Q </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Quit the application </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td colspan="4" style="text-align:left;width:1.3807in; " class="ce13">Edit menu </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Undo </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Z </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Undo the last operation </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Redo </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Y </td><td style="text-align:left;width:1.1835in; " class="ce20">Ctrl+Shift+Z </td><td style="text-align:left;width:4.1965in; " class="ce2">Redo the last undone operation </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Redo </td><td style="text-align:left;width:1.1835in; " class="ce18">Shift+Ctrl+Z </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Redo last undone operation (alternative) </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Cut </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+X </td><td style="text-align:left;width:1.1835in; " class="ce23">Shift+Delete </td><td style="text-align:left;width:4.1965in; " class="ce2">Cut the selected area and store it in the clipboard </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Copy </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+C </td><td style="text-align:left;width:1.1835in; " class="ce20">Ctrl+Insert </td><td style="text-align:left;width:4.1965in; " class="ce2">Copy the selected area into the clipboard </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Paste </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+V </td><td style="text-align:left;width:1.1835in; " class="ce20">Shift+Insert </td><td style="text-align:left;width:4.1965in; " class="ce2">Paste contents of clipboard at mouse/cursor position </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Select All </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+A </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Select everything in the contents area </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Deselect </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Shift+A </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Deselect everything in the contents area </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Find </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+F </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Find </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Find Next </td><td style="text-align:left;width:1.1835in; " class="ce18">F3 </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Find the next match </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Find Previous </td><td style="text-align:left;width:1.1835in; " class="ce18">Shift+F3 </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Find previous match </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Replace </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+R </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Find and replace matches </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce2">Delete word forward </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Delete </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Delete word from current cursor location to the end. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce2">Delete word backward </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Backspace </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Delete word from beginning to current cursor location. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Go to line... </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+G </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Move cursor to the corresponding line. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td colspan="4" style="text-align:left;width:1.3807in; " class="ce14">View Menu </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Full Screen Mode </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Shift+F </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Toggle full screen mode </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce15">Zoom menu </td><td style="text-align:left;width:1.1835in; " class="ce18" /><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Zoom In </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl++ </td><td style="text-align:left;width:1.1835in; " class="ce20">Ctrl+= </td><td style="text-align:left;width:4.1965in; " class="ce2">Zoom in to the document (magnify) </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Zoom Out </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+- </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Zoom out of the document </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Zoom to 100% </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+0 </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td colspan="4" style="text-align:left;width:1.3807in; " class="ce15">Bookmarks menu </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Add Bookmark </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+B </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Add a bookmark for the current location </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce15">Help menu </td><td style="text-align:left;width:1.1835in; " class="ce18" /><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Help </td><td style="text-align:left;width:1.1835in; " class="ce18">F1 </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Obtain help and documentation for the application </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce2">What's This </td><td style="text-align:left;width:1.1835in; " class="ce18">Shift+F1 </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Obtain a short help for the currently visible interface elements. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td colspan="4" style="text-align:left;width:1.3807in; " class="ce13">Navigation </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Focus to Menu </td><td style="text-align:left;width:1.1835in; " class="ce18">F10 </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Focus the menu bar. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce2">Show Context Menu </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+F10 </td><td style="text-align:left;width:1.1835in; " class="ce23">Menu </td><td style="text-align:left;width:4.1965in; " class="ce2">Show the context menu. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Toggle Menu bar </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+M </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Toggle the appearance of the menu bar. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce2">Page Down </td><td style="text-align:left;width:1.1835in; " class="ce18">Space </td><td style="text-align:left;width:1.1835in; " class="ce23">PageDown</td><td style="text-align:left;width:4.1965in; " class="ce2">Scroll down one Screen, displaying the next page if the application normally displays a page at a time. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce2">Page Up </td><td style="text-align:left;width:1.1835in; " class="ce18">Shift+space </td><td style="text-align:left;width:1.1835in; " class="ce20">PageUp </td><td style="text-align:left;width:4.1965in; " class="ce2">Scroll up one Screen, displaying the previous page if the application normally displays a page at a time. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Forward </td><td style="text-align:left;width:1.1835in; " class="ce18">Alt+Right </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Go to next page. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Back </td><td style="text-align:left;width:1.1835in; " class="ce18">Alt+Left </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Go to previous page. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Next Tab </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+PageUp </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Activate the next Tab. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce2">Previous Tab </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+PageDown</td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Activate the previous Tab. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro3"><td style="text-align:left;width:1.3807in; " class="ce2">Next Major Panel </td><td style="text-align:left;width:1.1835in; " class="ce18">F6 </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Switches focus to the next major panel, e.g. sidebar or content panel in a file manager. Useful to get focus from dockers back to the main window when. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce3">Resize Split Pane </td><td style="text-align:left;width:1.1835in; " class="ce20">F8 </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce3">Switches focus from one split pane to another to resize them via the arrow keys. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td colspan="4" style="text-align:left;width:1.3807in; " class="ce13">Text Navigation </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Beginning of line </td><td style="text-align:left;width:1.1835in; " class="ce18">Home </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Move cursor to the beginning of the line. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">End of line </td><td style="text-align:left;width:1.1835in; " class="ce18">End </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Move cursor to the beginning of the line. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">End </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+End </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Forward Word </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Right </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Move cursor to the beginning of the next word. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Backward Word </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Left </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Move cursor to the beginning of the previous word. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td colspan="4" style="text-align:left;width:1.3807in; " class="ce13">Text Completion </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce16">Substring completion </td><td style="text-align:left;width:1.1835in; " class="ce21">Ctrl+T </td><td style="text-align:left;width:1.1835in; " class="ce25" /><td style="text-align:left;width:4.1965in; " class="ce16">Toggle substring completion. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce16">Text Completion </td><td style="text-align:left;width:1.1835in; " class="ce21">Ctrl+E </td><td style="text-align:left;width:1.1835in; " class="ce25" /><td style="text-align:left;width:4.1965in; " class="ce16">Toggle text completion. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce16">Next item in list </td><td style="text-align:left;width:1.1835in; " class="ce21">Down </td><td style="text-align:left;width:1.1835in; " class="ce25" /><td style="text-align:left;width:4.1965in; " class="ce16">Select the next item in the completion list. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce16">Previous item in list </td><td style="text-align:left;width:1.1835in; " class="ce21">Up </td><td style="text-align:left;width:1.1835in; " class="ce25" /><td style="text-align:left;width:4.1965in; " class="ce16">Select the previous item in the completion list. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce16">Next completion match </td><td style="text-align:left;width:1.1835in; " class="ce21">Ctrl+Down </td><td style="text-align:left;width:1.1835in; " class="ce25" /><td style="text-align:left;width:4.1965in; " class="ce16">Select the next completion match. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce16">Previous completion match </td><td style="text-align:left;width:1.1835in; " class="ce21">Ctrl+Up </td><td style="text-align:left;width:1.1835in; " class="ce25" /><td style="text-align:left;width:4.1965in; " class="ce16">Select the previous completion match. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8"></td><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce17" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr></table>

F8 and F6 may still be used differently, if the window has no split panes (F8) or the definition of main panels is not required, e.g. if there are no dockers (F6). 

=== Standard System Shortcuts ===

<table border="0" cellspacing="0" cellpadding="0" class="ta1"><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce26">Key Binding </td><td style="text-align:left;width:3.7398in; " class="ce26">Comment </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td colspan="2" style="text-align:left;width:1.6673in; " class="ce27">Navigation </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Alt+Tab </td><td style="text-align:left;width:3.7398in; " class="ce7">Walk through windows </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Alt+Shift+Tab </td><td style="text-align:left;width:3.7398in; " class="ce7">Walk through windows (reverse) </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Ctrl+Tab </td><td style="text-align:left;width:3.7398in; " class="ce7">Focus to next widget (e.g. to get focus out of text fields). </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce29">Ctrl+Shift+Tab </td><td style="text-align:left;width:3.7398in; " class="ce30">Focus to previous widget (e.g. to get focus out of text fields). </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce29">Ctrl+F1 – F4 </td><td style="text-align:left;width:3.7398in; " class="ce30">Switch to desktop 1 to 4 </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce29">Ctrl+Alt+Tab</td><td style="text-align:left;width:3.7398in; " class="ce30">Switch focus between panel and desktop </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce29">Ctrl+Alt+Right </td><td style="text-align:left;width:3.7398in; " class="ce30">Switch to next desktop </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce29">Ctrl+Alt+Left </td><td style="text-align:left;width:3.7398in; " class="ce30">Switch to previous desktop </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce29">Ctrl+Alt+Shift+Tab</td><td style="text-align:left;width:3.7398in; " class="ce30">Switch focus between panel and desktop (reverse) </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td colspan="2" style="text-align:left;width:1.6673in; " class="ce27">Windows </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce29">Alt+F3 </td><td style="text-align:left;width:3.7398in; " class="ce30">Window operations menu </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce29">Alt+F4 </td><td style="text-align:left;width:3.7398in; " class="ce30">Close Window </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td colspan="2" style="text-align:left;width:1.6673in; " class="ce27">Miscellaneous </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce29">Alt+F12 </td><td style="text-align:left;width:3.7398in; " class="ce30">Mouse Emulation </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Ctrl+Alt+Escape </td><td style="text-align:left;width:3.7398in; " class="ce7">Kill window </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Alt+Print </td><td style="text-align:left;width:3.7398in; " class="ce7">Window screenshot </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Ctrl+Print </td><td style="text-align:left;width:3.7398in; " class="ce7">Desktop screenshot </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td colspan="2" style="text-align:left;width:1.6673in; " class="ce27">Panel </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Alt+F1 </td><td style="text-align:left;width:3.7398in; " class="ce7">Popup launch menu </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Ctrl+Alt+D </td><td style="text-align:left;width:3.7398in; " class="ce7">Toggle showing (empty) desktop </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td colspan="2" style="text-align:left;width:1.6673in; " class="ce27">Desktop </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Alt+F2 </td><td style="text-align:left;width:3.7398in; " class="ce7">Run command </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Ctrl+Escape </td><td style="text-align:left;width:3.7398in; " class="ce7">Show taskmanager </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Alt+F5 </td><td style="text-align:left;width:3.7398in; " class="ce7">Show windowlist </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Alt+Ctrl+L </td><td style="text-align:left;width:3.7398in; " class="ce7">Lock session </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td colspan="2" style="text-align:left;width:1.6673in; " class="ce27">Clipboard </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Ctrl+Alt+V </td><td style="text-align:left;width:3.7398in; " class="ce7">Show Klipper popup menu </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Ctrl+Alt+R </td><td style="text-align:left;width:3.7398in; " class="ce7">Manually invoke action on current clipboard </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Ctrl+Alt+X </td><td style="text-align:left;width:3.7398in; " class="ce7">Enable/disable clipboard actions </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td colspan="2" style="text-align:left;width:1.6673in; " class="ce27">Keyboard </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Ctrl+K </td><td style="text-align:left;width:3.7398in; " class="ce7">Switch to next keyboard layout </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.7398in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.7398in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr></table>

=== Implementation Notes ===

Keyboard accelerators - classes helping to establish consistent key bindings throughout the desktop.
* [http://api.kde.org/3.5-api/kdelibs-apidocs/kdecore/html/classKAccel.html KAccel] - collection of keyboard shortcuts.
* [http://api.kde.org/3.5-api/kdelibs-apidocs/kdecore/html/classKStdAccel.html KStdAccel] - easy access to the common keyboard shortcut keys.
* [http://api.kde.org/3.5-api/kdelibs-apidocs/kdecore/html/classKGlobalAccel.html KGlobalAccel] - collection of system-wide keyboard shortcuts.

Projects/Usability/HIG/Keyboard Shortcuts

2008-08-01T16:27:34Z

Seele:

Keyboard shortcuts help users perform common actions quickly through the keyboard instead of accessing the functionality in the UI with a mouse.

=== Global Keyboard Shortcuts ===
<table border="0" cellspacing="0" cellpadding="0" class="ta1"><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce1">Action </td><td style="text-align:left;width:1.1835in; " class="ce1">Key Binding </td><td style="text-align:left;width:1.1835in; " class="ce22" /><td style="text-align:left;width:4.1965in; " class="ce1">Comment </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td colspan="4" style="text-align:left;width:1.3807in; " class="ce13">File menu </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">New </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+N </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Create a new document </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Open </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+O </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Open a document </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Save </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+S </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Save the current document </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Save As </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Shift+S </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Save the current document </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Reload </td><td style="text-align:left;width:1.1835in; " class="ce18">F5 </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Reload the current document/view </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Print </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+P </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Print the current document </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Close </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+W </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Close the current document </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Quit </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Q </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Quit the application </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td colspan="4" style="text-align:left;width:1.3807in; " class="ce13">Edit menu </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Undo </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Z </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Undo the last operation </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Redo </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Y </td><td style="text-align:left;width:1.1835in; " class="ce20">Ctrl+Shift+Z </td><td style="text-align:left;width:4.1965in; " class="ce2">Redo the last undone operation </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Redo </td><td style="text-align:left;width:1.1835in; " class="ce18">Shift+Ctrl+Z </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Redo last undone operation (alternative) </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Cut </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+X </td><td style="text-align:left;width:1.1835in; " class="ce23">Shift+Delete </td><td style="text-align:left;width:4.1965in; " class="ce2">Cut the selected area and store it in the clipboard </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Copy </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+C </td><td style="text-align:left;width:1.1835in; " class="ce20">Ctrl+Insert </td><td style="text-align:left;width:4.1965in; " class="ce2">Copy the selected area into the clipboard </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Paste </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+V </td><td style="text-align:left;width:1.1835in; " class="ce20">Shift+Insert </td><td style="text-align:left;width:4.1965in; " class="ce2">Paste contents of clipboard at mouse/cursor position </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Select All </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+A </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Select everything in the contents area </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Deselect </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Shift+A </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Deselect everything in the contents area </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Find </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+F </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Find </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Find Next </td><td style="text-align:left;width:1.1835in; " class="ce18">F3 </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Find the next match </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Find Previous </td><td style="text-align:left;width:1.1835in; " class="ce18">Shift+F3 </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Find previous match </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Replace </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+R </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Find and replace matches </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce2">Delete word forward </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Delete </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Delete word from current cursor location to the end. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce2">Delete word backward </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Backspace </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Delete word from beginning to current cursor location. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Go to line... </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+G </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Move cursor to the corresponding line. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td colspan="4" style="text-align:left;width:1.3807in; " class="ce14">View Menu </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Full Screen Mode </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Shift+F </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Toggle full screen mode </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce15">Zoom menu </td><td style="text-align:left;width:1.1835in; " class="ce18" /><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Zoom In </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl++ </td><td style="text-align:left;width:1.1835in; " class="ce20">Ctrl+= </td><td style="text-align:left;width:4.1965in; " class="ce2">Zoom in to the document (magnify) </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Zoom Out </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+- </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Zoom out of the document </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Zoom to 100% </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+0 </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td colspan="4" style="text-align:left;width:1.3807in; " class="ce15">Bookmarks menu </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Add Bookmark </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+B </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Add a bookmark for the current location </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce15">Help menu </td><td style="text-align:left;width:1.1835in; " class="ce18" /><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Help </td><td style="text-align:left;width:1.1835in; " class="ce18">F1 </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Obtain help and documentation for the application </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce2">What's This </td><td style="text-align:left;width:1.1835in; " class="ce18">Shift+F1 </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Obtain a short help for the currently visible interface elements. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td colspan="4" style="text-align:left;width:1.3807in; " class="ce13">Navigation </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Focus to Menu </td><td style="text-align:left;width:1.1835in; " class="ce18">F10 </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Focus the menu bar. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce2">Show Context Menu </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+F10 </td><td style="text-align:left;width:1.1835in; " class="ce23">Menu </td><td style="text-align:left;width:4.1965in; " class="ce2">Show the context menu. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Toggle Menu bar </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+M </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Toggle the appearance of the menu bar. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce2">Page Down </td><td style="text-align:left;width:1.1835in; " class="ce18">Space </td><td style="text-align:left;width:1.1835in; " class="ce23">PageDown</td><td style="text-align:left;width:4.1965in; " class="ce2">Scroll down one Screen, displaying the next page if the application normally displays a page at a time. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce2">Page Up </td><td style="text-align:left;width:1.1835in; " class="ce18">Shift+space </td><td style="text-align:left;width:1.1835in; " class="ce20">PageUp </td><td style="text-align:left;width:4.1965in; " class="ce2">Scroll up one Screen, displaying the previous page if the application normally displays a page at a time. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Forward </td><td style="text-align:left;width:1.1835in; " class="ce18">Alt+Right </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Go to next page. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Back </td><td style="text-align:left;width:1.1835in; " class="ce18">Alt+Left </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Go to previous page. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Next Tab </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+PageUp </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Activate the next Tab. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce2">Previous Tab </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+PageDown</td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Activate the previous Tab. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro3"><td style="text-align:left;width:1.3807in; " class="ce2">Next Major Panel </td><td style="text-align:left;width:1.1835in; " class="ce18">F6 </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Switches focus to the next major panel, e.g. sidebar or content panel in a file manager. Useful to get focus from dockers back to the main window when. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce3">Resize Split Pane </td><td style="text-align:left;width:1.1835in; " class="ce20">F8 </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce3">Switches focus from one split pane to another to resize them via the arrow keys. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td colspan="4" style="text-align:left;width:1.3807in; " class="ce13">Text Navigation </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Beginning of line </td><td style="text-align:left;width:1.1835in; " class="ce18">Home </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Move cursor to the beginning of the line. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">End of line </td><td style="text-align:left;width:1.1835in; " class="ce18">End </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Move cursor to the beginning of the line. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">End </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+End </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Forward Word </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Right </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Move cursor to the beginning of the next word. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce2">Backward Word </td><td style="text-align:left;width:1.1835in; " class="ce18">Ctrl+Left </td><td style="text-align:left;width:1.1835in; " class="ce20" /><td style="text-align:left;width:4.1965in; " class="ce2">Move cursor to the beginning of the previous word. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td colspan="4" style="text-align:left;width:1.3807in; " class="ce13">Text Completion </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce16">Substring completion </td><td style="text-align:left;width:1.1835in; " class="ce21">Ctrl+T </td><td style="text-align:left;width:1.1835in; " class="ce25" /><td style="text-align:left;width:4.1965in; " class="ce16">Toggle substring completion. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce16">Text Completion </td><td style="text-align:left;width:1.1835in; " class="ce21">Ctrl+E </td><td style="text-align:left;width:1.1835in; " class="ce25" /><td style="text-align:left;width:4.1965in; " class="ce16">Toggle text completion. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce16">Next item in list </td><td style="text-align:left;width:1.1835in; " class="ce21">Down </td><td style="text-align:left;width:1.1835in; " class="ce25" /><td style="text-align:left;width:4.1965in; " class="ce16">Select the next item in the completion list. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce16">Previous item in list </td><td style="text-align:left;width:1.1835in; " class="ce21">Up </td><td style="text-align:left;width:1.1835in; " class="ce25" /><td style="text-align:left;width:4.1965in; " class="ce16">Select the previous item in the completion list. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce16">Next completion match </td><td style="text-align:left;width:1.1835in; " class="ce21">Ctrl+Down </td><td style="text-align:left;width:1.1835in; " class="ce25" /><td style="text-align:left;width:4.1965in; " class="ce16">Select the next completion match. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro2"><td style="text-align:left;width:1.3807in; " class="ce16">Previous completion match </td><td style="text-align:left;width:1.1835in; " class="ce21">Ctrl+Up </td><td style="text-align:left;width:1.1835in; " class="ce25" /><td style="text-align:left;width:4.1965in; " class="ce16">Select the previous completion match. </td><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8"></td><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce17" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.3807in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /><td style="text-align:left;width:4.1965in; " class="ce8" /><td style="text-align:left;width:1.1835in; " class="ce8" /></tr></table>

F8 and F6 may still be used differently, if the window has no split panes (F8) or the definition of main panels is not required, e.g. if there are no dockers (F6). 

== Standard System Shortcuts ==

<table border="0" cellspacing="0" cellpadding="0" class="ta1"><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce26">Key Binding </td><td style="text-align:left;width:3.7398in; " class="ce26">Comment </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td colspan="2" style="text-align:left;width:1.6673in; " class="ce27">Navigation </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Alt+Tab </td><td style="text-align:left;width:3.7398in; " class="ce7">Walk through windows </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Alt+Shift+Tab </td><td style="text-align:left;width:3.7398in; " class="ce7">Walk through windows (reverse) </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Ctrl+Tab </td><td style="text-align:left;width:3.7398in; " class="ce7">Focus to next widget (e.g. to get focus out of text fields). </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce29">Ctrl+Shift+Tab </td><td style="text-align:left;width:3.7398in; " class="ce30">Focus to previous widget (e.g. to get focus out of text fields). </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce29">Ctrl+F1 – F4 </td><td style="text-align:left;width:3.7398in; " class="ce30">Switch to desktop 1 to 4 </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce29">Ctrl+Alt+Tab</td><td style="text-align:left;width:3.7398in; " class="ce30">Switch focus between panel and desktop </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce29">Ctrl+Alt+Right </td><td style="text-align:left;width:3.7398in; " class="ce30">Switch to next desktop </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce29">Ctrl+Alt+Left </td><td style="text-align:left;width:3.7398in; " class="ce30">Switch to previous desktop </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce29">Ctrl+Alt+Shift+Tab</td><td style="text-align:left;width:3.7398in; " class="ce30">Switch focus between panel and desktop (reverse) </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td colspan="2" style="text-align:left;width:1.6673in; " class="ce27">Windows </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce29">Alt+F3 </td><td style="text-align:left;width:3.7398in; " class="ce30">Window operations menu </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce29">Alt+F4 </td><td style="text-align:left;width:3.7398in; " class="ce30">Close Window </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td colspan="2" style="text-align:left;width:1.6673in; " class="ce27">Miscellaneous </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce29">Alt+F12 </td><td style="text-align:left;width:3.7398in; " class="ce30">Mouse Emulation </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Ctrl+Alt+Escape </td><td style="text-align:left;width:3.7398in; " class="ce7">Kill window </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Alt+Print </td><td style="text-align:left;width:3.7398in; " class="ce7">Window screenshot </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Ctrl+Print </td><td style="text-align:left;width:3.7398in; " class="ce7">Desktop screenshot </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td colspan="2" style="text-align:left;width:1.6673in; " class="ce27">Panel </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Alt+F1 </td><td style="text-align:left;width:3.7398in; " class="ce7">Popup launch menu </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Ctrl+Alt+D </td><td style="text-align:left;width:3.7398in; " class="ce7">Toggle showing (empty) desktop </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td colspan="2" style="text-align:left;width:1.6673in; " class="ce27">Desktop </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Alt+F2 </td><td style="text-align:left;width:3.7398in; " class="ce7">Run command </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Ctrl+Escape </td><td style="text-align:left;width:3.7398in; " class="ce7">Show taskmanager </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Alt+F5 </td><td style="text-align:left;width:3.7398in; " class="ce7">Show windowlist </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Alt+Ctrl+L </td><td style="text-align:left;width:3.7398in; " class="ce7">Lock session </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td colspan="2" style="text-align:left;width:1.6673in; " class="ce27">Clipboard </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Ctrl+Alt+V </td><td style="text-align:left;width:3.7398in; " class="ce7">Show Klipper popup menu </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Ctrl+Alt+R </td><td style="text-align:left;width:3.7398in; " class="ce7">Manually invoke action on current clipboard </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Ctrl+Alt+X </td><td style="text-align:left;width:3.7398in; " class="ce7">Enable/disable clipboard actions </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td colspan="2" style="text-align:left;width:1.6673in; " class="ce27">Keyboard </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce28">Ctrl+K </td><td style="text-align:left;width:3.7398in; " class="ce7">Switch to next keyboard layout </td><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.7398in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr><tr class="ro1"><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.7398in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /><td style="text-align:left;width:3.6047in; " class="ce8" /><td style="text-align:left;width:1.6673in; " class="ce8" /></tr></table>

=== Implementation Notes ===

Keyboard accelerators - classes helping to establish consistent key bindings throughout the desktop.
* [http://api.kde.org/3.5-api/kdelibs-apidocs/kdecore/html/classKAccel.html KAccel] - collection of keyboard shortcuts.
* [http://api.kde.org/3.5-api/kdelibs-apidocs/kdecore/html/classKStdAccel.html KStdAccel] - easy access to the common keyboard shortcut keys.
* [http://api.kde.org/3.5-api/kdelibs-apidocs/kdecore/html/classKGlobalAccel.html KGlobalAccel] - collection of system-wide keyboard shortcuts.

Projects/Usability/HIG/Keyboard Accelerators

2008-08-01T16:27:26Z

Seele:

Keyboard accelerators are key bindings to access menu items in a consistent way.

=== Global Keyboard Accelerators ===
{|
|'''Menu Title '''
|'''Menu Item '''
|
|-
|File
|New
|
|-
|
|Open...
|
|-
|
|Open Recent
|
|-
|
|Save
|
|-
|
|Save As...
|
|-
|
|Save a Copy...
|
|-
|
|Save as Template
|
|-
|
|Save All
|
|-
|
|Reload
|
|-
|
|Print
|
|-
|
|Print Preview
|
|-
|
|Import
|
|-
|
|Export
|
|-
|
|Close File
|
|-
|
|Close All Files
|
|-
|
|Quit
|
|-
|Edit
|Undo
|
|-
|
|Redo
|
|-
|
|Cut 
|
|-
|
|Copy
|
|-
|
|Paste
|
|-
|
|Delete
|
|-
|
|Select All
|
|-
|
|Deselect
|
|-
|
|Find...
|
|-
|
|Find Next
|
|-
|
|Find Previous
|
|-
|
|Replace...
|
|-
|
|Go to Line...
|
|-
|View
|New View
|
|-
|
|Close All Views
|
|-
|
|Split View
|
|-
|
|Remove View
|
|-
|
|Splitter Orientation
|Horizontal
|-
|
|
|Vertical
|-
|
|View Mode
|
|-
|
|Full Screen Mode
|
|-
|
|Zoom
|Zoom In
|-
|
|
|Zoom Out
|-
|
|
|Zoom to Page Width
|-
|
|
|Zoom Whole Page
|-
|
|
|Zoom Factor
|-
|Insert
|
|
|-
|Format
|
|
|-
|Go
(Browser)
|Up
|
|-
|
|Back
|
|-
|
|Forward
|
|-
|
|Home
|
|-
|Go
(Document-based)
|Previous Page
|
|-
|
|Next Page
|
|-
|
|First Page
|
|-
|
|Last Page
|
|-
|
|Read Up Document
|
|-
|
|Read Down Document
|
|-
|
|Back
|
|-
|
|Forward
|
|-
|
|Go to Page...
|
|-
|
|Bookmarks
|Add Bookmark
|
|-
|
|
|Bookmark Tabs as Folder...
|
|-
|
|
|Edit Bookmarks
|
|-
|
|
|New Bookmarks Folder...
|
|-
|
|Tools
|
|
|-
|
|Settings
|Toolbars
|
|-
|
|Configure Shortcuts...
|
|-
|
|Configure Toolbars
|
|-
|
|Configure (Application Name)
|
|-
|Help
|(Application Name) Handbook
|
|-
|
|What's This?
|
|-
|
|Report Bug...
|
|-
|
|About (Application Name)
|
|-
|
|About KDE
|
|-
|
|
|}

=== Implementation Notes ===

Keyboard accelerators - classes helping to establish consistent key bindings throughout the desktop.
* [http://api.kde.org/3.5-api/kdelibs-apidocs/kdecore/html/classKAccel.html KAccel] - collection of keyboard shortcuts.
* [http://api.kde.org/3.5-api/kdelibs-apidocs/kdecore/html/classKStdAccel.html KStdAccel] - easy access to the common keyboard shortcut keys.
* [http://api.kde.org/3.5-api/kdelibs-apidocs/kdecore/html/classKGlobalAccel.html KGlobalAccel] - collection of system-wide keyboard shortcuts.

Projects/Usability/HIG Questions

2008-08-01T16:20:47Z

Seele:

= KDE4 HIG Questions and Requests =

Developer, please use this page to add questions and requests about the KDE4 Human Interface Guidelines (HIG)

* Please list questions about the KDE4 HIG here
* Also include your name/IRC nick/email if you want to be contacted for follow up questions
* Be as specific as possible and include a screenshot if applicable. [http://lists.kde.org/?l=kde-usability&m=120955187622753&w=2 This email on the kde-usability mailing list] is a '''good''' example of a HIG question/request.

* Which buttons have icons and when should we use/not use icons on buttons?
* The growth policy: are widgets supposed to grow and take all the available (horizontal) space, even in case of widgets that don't have a size policy for expanding?
* Description of alignment rule. See: http://lists.kde.org/?l=kde-core-devel&m=121639074230037&w=2 and
* Should the horizontal alignment of the layout be left- or center-? (eg: [http://img186.imageshack.us/img186/33/formlayoutalignxv0.png sample screenshot])
* Some musing about [[Projects/Usability/HIG_Questions/Standard_Shortcuts | Standard Shortcuts]]
* Remove or Delete for a button label?
* Order of Add Copy Remove/Delete in forms
* Options or Settings for a label?
* Reorder buttons (Move up down top bottom), icons, icons with text, or buttons with text labels?
* Listviews: http://ktown.kde.org/~fredrik/listviews/
* Visual style of notes/instructions in System Setting modules ([http://techbase.kde.org/Image:Systemsettings-information1.png Screenshot])
* when should tooltips be used? when is it too annoying and should be replaced by a "whats this?" function?
* Will the HIG specify a standard format and functions for the status bar?--[[User:JRT|JRT]] 03:02, 17 June 2008 (CEST)
* Will the HIG specify a minimum set of Zoom & View functions and specify which of these should be on the status bar and which should be in the Menu &/| Toolbars?--[[User:JRT|JRT]] 03:02, 17 June 2008 (CEST)
* <s>I suggest adding a guideline to the checkboxes section saying that checkbox labels should always be "positively" formulated such as "enable ...". Never "disable ..." or even "Hide ..." (use "Show ..." instead. This contradicts what is currently in [[Projects/Usability/HIG/Check_Box | Check Box]]). If the user has to activate a checkbox to disactivate something this is like a double negation and induces unnecessary cognitive load. Also see: http://lists.kde.org/?l=kde-usability&m=121651903819214&w=2</s>
* [[Projects/Usability/HIG/Keyboard_Accelerators|Keyboard Accelerators page needs reformatted and updated]]

Projects/Usability/HIG/Ellipsis

2008-08-01T16:19:49Z

Seele:

An ellipsis is used after menu items and button labels which the user is either required or is able to provide input. An ellipsis is not used when the label implies and action and user input is not required to complete the activity. Configuration dialogs are a good example of this, the label already implies action and making changes is not necessary to complete an activity such as checking a setting.

=== Guidelines ===

* Use an ellipsis after menu items and button labels which require user’s input before completing their action.
* Do not use an ellipsis if user input is not required
* Do not use an ellipsis for selections which result in actions (such as Save or Print) or do not require user input (such as configuration dialogs).
* Do not use an ellipsis for an action which may require confirmation before it is completed (such as a Deletion confirmation).

'''Do''' use an ellipsis for the following menu items and buttons:
* Find...
* Find and Replace...
* Open...
* Print...
* Replace...
* Save As...
* Send To...

'''Do not''' use an ellipsis for the following menu items and buttons:
* About
* Advanced Options
* Check Spelling
* Close or Quit
* Configure [something]
* Delete or Remove
* Help
* Preferences
* Print Preview
* Properties
* Toolboxes

Projects/Usability/HIG/Check Box

2008-08-01T16:19:03Z

Seele:

Check boxes are a widget to enable one more options in a group.

=== Guidelines ===
* Use checkboxes for non-exclusive options. Mutually exclusive options should use a set of [[Projects/Usability/HIG/Radio_Buttons|radio buttons]].
* For more than 10 options, use a list.
* Checking a checkbox should always "enable" an option or change the state of an option to "on". Checking a negative or disabling option is a double negative and causes confusion and errors.
* Checkbox labels are in [[Projects/Usability/HIG/Capitalization|sentence style capitalization]]

Projects/Usability/HIG/Combo Box

2008-08-01T16:15:32Z

Seele:

Combo boxes (also known as a dropdown box) offer the user a choice of two or more mutually exclusive options. Their disadvantage compared to related controls like radio buttons or lists is that the options are not visible without further interaction.

=== Guidelines ===

* For 3 or fewer options, use a set of [[Projects/Usability/HIG/Radio_Buttons|radio buttons]].
* For 4 to 10 options, use a combo box instead of radio buttons.
* For more than 10 options, use a list.
* Label the combo box with a descriptive label to the left of the combo box.
* Use sentence style capitalization for the label and the options.
* If activating a choice affects the appearance or the enabled state of other controls, place them next to the combo box or below the combo box with a space indentation.

Controls that show the options without further user interaction are preferable, except for the following cases:

* the list of options may change over time,
* the contents are obvious from the label and the one selected item, for example ''Month'' and ''January''
* the combo box is part of a related sequence of controls. For example, to set a reminder to ring 5 hours or minutes before or after an event.

=== Accessibility Guidelines ===
* Don't initiate an action when the user selects an item from a drop-down list.
* Don't forget to create a buddy relation so access keys are assigned.
* Make sure the items are easily accessible via keyboard by moving distinctive letters to the beginning of each option. For example, in a list of countries on continents, write ''Germany (Europe)'' instead of ''Europe/Germany''.

Projects/Usability/HIG/Capitalization

2008-08-01T16:14:47Z

Seele:

There are two types of capitalization, title capitalization and sentence style capitalization.

This Is an Example of Title Capitalization

This is an example of sentence capitalization

==Title Capitalization==

Title capitalization is when every word in a sentence, statement, phrase, or label are capitalized except for certain words. Capitalize all words except for:
* Prepositions having less than five letters, (e.g. "for", "in", "with" or "to", but "From" or "Under")
* Conjunctions ("and", "or" and "but")
* Articles ("the", "a" and "an")

Use '''title capitalization''' in the following cases:
* Window and dialog box titles
* Group box / group line labels
* button labels
* Tab labels
* Listview column headers
* Menu titles / menu items
* Derivatives of KCommand
* Combobox items
* Listbox items
* Tree list items
* Other heading/title text

==Sentence Style Capitalization==

Sentence style capitalization is when the first letter of the sentence, statement, phrase, or label is capitalized and all other words are lower case. The only exception to this is proper nouns which are always capitalized.

Use '''sentence style capitalization''' in the following cases:
* Edit box labels
* List box labels
* Combo box labels
* Spin box labels
* Check box labels
* Option button labels
* Spin box labels
* Slider labels
* Pop-up hint text
* Other non heading/title text

Projects/Usability/HIG/Combo Box

2008-08-01T16:12:27Z

Seele:

Combo boxes (also known as a dropdown box) offer the user a choice of two or more mutually exclusive options. Their disadvantage compared to related controls like radio buttons or lists is that the options are not visible without further interaction.

=== General Guidelines ===

* For 3 or fewer options, use a set of [[Projects/Usability/HIG/Radio_Buttons|radio buttons]].
* For 4 to 10 options, use a combo box instead of radio buttons.
* For more than 10 options, use a list.
* Label the combo box with a descriptive label to the left of the combo box.
* Use sentence style capitalization for the label and the options.
* If activating a choice affects the appearance or the enabled state of other controls, place them next to the combo box or below the combo box with a space indentation.

Controls that show the options without further user interaction are preferable, except for the following cases:

* the list of options may change over time,
* the contents are obvious from the label and the one selected item, for example ''Month'' and ''January''
* the combo box is part of a related sequence of controls. For example, to set a reminder to ring 5 hours or minutes before or after an event.

=== Accessibility Guidelines ===
* Don't initiate an action when the user selects an item from a drop-down list.
* Don't forget to create a buddy relation so access keys are assigned.
* Make sure the items are easily accessible via keyboard by moving distinctive letters to the beginning of each option. For example, in a list of countries on continents, write ''Germany (Europe)'' instead of ''Europe/Germany''.

Projects/Usability/HIG/Combo Box

2008-08-01T16:11:49Z

Seele: updated combo box

Combo boxes (also known as a dropdown box) offer the user a choice of two or more mutually exclusive options. Their disadvantage compared to related controls like radio buttons or lists is that the options are not visible without further interaction.

* For 3 or fewer options, use a set of [[Projects/Usability/HIG/Radio_Buttons|radio buttons]].
* For 4 to 10 options, use a combo box instead of radio buttons.
* For more than 10 options, use a list.
* Label the combo box with a descriptive label to the left of the combo box.
* Use sentence style capitalization for the label and the options.
* If activating a choice affects the appearance or the enabled state of other controls, place them next to the combo box or below the combo box with a space indentation.

In general, controls that show the options without further user interaction are preferable, except for the following cases:
* the list of options may change over time,
* the contents are obvious from the label and the one selected item, for example ''Month'' and ''January''
* the combo box is part of a related sequence of controls. For example, to set a reminder to ring 5 hours or minutes before or after an event.

=== Accessibility Guidelines ===
* Don't initiate an action when the user selects an item from a drop-down list.
* Don't forget to create a buddy relation so access keys are assigned.
* Make sure the items are easily accessible via keyboard by moving distinctive letters to the beginning of each option. For example, in a list of countries on continents, write ''Germany (Europe)'' instead of ''Europe/Germany''.

Projects/Usability/HIG/Check Box

2008-08-01T15:50:05Z

Seele:

Check boxes are a widget to enable one or a group or options.

* Use checkboxes for non-exclusive options. Exclusive options should use a set of radiobutton options.
* Checking a checkbox should always "enable" an option or change the state of an option to "on". Checking a negative or disabling option is a double negative and causes confusion and errors.

Projects/Usability/HIG Questions

2008-08-01T15:49:04Z

Seele:

= KDE4 HIG Questions and Requests =

Developer, please use this page to add questions and requests about the KDE4 Human Interface Guidelines (HIG)

* Please list questions about the KDE4 HIG here
* Also include your name/IRC nick/email if you want to be contacted for follow up questions
* Be as specific as possible and include a screenshot if applicable. [http://lists.kde.org/?l=kde-usability&m=120955187622753&w=2 This email on the kde-usability mailing list] is a '''good''' example of a HIG question/request.

* Which buttons have icons and when should we use/not use icons on buttons?
* The growth policy: are widgets supposed to grow and take all the available (horizontal) space, even in case of widgets that don't have a size policy for expanding?
* Description of alignment rule. See: http://lists.kde.org/?l=kde-core-devel&m=121639074230037&w=2 and
* Should the horizontal alignment of the layout be left- or center-? (eg: [http://img186.imageshack.us/img186/33/formlayoutalignxv0.png sample screenshot])
* Some musing about [[Projects/Usability/HIG_Questions/Standard_Shortcuts | Standard Shortcuts]]
* Remove or Delete for a button label?
* Order of Add Copy Remove/Delete in forms
* Options or Settings for a label?
* Reorder buttons (Move up down top bottom), icons, icons with text, or buttons with text labels?
* Listviews: http://ktown.kde.org/~fredrik/listviews/
* Visual style of notes/instructions in System Setting modules ([http://techbase.kde.org/Image:Systemsettings-information1.png Screenshot])
* when should tooltips be used? when is it too annoying and should be replaced by a "whats this?" function?
* Will the HIG specify a standard format and functions for the status bar?--[[User:JRT|JRT]] 03:02, 17 June 2008 (CEST)
* Will the HIG specify a minimum set of Zoom & View functions and specify which of these should be on the status bar and which should be in the Menu &/| Toolbars?--[[User:JRT|JRT]] 03:02, 17 June 2008 (CEST)
* <s>I suggest adding a guideline to the checkboxes section saying that checkbox labels should always be "positively" formulated such as "enable ...". Never "disable ..." or even "Hide ..." (use "Show ..." instead. This contradicts what is currently in [[Projects/Usability/HIG/Check_Box | Check Box]]). If the user has to activate a checkbox to disactivate something this is like a double negation and induces unnecessary cognitive load. Also see: http://lists.kde.org/?l=kde-usability&m=121651903819214&w=2</s>

Projects/Usability/HIG/Check Box

2008-08-01T15:47:40Z

Seele: reword guidelines

Projects/Usability/HIG/Messages

2008-08-01T15:41:11Z

Seele:

Warning and error messages appear when a problem or error has occurred.

Warning and error messages should be:
* ''Understandable''. Phrase your messages clearly, in non-technical terms and avoid obscure error codes.
* ''Specific instead of general''. If the message is reporting a problem concerning a specific object or application, use the object or application name when referring to it.
* ''Informative and constructive''. Tell the user the reason for a problem and help on how to solve the problem.
* ''Polite, non-terrifying and non-blaming''. Avoid wording that terrifies the user ("fatal", "illegal"), blames him for his behavior, and be polite.

=== Confirmation Button Labels ===
* To close a warning or error message that does not require further user interaction, provide a Close button. '''Do not use an OK button.''' Users may get confused if they are asked to confirm an error.
* Use buttons which match the type of statement or question made in the warning or error message. For example, do no ask a Yes/No question but then provide OK/Cancel buttons.
* When the user must choose between two actions to continue, use descriptive button labels instead of standard Yes/No or OK/Cancel buttons. For example, if the user must choose to continue or stop an action, provide the buttons "Continue" and "Cancel".

=== Error Details ===
* Provide only a short error message and complement it by a Details button that provides more a detailed explanation in the same error dialog.
* If it makes sense for this kind of error, link from the error dialog to the corresponding page in the help system. Provide a Help button then.

=== Dialog vs. Info Panel ===
* Use dialogs for critical error messages, and when you need to make sure that the user sees the message.
* Use info panels for non-critical messages which do not require any further user interaction (typically dialogs with a single "OK" or "Close" button).

Projects/Usability/HIG/Messages

2008-08-01T15:39:08Z

Seele:

Warning and error messages appear when a problem or error has occurred.

Warning and error messages should be:
* ''Understandable''. Phrase your messages clearly, in non-technical terms and avoid obscure error codes.
* ''Specific instead of general''. If the message is reporting a problem concerning a specific object or application, use the object or application name when referring to it.
* ''Informative and constructive''. Tell the user the reason for a problem and help on how to solve the problem.
* ''Polite, non-terrifying and non-blaming''. Avoid wording that terrifies the user ("fatal", "illegal"), blames him for his behavior, and be polite.

'''Confirmation Button Labels'''
* To close a warning or error message that does not require further user interaction, provide a Close button. '''Do not use an OK button.''' Users may get confused if they are asked to confirm an error.
* Use buttons which match the type of statement or question made in the warning or error message. For example, do no ask a Yes/No question but then provide OK/Cancel buttons.
* When the user must choose between two actions to continue, use descriptive button labels instead of standard Yes/No or OK/Cancel buttons. For example, if the user must choose to continue or stop an action, provide the buttons "Continue" and "Cancel".

'''Error Details'''
* Provide only a short error message and complement it by a Details button that provides more a detailed explanation in the same error dialog.
* If it makes sense for this kind of error, link from the error dialog to the corresponding page in the help system. Provide a Help button then.

'''Dialog vs. Info Panel'''
* Use dialogs for critical error messages, and when you need to make sure that the user sees the message.
* Use info panels for non-critical messages which do not require any further user interaction (typically dialogs with a single "OK" or "Close" button).

Projects/Usability

2008-08-01T00:17:06Z

Seele: update user research profile projects

The KDE Usability Project aims to improve KDE usability and user experience through:

* Educating developers about usability practices
* Conducting usability activities to help gather feedback from users
* Working with projects and help design usable user interfaces

Learn more at the [http://usability.kde.org KDE Usability Project] website.

= [[Projects/Usability/HIG|KDE4 Human Interface Guidelines]] =

If you have questions about guidelines or want to request a missing guideline or change to a guideline, please put it on the [http://techbase.kde.org/Projects/Usability/HIG_Questions HIG Questions] page. We will refer to this page during the [http://season.openusability.org Season of Usability] KDE4 HIG project.

= User Research Profiles =

The purpose of this template is to provide a place to document an application's user research information for reference during development. Top level items are information everyone in the project should be aware of. Some of the details in the lower sections may take some work and discussion within the project to complete.

[http://techbase.kde.org/index.php?title=Projects/Usability/Project_User_Research_Template Project User Research Template]

== Projects ==

These projects have been called to work on their user research profiles:

* [[Projects/Gwenview/User_Research_Profile|Gwenview]]
* [[Projects/Kopete/User_Research_Profile|Kopete]]
* [[Projects/Okular/User_Research_Profile|Okular]]
* [[Projects/Plasma/PURP|Plasma]]

[[Category:Usability]]

Projects/Usability/HIG/Menu Bar

2008-07-21T21:02:23Z

Seele:

The menubar appears at the top of a main window and provides access to all commands and most of the settings available in an application. It contains menu titles which describe the content of each menu. Each menu title is accessible by accelerator keys, which must be set by the developer.

* Group menus in consistency with the KDE standard menu bar.
* Provide a menubar in every application main window
* Do not display menubars in secondary or internal windows
* Menu item titles should be listed in a standard order
* Provide accelerator keys for every menu title in the menubar
* Do not disable menu titles even if no items under that menu are available
* Menu titles on a menubar appear as a single word with the first letter capitalized
* Do not use compound words (e.g. ToolOptions), and hyphens (e.g. Tool-Options) in label names; they make words harder to read and recognize
* Never make the menubar 'hideable', users may not easily be able to make the menubar viewable again

'''Example: Standard Menu Bar'''

This is the order of menu items in a standard menu bar. If an application does not have options under one of the standard menu items, do not include it in the menu. At the minimum, all windows should have a File (or File equivalent, such as in the case if Konqueror and Amarok) and Help menu.

| File | Edit | View | Insert | Format | ''Application Specific Menus'' | Go | Bookmarks | Tools | Settings | Window | Help |

Projects/Usability/HIG/Menu Bar

2008-07-21T21:01:56Z

Seele:

The menubar appears at the top of a main window and provides access to all commands and most of the settings available in an application. It contains menu titles which describe the content of each menu. Each menu title is accessible by accelerator keys, which must be set by the developer.

* Group menus in consistency with the KDE standard menu bar.
* Provide a menubar in every application main window
* Do not display menubars in secondary or internal windows
* Menu item titles should be listed in a standard order
* Provide accelerator keys for every menu title in the menubar
* Do not disable menu titles even if no items under that menu are available
* Menu titles on a menubar appear as a single word with the first letter capitalized
* Do not use compound words (e.g. ToolOptions), and hyphens (e.g. Tool-Options) in label names; they make words harder to read and recognize
* Never make the menubar 'hideable', users may not easily be able to make the menubar viewable again

'''Example: Standard Menu Bar'''

This is the order of menu items in a standard menu bar. If an application does not have options under one of the standard menu items, do not include it in the menu. At the minimum, all windows should have a File (or File equivalent, such as in the case if Konqueror and Amarok) and Help menu.

| File | Edit | View | Insert | Format | ''Application Specific Menus'' | Go | Bookmarks | Tools | Settings | Window | Help |<nowiki>Insert non-formatted text here</nowiki>

Projects/Usability/HIG/Ellipsis

2008-07-20T22:20:09Z

Seele: add find and replace

An ellipsis is used after menu items and button labels which the user is either required or is able to provide input. An ellipsis is not used when the label implies and action and user input is not required to complete the activity. Configuration dialogs are a good example of this, the label already implies action and making changes is not necessary to complete an activity such as checking a setting.

* Use an ellipsis after menu items and button labels which require user’s input before completing their action.
* Do not use an ellipsis if user input is not required
* Do not use an ellipsis for selections which result in actions (such as Save or Print) or do not require user input (such as configuration dialogs).
* Do not use an ellipsis for an action which may require confirmation before it is completed (such as a Deletion confirmation).

'''Do''' use an ellipsis for the following menu items and buttons:
* Find...
* Find and Replace...
* Open...
* Print...
* Replace...
* Save As...
* Send To...

'''Do not''' use an ellipsis for the following menu items and buttons:
* About
* Advanced Options
* Check Spelling
* Close or Quit
* Configure [something]
* Delete or Remove
* Help
* Preferences
* Print Preview
* Properties
* Toolboxes

Projects/Usability/HIG Questions

2008-07-20T14:22:08Z

Seele:

= KDE4 HIG Questions and Requests =

Developer, please use this page to add questions and requests about the KDE4 Human Interface Guidelines (HIG)

* Please list questions about the KDE4 HIG here
* Also include your name/IRC nick/email if you want to be contacted for follow up questions
* Be as specific as possible and include a screenshot if applicable. [http://lists.kde.org/?l=kde-usability&m=120955187622753&w=2 This email on the kde-usability mailing list] is a '''good''' example of a HIG question/request.

* Which buttons have icons and when should we use/not use icons on buttons?
* The growth policy: are widgets supposed to grow and take all the available (horizontal) space, even in case of widgets that don't have a size policy for expanding?
* Description of alignment rule. See: http://lists.kde.org/?l=kde-core-devel&m=121639074230037&w=2 and
* Should the horizontal alignment of the layout be left- or center-? (eg: [http://img186.imageshack.us/img186/33/formlayoutalignxv0.png sample screenshot])
* Some musing about [[Projects/Usability/HIG_Questions/Standard_Shortcuts | Standard Shortcuts]]
* Remove or Delete for a button label?
* Order of Add Copy Remove/Delete in forms
* Options or Settings for a label?
* Reorder buttons (Move up down top bottom), icons, icons with text, or buttons with text labels?
* Listviews: http://ktown.kde.org/~fredrik/listviews/
* Visual style of notes/instructions in System Setting modules ([http://techbase.kde.org/Image:Systemsettings-information1.png Screenshot])
* when should tooltips be used? when is it too annoying and should be replaced by a "whats this?" function?
* Will the HIG specify a standard format and functions for the status bar?--[[User:JRT|JRT]] 03:02, 17 June 2008 (CEST)
* Will the HIG specify a minimum set of Zoom & View functions and specify which of these should be on the status bar and which should be in the Menu &/| Toolbars?--[[User:JRT|JRT]] 03:02, 17 June 2008 (CEST)
* I suggest adding a guideline to the checkboxes section saying that checkbox labels should always be "positively" formulated such as "enable ...". Never "disable ..." or even "Hide ..." (use "Show ..." instead. This contradicts what is currently in [[Projects/Usability/HIG/Check_Box | Check Box]]). If the user has to activate a checkbox to disactivate something this is like a double negation and induces unnecessary cognitive load. Also see: http://lists.kde.org/?l=kde-usability&m=121651903819214&w=2
*