Unify sidebar appearance
Open, Needs TriagePublic

Description

KDE software has a lot of different visual styles for sidebars, many ably illustrated in T11093: Improve Consistency across the Board:

Let's unify these to have the following characteristics:

  • White background (with default breeze color scheme; obviously it should follow the color scheme
  • Full width and height; top touches titlebar/tools area, bottom touches bottom window edge or status bar, left side touches left window edge, etc.
  • Single-pixel vertical line separates the sidebar from the content area on the right
  • When icons are large, they should be colorful: T10165: Large category icons should all be colorful
felixernst added a subscriber: felixernst.EditedJun 29 2019, 1:55 PM

There are two different scenarios for sidebars explained in T11093: Improve Consistency across the Board. Just to be clear: This task is only about the second one, right? I would tend to think these can be viewed as separate issues for now (roughly quoting @niccolove):

  1. Sidebars with many different pages that can be navigated through tabs - (we might want a separate task for this)
  2. Sidebars used to help the user navigate through the pages of an application - (this task)

So talking about the second kind of sidebar:

Let's unify these to have the following characteristics:

  • White background (with default breeze color scheme; obviously it should follow the color scheme
  • Full width and height; top touches titlebar/tools area, bottom touches bottom window edge or status bar, left side touches left window edge, etc.
  • Single-pixel vertical line separates the sidebar from the content area on the right
  • When icons are large, they should be colorful

+1.
I would think we only need two different sidebar appearances for this: The one used in System Settings when there are many entries and D20908: Redesign QML applet configuration windows when there are few.

ndavis added a subscriber: ndavis.Jun 29 2019, 4:20 PM

I would think we only need two different sidebar appearances for this: The one used in System Settings when there are many entries and D20908: RFC: Redesign QML applet configuration windows when there are few.

I will guess that sidebars should use the systemsettings-like list as sidebar vs configuration-like big icon above text when there are lots of elements. What about tabs on top? I'd say those should be used when they only change a part of the window and not the whole view (except in falkon of course), thus switching ksys to to big icon above text style, correct?

What about tabs on top? I'd say those should be used when they only change a part of the window and not the whole view (except in falkon of course),

Yes, in cases in which tabs can be replaced by sidebars without detriment we certainly should aim for unification to a single ui design. Aside from that I don't really have an opinion yet on when tabs should be used.

thus switching ksys to to big icon above text style, correct?

I think it could work for KSysGuard but I also think that it is in the awkward position of having exactly two tabs. This makes a sidebar seem a bit excessive with the benefits of having big icons for both pages (and unification).

What about tabs on top? I'd say those should be used when they only change a part of the window and not the whole view (except in falkon of course), thus switching ksys to to big icon above text style, correct?

Forget that, there's a much better definitions. Tabs should be used when the views are editable from the user, aka when the user can add, close and move tabs, such as in falkon, dolphin, etc. Also, tabs should be used when different views do not display different content: if you open multiple tabs on dolphin they are all about file viewing, while sidebars with big icons should be used when your are dividing different things in categories which should not change over time nor be user-editable.

niccolove moved this task from Reported to VDG Discussion on the Consistency board.