brl/gnome-shell
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
4bfdd677e3
gnome-shell/js/extensionPrefs/ui/extensions-window.ui

306 lines
13 KiB
Plaintext
Raw Normal View History

extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated with glade 3.22.0 -->
<interface>
<requires lib="gtk+" version="3.20"/>
extensionPrefs: Add standard app elements In order to turn the extensions-prefs tool into a proper GNOME app, it should follow basic app patterns, so add a primary menu and about dialog. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 00:51:35 -05:00
<menu id="primary-menu">
<section>
<item>
<attribute name="label" translatable="yes">Help</attribute>
<attribute name="action">win.show-help</attribute>
</item>
<item>
<attribute name="label" translatable="yes">About Extensions</attribute>
<attribute name="action">win.show-about</attribute>
</item>
</section>
</menu>
extensionPrefs: Add info popover to headerbar Extensions can have a major impact on stability and performance. Now that the tool will become the main way for users to manage their extensions, it is an appropriate place to warn the user of that risk. Add a small info popover to the headerbar to display that warning, together with the previously removed hint of where to go for finding new extensions. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2020-01-24 13:00:37 -05:00
<object class="GtkPopover" id="infoPopover">
<child>
<object class="GtkBox">
<property name="visible">True</property>
<property name="orientation">vertical</property>
<property name="margin">12</property>
<property name="spacing">6</property>
<child>
<object class="GtkLabel">
<property name="visible">True</property>
<property name="label" translatable="yes">To find and add extensions, visit &lt;a href="https://extensions.gnome.org"&gt;extensions.gnome.org&lt;/a&gt;.</property>
<property name="use_markup">True</property>
<property name="xalign">0</property>
</object>
</child>
<child>
<object class="GtkLabel">
<property name="visible">True</property>
<property name="label" translatable="yes">Warning</property>
<property name="xalign">0</property>
<property name="margin_top">6</property>
<attributes>
<attribute name="weight" value="bold"/>
</attributes>
</object>
</child>
<child>
<object class="GtkLabel">
<property name="visible">True</property>
<property name="label" translatable="yes">Extensions can cause system issues, including performance problems. If you encounter problems with your system, it is recommended to disable all extensions.</property>
<property name="wrap">True</property>
<property name="max_width_chars">40</property>
<property name="xalign">0</property>
</object>
</child>
</object>
</child>
</object>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
<template class="ExtensionsWindow" parent="GtkApplicationWindow">
<property name="default_width">800</property>
<property name="default_height">500</property>
<child type="titlebar">
<object class="GtkHeaderBar">
<property name="visible">True</property>
extensionPrefs: Rename to Extensions ... and make the application user-visible. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2020-01-24 11:00:24 -05:00
<property name="title" translatable="yes">Extensions</property>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
<property name="show_close_button">True</property>
extensionPrefs: Add info popover to headerbar Extensions can have a major impact on stability and performance. Now that the tool will become the main way for users to manage their extensions, it is an appropriate place to warn the user of that risk. Add a small info popover to the headerbar to display that warning, together with the previously removed hint of where to go for finding new extensions. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2020-01-24 13:00:37 -05:00
<child>
<object class="GtkMenuButton">
<property name="visible">True</property>
<property name="popover">infoPopover</property>
<child>
<object class="GtkImage">
<property name="visible">True</property>
<property name="icon_name">dialog-information-symbolic</property>
</object>
</child>
</object>
</child>
extensionPrefs: Add standard app elements In order to turn the extensions-prefs tool into a proper GNOME app, it should follow basic app patterns, so add a primary menu and about dialog. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 00:51:35 -05:00
<child>
<object class="GtkMenuButton" id="menuButton">
<property name="visible">True</property>
<property name="can_focus">True</property>
<property name="receives_default">True</property>
<property name="menu_model">primary-menu</property>
<child>
<object class="GtkImage">
<property name="visible">True</property>
<property name="icon_name">open-menu-symbolic</property>
</object>
</child>
</object>
<packing>
<property name="pack_type">end</property>
</packing>
</child>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
<child>
<object class="GtkSwitch" id="killSwitch">
<property name="visible">True</property>
</object>
<packing>
<property name="pack_type">end</property>
</packing>
</child>
</object>
</child>
<child>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<object class="GtkBox">
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
<property name="visible">True</property>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<property name="orientation">vertical</property>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
<child>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<object class="GtkStack" id="mainStack">
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
<property name="visible">True</property>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<property name="transition_type">crossfade</property>
<property name="vexpand">True</property>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
<child>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<object class="GtkScrolledWindow" id="scrolledWindow">
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
<property name="visible">True</property>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<property name="hscrollbar_policy">never</property>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
<child>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<object class="GtkViewport">
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
<property name="visible">True</property>
extensionPrefs: Split user and system extensions Until now, it didn't matter whether an extension was installed in the user's home or system-wide. However with support for uninstallation, there is now a significant different, as that action is only available for user extensions. Account for that by separating extensions by type, so that users don't have to second-guess which extensions can be fully-managed and which appear as part of the system. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 02:08:05 -05:00
<child>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<object class="GtkBox" id="mainBox">
extensionPrefs: Don't fill view Extension rows contain both name/description and controls to open preferences and enable/disable the extension. Those elements become disassociated when the row expands too much horizontally, so instead of filling the entire view, switch to the embedded list style[0]. [0] https://developer.gnome.org/hig/stable/lists.html.en https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 01:27:48 -05:00
<property name="visible">True</property>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<property name="orientation">vertical</property>
<property name="halign">center</property>
<property name="margin">36</property>
<property name="spacing">12</property>
<child>
<object class="GtkLabel">
<property name="visible"
bind-source="userList"
bind-property="visible"
bind-flags="sync-create"/>
<property name="halign">start</property>
<property name="hexpand">True</property>
<property name="label" translatable="yes">Manually Installed</property>
<attributes>
<attribute name="weight" value="bold"/>
</attributes>
</object>
</child>
<child>
<object class="GtkListBox" id="userList">
<property name="visible">True</property>
<property name="selection_mode">none</property>
<property name="margin_bottom">24</property>
<style>
<class name="frame"/>
</style>
</object>
</child>
<child>
<object class="GtkLabel">
<property name="visible"
bind-source="systemList"
bind-property="visible"
bind-flags="sync-create"/>
<property name="halign">start</property>
<property name="hexpand">True</property>
<property name="label" translatable="yes">Built-In</property>
<attributes>
<attribute name="weight" value="bold"/>
</attributes>
</object>
</child>
<child>
<object class="GtkListBox" id="systemList">
<property name="visible">True</property>
<property name="selection_mode">none</property>
<style>
<class name="frame"/>
</style>
</object>
</child>
extensionPrefs: Don't fill view Extension rows contain both name/description and controls to open preferences and enable/disable the extension. Those elements become disassociated when the row expands too much horizontally, so instead of filling the entire view, switch to the embedded list style[0]. [0] https://developer.gnome.org/hig/stable/lists.html.en https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 01:27:48 -05:00
</object>
</child>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
</object>
</child>
</object>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<packing>
<property name="name">main</property>
</packing>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
</child>
<child>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<object class="GtkBox">
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
<property name="visible">True</property>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<property name="orientation">vertical</property>
<property name="margin">32</property>
<property name="spacing">6</property>
<property name="valign">center</property>
<child>
<object class="GtkImage">
<property name="visible">True</property>
<property name="pixel_size">96</property>
<property name="icon_name">org.gnome.Extensions-symbolic</property>
</object>
</child>
<child>
<object class="GtkLabel">
<property name="visible">True</property>
<property name="label" translatable="yes">No Installed Extensions</property>
<attributes>
<attribute name="weight" value="bold"/>
<attribute name="scale" value="1.44"/>
</attributes>
</object>
</child>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
</object>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<packing>
<property name="name">placeholder</property>
</packing>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
</child>
<child>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<object class="GtkBox">
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
<property name="visible">True</property>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<property name="margin_left">100</property>
<property name="margin_right">100</property>
<property name="margin_top">100</property>
<property name="margin_bottom">60</property>
<property name="orientation">vertical</property>
<property name="spacing">12</property>
<child>
<object class="GtkLabel">
<property name="visible">True</property>
<property name="label" translatable="yes">Something’s gone wrong</property>
<attributes>
<attribute name="scale" value="1.44"/>
</attributes>
<style>
<class name="dim-label"/>
</style>
</object>
</child>
<child>
<object class="GtkLabel">
<property name="visible">True</property>
<property name="label" translatable="yes">We’re very sorry, but it was not possible to get the list of installed extensions. Make sure you are logged into GNOME and try again.</property>
<property name="justify">center</property>
<property name="wrap">True</property>
<style>
<class name="dim-label"/>
</style>
</object>
</child>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
</object>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<packing>
<property name="name">noshell</property>
</packing>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
</child>
</object>
</child>
<child>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<object class="GtkActionBar" id="updatesBar">
<property name="no_show_all">True</property>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
<child>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<object class="GtkImage">
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
<property name="visible">True</property>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<property name="pixel-size">24</property>
<property name="margin">6</property>
<property name="icon_name">software-update-available-symbolic</property>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
<style>
extensionPrefs: Remove stray > in .ui file This slipped through as GtkBuilder still accepts it, but let's not rely on that and fix our XML. https://gitlab.gnome.org/GNOME/gnome-shell/issues/2180
2020-02-06 14:03:35 -05:00
<class name="warning"/>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
</style>
</object>
</child>
<child>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<object class="GtkBox">
<property name="visible">True</property>
<property name="orientation">vertical</property>
<child>
<object class="GtkLabel">
<property name="visible">True</property>
<property name="halign">start</property>
<property name="label">Extension Updates Ready</property>
<attributes>
<attribute name="weight" value="bold"/>
</attributes>
</object>
</child>
<child>
<object class="GtkLabel" id="updatesLabel">
<property name="visible">True</property>
<property name="halign">start</property>
</object>
</child>
</object>
</child>
<child>
<object class="GtkButton">
extensionPrefs: Make the Log Out button a proper verb https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/981
2020-02-05 14:43:59 -05:00
<property name="label" translatable="yes">Log Out…</property>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
<property name="visible">True</property>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<property name="valign">center</property>
<property name="action-name">win.logout</property>
<property name="receives_default">True</property>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
<style>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<class name="suggested-action"/>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
</style>
</object>
extensionPrefs: Support extension updates Now that we have support for extension updates in the shell, we need some place to display the updates to the user. As we are establishing the Extensions app as the primary way for managing extensions, it's a natural place for that functionality. Show which extensions have updates available, and offer a log out button (so gnome-shell can apply the updates when logging back in). https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-30 09:20:04 -05:00
<packing>
<property name="pack_type">end</property>
</packing>
extensionPrefs: Use template for ExtensionsWindow As the window will become more complex, it makes sense to let GtkBuilder construct the UI and focus on the actual implementation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1968
2019-11-29 20:48:18 -05:00
</child>
</object>
</child>
</object>
</child>
</template>
</interface>
Reference in New Issue Copy Permalink