{"id":114355,"date":"2024-03-16T12:25:47","date_gmt":"2024-03-16T10:25:49","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-biblioteki-libadwaita-1-5-dlya-sozdaniya-interfejsov-v-stile-gnome"},"modified":"2024-03-16T12:25:47","modified_gmt":"2024-03-16T10:25:49","slug":"vypusk-biblioteki-libadwaita-1-5-dlya-sozdaniya-interfejsov-v-stile-gnome","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-biblioteki-libadwaita-1-5-dlya-sozdaniya-interfejsov-v-stile-gnome","title":{"rendered":"The release of the Libadwaita 1.5 library for building interfaces in the GNOME style.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

The GNOME Project has released version 1.5 of the Libadwaita library, which includes a set of components for styling user interfaces in accordance with GNOME HIG (Human Interface Guidelines). The library includes ready-made widgets and objects for building applications that align with the overall GNOME style, with interfaces that can adapt to screens of any size. The library code is written in C and is distributed under the LGPL 2.1+ license. <\/p>\n

The libadwaita library is used in conjunction with GTK4 and includes components from the Adwaita theme used in GNOME, which have been extracted from GTK into a separate library. Extracting GNOME's visual styling elements into a separate library enables the necessary changes for GNOME to be developed independently of GTK, allowing GTK developers to focus on foundational aspects while GNOME developers can more rapidly and flexibly implement the styling changes they require without impacting GTK itself. <\/p>\n

The library includes standard widgets that cover various interface elements such as lists, panels, editing blocks, buttons, tabs, search forms, dialog windows, etc. The proposed widgets allow for the creation of versatile interfaces that function seamlessly on both large PC and laptop screens and small touchscreens of smartphones. The user interface of applications dynamically adapts based on the screen size and available input devices. The library also includes a set of Adwaita styles that align appearances with GNOME guidelines, eliminating the need for manual adaptation.

\"The<\/center> <\/p>\n

The main change in libadwaita 1.5 is the redesign of adaptive widgets for creating dialog windows that adjust to the size of the visible area. Unlike traditional dialogs that are placed in separate windows, the new dialogs are formed on the client side, rendered within existing windows, and cannot extend beyond the parent window. This approach simplifies the creation of versatile dialogs that work across mobile and desktop interfaces and provides enhanced control over dialogs (for example, there's no need to track overflow, behavior regarding close buttons can be chosen, automatic full-screen expansion is enabled in mobile app versions, and the style of the current window, rather than the system, is taken into account when dimming the dialog).

\"The\"The<\/center> <\/p>\n

There are plans to implement another version of such dialogs that are attached not to windows but to tabs within a window, which may be useful in applications like browsers, so that tab-related dialogs do not overlap the main window when switching between tabs. <\/p>\n

Support for displaying dialogs as bottom sheets, pinned to the bottom of the screen, has been implemented for mobile devices, rather than as center-aligned sheets. Bottom-pinned dialogs free users from confusion about closing windows \u2014 in such dialogs, part of the parent window remains visible, and the close buttons for both the parent window and the dialog are clearly separated, making them difficult to confuse.

\"The<\/center> <\/p>\n

Managing new dialogs is done using the AdwDialog class, which generally behaves similarly to the GtkWindow class, with differences mainly in display and closing operations. For example, the ':transient-for' property has been replaced with a parameter in the adw_dialog_present() function, a new signal '::close-attempt' has been added, and the handling of the ':can-close' parameter has been modified. Instead of using the AdwPreferencesWindow, AdwAboutWindow, and AdwMessageDialog classes, it is proposed to use the AdwPreferencesDialog, AdwAboutDialog, and AdwAlertDialog classes with the new dialogs. <\/p>\n

Dialogs that do not have a parent window will still be handled as separate windows. Dialogs whose parent windows cannot be used for dialog placement, for example, if they do not allow resizing or are missing the AdwWindow and AdwApplicationWindow classes, will also function as windows. <\/p>\n

Changes in Libadwaita 1.5 not related to dialog overhauls: <\/p>\n