Difference between revisions of "Projects/Usability/HIG/LineEdit"

< Projects‎ | Usability‎ | HIG
Jump to: navigation, search
(Created page with "__NOTOC__ == Purpose == Edit controls display a single line of text to the user and allow the user to enter unconstrained text. A ''line edits'' is used to enter one line of ...")
 
 
(3 intermediate revisions by one user not shown)
Line 2: Line 2:
  
 
== Purpose ==
 
== Purpose ==
Edit controls display a single line of text to the user and allow the user to enter unconstrained text. A ''line edits'' is used to enter one line of text. If more than one line is required a ''text edit'' is the right control. Because edits are unconstrained and don’t accept valid data only, input validation and problem handling should be handled carefully.
+
The ''line edit'' control displays a single line of text to the user and allow the user to enter unconstrained text. If more than one line is required a text edit is the right control. Because line edits are unconstrained and don’t accept valid data only, input validation and problem handling should be handled carefully.
  
 
== Examples ==
 
== Examples ==
  
 
== Guidelines ==
 
== Guidelines ==
* Use edits for input of unconstrained text. If only a specific type of data is valid, use other controls.
+
=== Is this the right control ===
 +
* Use edits for input of single lines of unconstrained text.  
 +
* In case of multiple lines of text or more than a few words, use a [[Projects/Usability/HIG/TextEdit|text edit]]
 +
* Do not use a line edit if only a specific type of data is valid. Use a control for constrained input.
 +
=== Behavior ===
 
* Mask letters if edit is used to enter passwords.
 
* Mask letters if edit is used to enter passwords.
 
** When setting a new password, have it entered twice to prevent typos in passwords.
 
** When setting a new password, have it entered twice to prevent typos in passwords.
 
** Provide a "Show password" check box to unmask the password both when setting new and when entering existing passwords.
 
** Provide a "Show password" check box to unmask the password both when setting new and when entering existing passwords.
 
* Consider to use auto-complete feature to help users when entering data that is likely to be used repeatedly.
 
* Consider to use auto-complete feature to help users when entering data that is likely to be used repeatedly.
* Don't make users scroll unnecessarily; size text boxes to eliminate the need for scrolling.
+
* If the user enters a character that is known to be invalid, ignore the character and display an input problem hint that explains the valid characters (e.g. numbers vs. characters).
* Don't put horizontal scroll bars on multi-line text boxes.
+
* When disabling edit or text box, also disable any associated labels and buttons.
+
* If the user enters a character that is known to be invalid, ignore the character and display an input problem hint that explains the valid characters (e.g. numbers vs. characters).  
+
 
* If the input data has a value or format that is known to be invalid, display an input problem hint when the text box loses input focus (e.g. wrong zip code format).
 
* If the input data has a value or format that is known to be invalid, display an input problem hint when the text box loses input focus (e.g. wrong zip code format).
 
* If the input data is inconsistent with other controls on the window, give an error message when the entire input is complete, such as when users click OK for a modal dialog box.
 
* If the input data is inconsistent with other controls on the window, give an error message when the entire input is complete, such as when users click OK for a modal dialog box.
 
* Don't clear invalid input data unless users aren't able to correct errors easily. Doing so allows users to correct mistakes without starting over.
 
* Don't clear invalid input data unless users aren't able to correct errors easily. Doing so allows users to correct mistakes without starting over.
 +
=== Appearance ===
 +
* When disabling the line edit, also disable any associated labels and buttons.
 +
* Label every line edit with a descriptive caption to the left (cf. [[Projects/Usability/HIG/Alignment| alignment]]).
 +
* Create a buddy relation so access keys are assigned.
 +
[[Category:Usability]][[Category:Behavior]][[Category:Editing_and_Manipulation]][[Category:Unconstrained_input]]

Latest revision as of 13:46, 2 August 2013


[edit] Purpose

The line edit control displays a single line of text to the user and allow the user to enter unconstrained text. If more than one line is required a text edit is the right control. Because line edits are unconstrained and don’t accept valid data only, input validation and problem handling should be handled carefully.

[edit] Examples

[edit] Guidelines

[edit] Is this the right control

  • Use edits for input of single lines of unconstrained text.
  • In case of multiple lines of text or more than a few words, use a text edit
  • Do not use a line edit if only a specific type of data is valid. Use a control for constrained input.

[edit] Behavior

  • Mask letters if edit is used to enter passwords.
    • When setting a new password, have it entered twice to prevent typos in passwords.
    • Provide a "Show password" check box to unmask the password both when setting new and when entering existing passwords.
  • Consider to use auto-complete feature to help users when entering data that is likely to be used repeatedly.
  • If the user enters a character that is known to be invalid, ignore the character and display an input problem hint that explains the valid characters (e.g. numbers vs. characters).
  • If the input data has a value or format that is known to be invalid, display an input problem hint when the text box loses input focus (e.g. wrong zip code format).
  • If the input data is inconsistent with other controls on the window, give an error message when the entire input is complete, such as when users click OK for a modal dialog box.
  • Don't clear invalid input data unless users aren't able to correct errors easily. Doing so allows users to correct mistakes without starting over.

[edit] Appearance

  • When disabling the line edit, also disable any associated labels and buttons.
  • Label every line edit with a descriptive caption to the left (cf. alignment).
  • Create a buddy relation so access keys are assigned.

This page was last modified on 2 August 2013, at 13:46. This page has been accessed 934 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal