Skip to main content

Your submission was sent successfully! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates from Canonical and upcoming events where you can meet our team.Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

  1. Blog
  2. Article

Canonical
on 6 January 2012


With Unity we have been trying to raise the bar innovating in the User Experience with new UI elements, such as Dash and Overlay Scrollbars. But this shouldn’t come at the cost of overlooking less exciting but essential core areas of the OS.

Last cycle we started thinking about how to improve System Settings, and in Precise we hope some of these improvements can start landing.

After examining the current panels and a number of interesting and useful discussions with GNOME upstream, we have defined a small but useful set of changes that we hope will add another level of refinement.

Besides the usual detailed tweaks to options + related widgets, there were other areas we looked at. These are:

  • layout consistency
  • Unity customisation options
  • simplified structure

Switch pattern consistency

With the introduction of the switch widget in GTK 3, and consequentially in GNOME System Settings, different layout patterns have emerged. However, unlike its use in mobile design patterns where it is aligned to the right of its label, in System Settings there were instances of it aligning to the bottom or left of its label.

Because this mobile pattern is here to stay, and it is also easily encapsulable (eg. in menus), made sense to bring consistency to its alignment. Also cognitively, the control should be “after” the label.

This is the result:


Where the description under the header is optional.

Simplified structure

While adding new options to some panels, also reported in some bugs, it became obvious that a bit of reordering was necessary. The biggest change has been the removal of the Screen Settings. Its options have been distributed across more panels.

Where to start

You can review all the details starting from this document. As usual, specs and code are meant to be fixed, so I would be very grateful if you could share your most constructive opinions! 😉

Related posts


sergiodj
18 November 2024

Profile-guided optimization: A case study

Ubuntu Article

Software developers spend a huge amount of effort working on optimization – extracting more speed and better performance from their algorithms and programs. This work usually involves a lot of time-consuming manual investigation, making automatic performance optimization a hot topic in the world of software development. Profile-guided opt ...


Maximilian Blazek
6 November 2024

Designing Canonical’s Figma libraries for performance and structure

Design Article

How Canonical’s Design team rebuilt their Figma libraries, with practical guidelines on structure, performance, and maintenance processes. ...


Serdar Vural
28 October 2024

Canonical at India Mobile Congress 2024 – a retrospective

AI OpenStack

With an ambition to become Asia’s technology hub for telecommunications in the 5G/6G era, India hosts the annual India Mobile Congress (IMC) in Pragati Maidan, New Delhi. IMC is an annual trade exhibition for the telecommunication sector, bringing together operators, system integrators, as well as software and hardware vendors. It has now ...