Projects/Usability/HIG/Dialogs: Difference between revisions

    From KDE TechBase
    < Projects‎ | Usability‎ | HIG
    No edit summary
    (HIG moved to community)
     
    (16 intermediate revisions by 5 users not shown)
    Line 1: Line 1:
    == Dialogs ==
    {{ Moved To Community | KDE_Visual_Design_Group/HIG/Dialogs }}
     
     
    '''Reduce the dialog flood'''
    * Do not nest dialogs more than two levels deep.
    <small>For example "Configuration dialog > Advanced dialog" is ok, "Configuration dialog > Advanced dialog > Further settings dialog" is too deep.</small>
     
    * Avoid dialogs that contain only one or two options. If possible, use inline-editing instead.
    <small> For example, to rename a list item, do not show a dialog but allow the user to change the label inside the list</small>
     
    * 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 info panels instead.
    <small>See [[Projects/Usability/HIG/Messages|Messages]]) </small>
     
     
    '''Position of dialogs'''
    * Always keep dialogs on top of their parent.
    <small>This is usually taken care of by the window manager. But in '''composed applications''', focus problems may occur. Check carefully in this case. </small>
     
    * If reference in the parent window is required, make sure your dialog does not cover relevant parts.
    <small>For example a find dialog should neither be centered, nor cover a search result. </small>
     
     
    '''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.

    Latest revision as of 11:26, 4 August 2016

    This page is now on the community wiki.