GNOME Project published library release Libadwaita 1.5which includes a set of components for styling the user interface, corresponding recommendations GNOME HIG (Human Interface Guidelines). The library includes ready-made widgets and objects for building applications that comply with the general GNOME style, the interface of which can be adaptively adjusted to screens of any size. The library code is written in C and distributed by licensed under LGPL 2.1+.
The libadwaita library is used in conjunction with GTK4 and includes components of the Adwaita theme used in GNOME, which have been moved out of GTK into a separate library. Moving GNOME styling elements into a separate library allows GNOME-specific changes to be developed separately from GTK, allowing GTK developers to focus on the core stuff and GNOME developers to more quickly and flexibly push forward styling changes they want without affecting GTK itself.
The library includes standard widgets covering various interface elements, such as lists, panels, editing blocks, buttons, tabs, search forms, dialog boxes, etc. The proposed widgets allow you to create universal interfaces that function seamlessly both on large PC and laptop screens, and on small touch screens of smartphones. The application interface changes dynamically depending on the screen size and available input devices. The library also includes a set of Adwaita styles that bring the appearance into line with GNOME guidelines without the need for manual adaptation.
The main change in libadwaita 1.5 was the reworking of adaptive widgets to create dialog boxes that adjust to the size of the visible area. Unlike traditional dialogs, which are housed in separate windows, new dialogs are rendered client-side, rendered inside existing windows, and cannot extend beyond the parent window. This approach simplifies the creation of universal dialogs that can be combined with interfaces for mobile and desktop systems, and also provides additional options for managing dialogs (for example, there is no need to monitor for exiting the window border, you can choose the behavior of close buttons, automatic expansion to full screen is provided in mobile versions of applications, the style of the current window, not the system, is taken into account when dimming the dialog).
In the future, it is planned to implement another version of such dialogs, linked not to windows, but to tabs inside the window, which may be needed in applications such as browsers so that dialogs associated with a tab do not overlap the main window when switching between tabs.
For mobile devices, support has been implemented for placing dialogs in the form of sheets docked at the bottom of the screen (bottom sheets), rather than in the form of sheets aligned to the center. Dialogs attached to the bottom save users from confusion with closing windows – in such dialogs, part of the parent window remains visible and the buttons for closing the parent window and the dialog itself are clearly separated, so it is now difficult to confuse them.
New dialogs are managed using the class AdwDialogwhich in most situations is like using a class GtkWindow, and the differences boil down to display and close operations. For example, the “:transient-for” property was replaced with a parameter in the adw_dialog_present() function, a new signal “::close-attempt” was added, and the processing of the “:can-close” parameter was changed. Instead of the AdwPreferencesWindow, AdwAboutWindow and AdwMessageDialog classes, it is proposed to use the classes AdwPreferencesDialog,
AdwAboutDialog And AdwAlertDialog.
Dialogs that do not have a parent window will still be treated as separate windows. Dialogs whose parent windows cannot be used to host dialogs will also function as windows, for example, if they do not allow resizing or do not have the AdwWindow and AdwApplicationWindow classes for them.
Not related to dialogue reworking changes in Libadwaita 1.5:
- To class AdwEntryRow added property “:text-length” to limit the text size in the input field.
- To class AdwMessageDialog added method remove_response().
- To class AdwBreakpointBinwhich allows you to change the user interface in any way depending on the size of the window, the ability to programmatically delete breakpoints has been added.
- To class AdwSwipeTracker added flag “:allow-window-handle“, allowing scrolling on top of the top panel (used in sheets attached to the bottom edge).
- Increased the brightness of the colors used when shading windows in a dark design style.
Thanks for reading:


