Projects/Usability/HIG/ContextDrawer: Difference between revisions

From KDE TechBase
< Projects‎ | Usability‎ | HIG
(Created page with "= Context Drawer = thumb | 400px | none == Purpose == The Context Drawer is used to access controls that depend on the current context. This c...")
 
(HIG moved to community)
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
= Context Drawer =
{{ Moved To Community | KDE_Visual_Design_Group/HIG/ContextDrawer }}
 
[[File:Context_drawer.jpg | thumb | 400px | none]]
 
== Purpose ==
 
The Context Drawer is used to access controls that depend on the current context. This can be, for example, controls that affect a selected element in a list or that navigate through an opened document.
 
== Is this the right control? ==
 
Use a Context Drawer if your application has any functions which are only relevant in specific contexts, and which are not central enough to the application's main purpose to put them in the main user interface or in a toolbar. For actions which are always available, use the [[../../GlobalDrawer | Global Drawer]].
 
== Guidelines ==
 
* The Context Drawer is opened by swiping in from the left or right edge of the screen (depending on a system-wide setting) and closed by swiping in the other direction or tapping outside of it.
* At the top of the drawer, state which object the controls affect (e.g. "Selected email")
* By default, the Context Drawer simply contains a vertical list of action buttons which affect the currently selected/opened element
** Center the list vertically instead of top-aligning, to allow an easier reach with the thumb
* If needed, other controls related to the current context can be put in the Context Drawer
** Try to keep the content of the context drawer in one page. If there two distinct "modes" of contextual actions (for example navigating through a PDF either by table of contents or thumbnails), consider using two [[../../TabControl | Tabs]] to separate them, but never use more than two tabs
 
== Implementation ==
 
To be defined when component is ready.

Latest revision as of 11:26, 4 August 2016

This page is now on the community wiki.