gnome-control-center/panels/common/cc-permission-infobar.ui

<?xml version="1.0" encoding="UTF-8"?>
<interface>
  <template class="CcPermissionInfobar" parent="AdwBin">
    <child>
      <object class="AdwBanner" id="banner">
        <property name="button-label" translatable="yes">_Unlock…</property>
        <signal name="button-clicked" handler="banner_button_clicked_cb" swapped="yes"/>
      </object>
    </child>
  </template>
</interface>
common: Introduce "CcPermissionInfobar" widget The "CcPermissionInfobar" widget is a more descriptive way to communicate that some Settings panel needs authentication in order to perform certain actions. This widget doesn't handle the permissions (as in GPermission) itself. It needs to be binded to an existing instance of GPermission, and it will react to the permission's state (show when the current user is not authorized, and hide when the user is authorized). This is part of a big set of changes that aim to set a consistent authentication method accross Settings panels. See #685, #556, and #771 2019-12-19 15:45:23 +01:00			`<?xml version="1.0" encoding="UTF-8"?>`
			`<interface>`
common: Port to GTK4 This is only the bare minimum to make everything under panels/common build. Since these widgets are used by the main window, port them first. CcTimeEntry was particularly hard to port. That's because GtkEntry is a final class now. Overall, though, I'm happy with how it turned out to be - much cleaner, less code, more obvious. 2021-10-19 20:53:12 -03:00			`<template class="CcPermissionInfobar" parent="AdwBin">`
common: Introduce "CcPermissionInfobar" widget The "CcPermissionInfobar" widget is a more descriptive way to communicate that some Settings panel needs authentication in order to perform certain actions. This widget doesn't handle the permissions (as in GPermission) itself. It needs to be binded to an existing instance of GPermission, and it will react to the permission's state (show when the current user is not authorized, and hide when the user is authorized). This is part of a big set of changes that aim to set a consistent authentication method accross Settings panels. See #685, #556, and #771 2019-12-19 15:45:23 +01:00			`<child>`
general: Use AdwBanner in CcPermissionInfobar AdwBanner is a new adaptive widget that replaces GtkInfoBar. AdwBanner adapts better to mobile sizes and has an API that fits with how we use infobars. This commit changes CcPermissionInfobar to use an AdwBanner internally instead of a GtkInfoBar. It also re-implements part of GtkLockButton, as AdwBanner does not support adding arbitrary widgets. 2022-12-25 16:54:50 -06:00			`<object class="AdwBanner" id="banner">`
			`<property name="button-label" translatable="yes">_Unlock…</property>`
			`<signal name="button-clicked" handler="banner_button_clicked_cb" swapped="yes"/>`
common: Introduce "CcPermissionInfobar" widget The "CcPermissionInfobar" widget is a more descriptive way to communicate that some Settings panel needs authentication in order to perform certain actions. This widget doesn't handle the permissions (as in GPermission) itself. It needs to be binded to an existing instance of GPermission, and it will react to the permission's state (show when the current user is not authorized, and hide when the user is authorized). This is part of a big set of changes that aim to set a consistent authentication method accross Settings panels. See #685, #556, and #771 2019-12-19 15:45:23 +01:00			`</object>`
			`</child>`
			`</template>`
			`</interface>`