applications/gnome-control-center
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
gnome-control-center/panels/common/cc-permission-infobar.ui

69 lines
2.7 KiB
Text
Raw Normal View History

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
<property name="valign">start</property>
<child>
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
<object class="GtkRevealer" id="revealer">
<property name="hexpand">True</property>
<property name="reveal-child">True</property>
<child>
<object class="GtkInfoBar">
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>
<object class="GtkBox">
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
<property name="margin-top">10</property>
<property name="margin-bottom">10</property>
<property name="margin-start">10</property>
<property name="margin-end">10</property>
<property name="spacing">10</property>
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>
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
<object class="GtkImage">
<property name="icon-name">system-lock-screen-symbolic</property>
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>
<child>
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
<object class="GtkBox">
<property name="hexpand">True</property>
<property name="orientation">vertical</property>
<child>
<object class="GtkLabel" id="title">
<property name="halign">start</property>
<!-- Actual string set in code -->
<property name="label"></property>
<attributes>
<attribute name="weight" value="bold"/>
</attributes>
</object>
</child>
<child>
<object class="GtkLabel">
<property name="halign">start</property>
<property name="label" translatable="yes">Some settings must be unlocked before they can be changed.</property>
</object>
</child>
</object>
</child>
</object>
</child>
<child>
<object class="GtkCenterBox">
<property name="margin-top">10</property>
<property name="margin-bottom">10</property>
<property name="margin-start">10</property>
<property name="margin-end">10</property>
<child type="end">
<object class="GtkLockButton" id="lock_button">
<property name="receives-default">True</property>
<property name="label" translatable="yes">Unlock…</property>
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>
</object>
</child>
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
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>
</object>
</child>
</template>
</interface>
Reference in a new issue Copy permalink