brl/gnome-shell
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
859ded5790
gnome-shell/subprojects/extensions-app/data/ui/extensions-window.ui

205 lines
8.9 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-30 01:48:18 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<interface>
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 05:51:35 +00: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: 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-30 01:48:18 +00:00
<template class="ExtensionsWindow" parent="GtkApplicationWindow">
extensions-app: Use consistent style for property names GtkBuilder understands both dashes and underscores in property names, and we currently use a mix of both. The actual properties use dashes, so settle on that. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
<property name="default-width">800</property>
<property name="default-height">500</property>
extensions-app: Set title on window instead of headerbar GTK4 will remove the GtkHeaderBar:title property, so stop using it and set the window's title property instead, as that's what headbars use in both GTK3 and GTK4 unless explicitly overridden. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00: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-30 01:48:18 +00:00
<child type="titlebar">
<object class="GtkHeaderBar">
Port extensions app and portal to GTK4 With the previous preparations in place, it is time to take the plunge. As both the app and the portal use the same small library for handling external windows, port everything at once to avoid the hassle of building and installing two versions of the library. With the portal using GTK4 now, all extensions must port their preference widgets as well. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
<child type="end">
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 05:51:35 +00:00
<object class="GtkMenuButton" id="menuButton">
extensions-app: Use consistent style for property names GtkBuilder understands both dashes and underscores in property names, and we currently use a mix of both. The actual properties use dashes, so settle on that. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
<property name="receives-default">True</property>
<property name="menu-model">primary-menu</property>
Port extensions app and portal to GTK4 With the previous preparations in place, it is time to take the plunge. As both the app and the portal use the same small library for handling external windows, port everything at once to avoid the hassle of building and installing two versions of the library. With the portal using GTK4 now, all extensions must port their preference widgets as well. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
<property name="icon-name">open-menu-symbolic</property>
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 05:51:35 +00:00
</object>
</child>
Port extensions app and portal to GTK4 With the previous preparations in place, it is time to take the plunge. As both the app and the portal use the same small library for handling external windows, port everything at once to avoid the hassle of building and installing two versions of the library. With the portal using GTK4 now, all extensions must port their preference widgets as well. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
<child type="end">
extensions-app: Add extension filtering It's possible for the list of installed extension to get long enough to make searching more convenient than scrolling. Support that by implementing the standard search pattern[0] with a hidden search bar and a toggle in the headerbar. [0] https://developer.gnome.org/hig/stable/search.html.en https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3382
2020-11-11 01:37:20 +00:00
<object class="GtkToggleButton" id="searchButton">
extensions-app: Use consistent style for property names GtkBuilder understands both dashes and underscores in property names, and we currently use a mix of both. The actual properties use dashes, so settle on that. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
<property name="receives-default">True</property>
Port extensions app and portal to GTK4 With the previous preparations in place, it is time to take the plunge. As both the app and the portal use the same small library for handling external windows, port everything at once to avoid the hassle of building and installing two versions of the library. With the portal using GTK4 now, all extensions must port their preference widgets as well. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
<property name="icon-name">edit-find-symbolic</property>
extensions-app: Add extension filtering It's possible for the list of installed extension to get long enough to make searching more convenient than scrolling. Support that by implementing the standard search pattern[0] with a hidden search bar and a toggle in the headerbar. [0] https://developer.gnome.org/hig/stable/search.html.en https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3382
2020-11-11 01:37:20 +00:00
<child>
Port extensions app and portal to GTK4 With the previous preparations in place, it is time to take the plunge. As both the app and the portal use the same small library for handling external windows, port everything at once to avoid the hassle of building and installing two versions of the library. With the portal using GTK4 now, all extensions must port their preference widgets as well. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
<object class="GtkShortcutController">
<property name='scope'>global</property>
<child>
<object class='GtkShortcut'>
<property name='trigger'>&lt;Control&gt;f</property>
<property name='action'>activate</property>
</object>
</child>
<child>
<object class='GtkShortcut'>
<property name='trigger'>&lt;Control&gt;s</property>
<property name='action'>activate</property>
</object>
</child>
extensions-app: Add extension filtering It's possible for the list of installed extension to get long enough to make searching more convenient than scrolling. Support that by implementing the standard search pattern[0] with a hidden search bar and a toggle in the headerbar. [0] https://developer.gnome.org/hig/stable/search.html.en https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3382
2020-11-11 01:37:20 +00:00
</object>
</child>
</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-30 01:48:18 +00:00
</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 14:20:04 +00:00
<object class="GtkBox">
<property name="orientation">vertical</property>
extensions-app: Add extension filtering It's possible for the list of installed extension to get long enough to make searching more convenient than scrolling. Support that by implementing the standard search pattern[0] with a hidden search bar and a toggle in the headerbar. [0] https://developer.gnome.org/hig/stable/search.html.en https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3382
2020-11-11 01:37:20 +00:00
<child>
<object class="GtkSearchBar" id="searchBar">
Port extensions app and portal to GTK4 With the previous preparations in place, it is time to take the plunge. As both the app and the portal use the same small library for handling external windows, port everything at once to avoid the hassle of building and installing two versions of the library. With the portal using GTK4 now, all extensions must port their preference widgets as well. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
<property name="key-capture-widget">ExtensionsWindow</property>
extensions-app: Add extension filtering It's possible for the list of installed extension to get long enough to make searching more convenient than scrolling. Support that by implementing the standard search pattern[0] with a hidden search bar and a toggle in the headerbar. [0] https://developer.gnome.org/hig/stable/search.html.en https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3382
2020-11-11 01:37:20 +00:00
<property name="search-mode-enabled"
bind-source="searchButton"
bind-property="active"
bind-flags="bidirectional"/>
<child>
<object class="GtkSearchEntry" id="searchEntry">
<property name="max-width-chars">35</property>
</object>
</child>
</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-30 01:48:18 +00: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 14:20:04 +00:00
<object class="GtkStack" id="mainStack">
extensions-app: Use consistent style for property names GtkBuilder understands both dashes and underscores in property names, and we currently use a mix of both. The actual properties use dashes, so settle on that. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
<property name="transition-type">crossfade</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 14:20:04 +00:00
<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-30 01:48:18 +00:00
<child>
Port extensions app and portal to GTK4 With the previous preparations in place, it is time to take the plunge. As both the app and the portal use the same small library for handling external windows, port everything at once to avoid the hassle of building and installing two versions of the library. With the portal using GTK4 now, all extensions must port their preference widgets as well. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
<object class="GtkStackPage">
<property name="name">main</property>
<property name="child">
extensions-app: Use AdwPreferencesPage and AdwPreferencesGroup Give consistent styling and sizing to extensions lists. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1997>
2021-10-18 13:18:11 +00:00
<object class="AdwPreferencesPage">
extensions-app: Move headerbar content to the main view With the new borderless style of libadwaita, the global switch in the headerbar did not look good. Moving it to the main view is the opportunity to also move the content of the information popover. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2114>
2022-01-18 10:19:54 +00:00
<child>
<object class="AdwPreferencesGroup">
<child>
<object class="AdwActionRow">
<property name="title" translatable="yes">Extensions</property>
<property name="subtitle" translatable="yes">Extensions can cause performance and stability issues. Disable extensions if you encounter problems with your system.</property>
<property name="activatable-widget">enabledSwitch</property>
<child>
<object class="GtkSwitch" id="enabledSwitch">
<property name="action-name">win.user-extensions-enabled</property>
<property name="valign">center</property>
</object>
</child>
</object>
</child>
</object>
</child>
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 07:08:05 +00:00
<child>
extensions-app: Use AdwPreferencesPage and AdwPreferencesGroup Give consistent styling and sizing to extensions lists. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1997>
2021-10-18 13:18:11 +00:00
<object class="AdwPreferencesGroup" id="userGroup">
<property name="title" translatable="yes">Manually Installed</property>
extensions-app: Move headerbar content to the main view With the new borderless style of libadwaita, the global switch in the headerbar did not look good. Moving it to the main view is the opportunity to also move the content of the information popover. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2114>
2022-01-18 10:19:54 +00:00
<property name="description" translatable="yes">To find and add extensions, visit &lt;a href="https://extensions.gnome.org"&gt;extensions.gnome.org&lt;/a&gt;.</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 14:20:04 +00:00
<child>
extensions-app: Use AdwPreferencesPage and AdwPreferencesGroup Give consistent styling and sizing to extensions lists. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1997>
2021-10-18 13:18:11 +00:00
<object class="GtkListBox" id="userList">
<property name="selection-mode">none</property>
<style>
extensions-app: Change lists style class to `.boxed-list` The previous `.content` style class is deprecated. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2114>
2022-01-18 10:37:51 +00:00
<class name="boxed-list"/>
extensions-app: Use AdwPreferencesPage and AdwPreferencesGroup Give consistent styling and sizing to extensions lists. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1997>
2021-10-18 13:18:11 +00:00
</style>
</object>
</child>
</object>
</child>
<child>
<object class="AdwPreferencesGroup" id="systemGroup">
<property name="title" translatable="yes">Built-In</property>
<child>
<object class="GtkListBox" id="systemList">
<property name="selection-mode">none</property>
<style>
extensions-app: Change lists style class to `.boxed-list` The previous `.content` style class is deprecated. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2114>
2022-01-18 10:37:51 +00:00
<class name="boxed-list"/>
extensions-app: Use AdwPreferencesPage and AdwPreferencesGroup Give consistent styling and sizing to extensions lists. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1997>
2021-10-18 13:18:11 +00: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 14:20:04 +00:00
</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 06:27:48 +00: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-30 01:48:18 +00:00
</object>
Port extensions app and portal to GTK4 With the previous preparations in place, it is time to take the plunge. As both the app and the portal use the same small library for handling external windows, port everything at once to avoid the hassle of building and installing two versions of the library. With the portal using GTK4 now, all extensions must port their preference widgets as well. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
</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-30 01:48:18 +00:00
</object>
</child>
<child>
Port extensions app and portal to GTK4 With the previous preparations in place, it is time to take the plunge. As both the app and the portal use the same small library for handling external windows, port everything at once to avoid the hassle of building and installing two versions of the library. With the portal using GTK4 now, all extensions must port their preference widgets as well. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
<object class="GtkStackPage">
<property name="name">placeholder</property>
<property name="child">
extensions-app: Replace empty views with AdwStatusPage AdwStatusPage provides consistent styling for empty views. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1997>
2021-10-04 13:45:21 +00:00
<object class="AdwStatusPage">
<property name="icon-name">org.gnome.Extensions-symbolic</property>
<property name="title" translatable="yes">No Installed Extensions</property>
extensions-app: Move headerbar content to the main view With the new borderless style of libadwaita, the global switch in the headerbar did not look good. Moving it to the main view is the opportunity to also move the content of the information popover. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2114>
2022-01-18 10:19:54 +00:00
<property name="description" translatable="yes">To find and add extensions, visit &lt;a href="https://extensions.gnome.org"&gt;extensions.gnome.org&lt;/a&gt;.</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 14:20:04 +00:00
</object>
Port extensions app and portal to GTK4 With the previous preparations in place, it is time to take the plunge. As both the app and the portal use the same small library for handling external windows, port everything at once to avoid the hassle of building and installing two versions of the library. With the portal using GTK4 now, all extensions must port their preference widgets as well. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
</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-30 01:48:18 +00:00
</object>
</child>
<child>
Port extensions app and portal to GTK4 With the previous preparations in place, it is time to take the plunge. As both the app and the portal use the same small library for handling external windows, port everything at once to avoid the hassle of building and installing two versions of the library. With the portal using GTK4 now, all extensions must port their preference widgets as well. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
<object class="GtkStackPage">
<property name="name">noshell</property>
<property name="child">
extensions-app: Replace empty views with AdwStatusPage AdwStatusPage provides consistent styling for empty views. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1997>
2021-10-04 13:45:21 +00:00
<object class="AdwStatusPage">
<property name="title" translatable="yes">Something’s gone wrong</property>
<property name="description" 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>
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 14:20:04 +00:00
</object>
Port extensions app and portal to GTK4 With the previous preparations in place, it is time to take the plunge. As both the app and the portal use the same small library for handling external windows, port everything at once to avoid the hassle of building and installing two versions of the library. With the portal using GTK4 now, all extensions must port their preference widgets as well. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
</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-30 01:48:18 +00:00
</object>
</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 14:20:04 +00:00
<object class="GtkActionBar" id="updatesBar">
Port extensions app and portal to GTK4 With the previous preparations in place, it is time to take the plunge. As both the app and the portal use the same small library for handling external windows, port everything at once to avoid the hassle of building and installing two versions of the library. With the portal using GTK4 now, all extensions must port their preference widgets as well. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
<property name="revealed">False</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-30 01:48:18 +00: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 14:20:04 +00:00
<object class="GtkImage">
<property name="pixel-size">24</property>
extensions-app: Stop using :margin shortcut The property has been removed in GTK4, so prepare for a port by setting the four individual margin properties instead. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
<property name="margin-start">6</property>
<property name="margin-end">6</property>
<property name="margin-top">6</property>
<property name="margin-bottom">6</property>
extensions-app: Use consistent style for property names GtkBuilder understands both dashes and underscores in property names, and we currently use a mix of both. The actual properties use dashes, so settle on that. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
<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-30 01:48:18 +00: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 19:03:35 +00: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-30 01:48:18 +00: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 14:20:04 +00:00
<object class="GtkBox">
<property name="orientation">vertical</property>
extensions-app: Vertically center updates bar text With the new stylesheet, the text is too close to the bar border. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1997>
2021-10-05 07:49:13 +00:00
<property name="valign">center</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 14:20:04 +00:00
<child>
<object class="GtkLabel">
<property name="halign">start</property>
extensions-app: Fix translatable string https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1231
2020-05-01 11:50:34 +00:00
<property name="label" translatable="yes">Extension Updates Ready</property>
extensions-app: Use `.heading` class for headings Don't hardcode headings styling. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1997>
2021-10-04 13:22:09 +00:00
<style>
<class name="heading"/>
</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 14:20:04 +00:00
</object>
</child>
<child>
<object class="GtkLabel" id="updatesLabel">
<property name="halign">start</property>
</object>
</child>
</object>
</child>
Port extensions app and portal to GTK4 With the previous preparations in place, it is time to take the plunge. As both the app and the portal use the same small library for handling external windows, port everything at once to avoid the hassle of building and installing two versions of the library. With the portal using GTK4 now, all extensions must port their preference widgets as well. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
<child type="end">
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 14:20:04 +00:00
<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 19:43:59 +00:00
<property name="label" translatable="yes">Log Out…</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 14:20:04 +00:00
<property name="valign">center</property>
<property name="action-name">win.logout</property>
extensions-app: Use consistent style for property names GtkBuilder understands both dashes and underscores in property names, and we currently use a mix of both. The actual properties use dashes, so settle on that. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1495>
2020-04-15 18:27:15 +00:00
<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-30 01:48:18 +00: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 14:20:04 +00: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-30 01:48:18 +00:00
</style>
</object>
</child>
</object>
</child>
</object>
</child>
</template>
</interface>
Reference in New Issue Copy Permalink