[kde-guidelines] Styleguide: Tabs

Thomas Pfeiffer colomar at autistici.org
Wed Oct 9 17:55:02 UTC 2013


On Wednesday 09 October 2013 09:18:42 Heiko Tietze wrote:
> I tried to include the common KDE pages, most probbly implemented per
> listview. Horizontal tabs are that what you might expect with a tab
> control. But paged dialogs handle the content similar to vertical tabs.
> What do you think?
> 
> Viewing and Navigation > Grouping
> * Use tabs to show related information on separate pages.
> http://techbase.kde.org/Projects/Usability/TabControl
> 
> == Purpose ==
> A ''tab control'' is a way to present related information on separate pages.
> Tabs are used for dynamic window surface to increase the surface, to manage
> multiple documents within a single window, or as view of exclusive options.
> 
> Tabs have several advantages: The user can easily access available options
> or see which forms have been opened. Because foreground tabs are visually
> differentiated from background tabs the user knows what item is currently
> in progress. The disadvantage is when dealing with many tabs at once. When
> a window is tabbed to a certain number that exceeds the available area of
> the monitor, the tabs clutter up.
> 
> == Example ==
> == Guidelines ==
> === Is this the right control ===
> * Use tabs for
> ** many controls that can be organized within a few categories, like
> extended configuration settings ** for a variable number of sections, like
> browser pages
> ** to manage multiple documents
> * Do not use tabs
> ** for only one page (but do not hide the tab when more pages are expected)
> ** for controls that apply to the entire application
> ** for sequential steps, like wizards.
> === Behavior ===
> * Do not abuse other controls to simulate tab behavior.
> * Use horizontal tabs if the window has seven or fewer tabs and all the tabs
> fit on one row. * Use vertical tabs for less than five options with static
> content. Prefer vertical tabs for configuration content. * Do not use
> multiple rows of tabs because it leads to jumping UI elements, which
> destroys spatial memory. * Do not disable a tab when it doesn't apply to
> the current context; disable the controls on the page. * Do not make the
> settings on a page dependent on settings on other pages. ===  Appearance
> ===
> * If users are likely to start with the last tab displayed, make the tab
> persist and select it by default. Otherwise, select the first page by
> default. * Do not assign effects to changing tabs; tabs must be accessible
> in any order. * Do not place icons on horizontal tabs since they usually
> add unnecessary visual clutter and consume screen space. * Always add icons
> of 48x48px to vertical tabs.
> == Implementation ==
> [[Category:Usability]][[Category:Behavior]][[Category:Viewing_and_Navigation
> ]][[Category:Grouping]]

Perfect, nothing to comment from my side :)


More information about the kde-guidelines mailing list