brl/gnome-shell
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
gnome-shell/subprojects/extensions-app/data/org.gnome.Extensions.data.gresource.xml.in

21 lines
811 B
XML
Raw Normal View History

extensionPrefs: Use imports.package.start() We want to make the extensions app code more self-contained to make it easier to build separately, and ultimately make it available on flathub. One complication we are facing is that it is currently all over the source tree: - js/extensionPrefs for the main code - src for the launcher process - data for .desktop file and icons Switching from a C launcher to the imports.package module allows us to consolidate the first two, and will also take care of the annoying setup bits (defining JS search path, extending GI lookup, loading resources). https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1081
2020-03-05 17:44:27 +01:00
<?xml version="1.0" encoding="UTF-8"?>
<gresources>
extensions-app: Use Adw.Application's automatic style loading Now that we switched to AdwApplication, we can automate loading the custom stylesheet by simply using the expected name and resource prefix. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1997>
2022-01-05 14:51:53 +01:00
<gresource prefix="/org/gnome/Extensions@profile@">
<file alias="style.css">css/style.css</file>
extensions-app: Add shortcuts window There aren't many shortcuts and all of them are standard, but documenting them is still good practice, and our main menu is a tad bit less empty. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3051>
2023-12-12 21:13:56 +01:00
extensions-app: Make kill switch more compact Instead of using a subtitle, move the stability warning into an information popover. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3051>
2023-12-11 00:34:31 +01:00
<file preprocess="xml-stripblanks">icons/scalable/actions/info-symbolic.svg</file>
extensions-app: Use details popover Showing all the extension info and possible actions in every row is fairly noisy, and doesn't match the usual list patterns. Streamline the UI by moving the actions and most of the info into a details popover, so the rows themselves get closer to the standard pattern. Closes https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7119 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3051>
2023-12-10 23:21:38 +01:00
<file preprocess="xml-stripblanks">icons/scalable/actions/remove-symbolic.svg</file>
<file preprocess="xml-stripblanks">icons/scalable/actions/settings-symbolic.svg</file>
<file preprocess="xml-stripblanks">icons/scalable/actions/website-symbolic.svg</file>
extensions-app: Make kill switch more compact Instead of using a subtitle, move the stability warning into an information popover. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3051>
2023-12-11 00:34:31 +01:00
extensions-app: Add shortcuts window There aren't many shortcuts and all of them are standard, but documenting them is still good practice, and our main menu is a tad bit less empty. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3051>
2023-12-12 21:13:56 +01:00
<file alias="gtk/help-overlay.ui">ui/help-overlay.ui</file>
extensions-app: Use Adw.Application's automatic style loading Now that we switched to AdwApplication, we can automate loading the custom stylesheet by simply using the expected name and resource prefix. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1997>
2022-01-05 14:51:53 +01:00
</gresource>
extensionPrefs: Use imports.package.start() We want to make the extensions app code more self-contained to make it easier to build separately, and ultimately make it available on flathub. One complication we are facing is that it is currently all over the source tree: - js/extensionPrefs for the main code - src for the launcher process - data for .desktop file and icons Switching from a C launcher to the imports.package module allows us to consolidate the first two, and will also take care of the annoying setup bits (defining JS search path, extending GI lookup, loading resources). https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1081
2020-03-05 17:44:27 +01:00
extensions-app: Use Adw.Application's automatic style loading Now that we switched to AdwApplication, we can automate loading the custom stylesheet by simply using the expected name and resource prefix. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1997>
2022-01-05 14:51:53 +01:00
<gresource prefix="/org/gnome/Extensions">
extensionPrefs: Load D-Bus interface from own resource Using the "regular" loadInterfaceXML() helper means less code duplication, but it also ties us to the resource used by gnome-shell. In order to untangle the extension app from core gnome-shell, change that to load the interface from the existing data resource instead. While that does involve reimplementing loadInterfaceXML(), it's not too bad actually with the resource-loading code stripped (as the data resource is already loaded by the package module). https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1081
2020-03-07 19:26:06 +01:00
<file>dbus-interfaces/org.gnome.Shell.Extensions.xml</file>
extensionPrefs: Use imports.package.start() We want to make the extensions app code more self-contained to make it easier to build separately, and ultimately make it available on flathub. One complication we are facing is that it is currently all over the source tree: - js/extensionPrefs for the main code - src for the launcher process - data for .desktop file and icons Switching from a C launcher to the imports.package module allows us to consolidate the first two, and will also take care of the annoying setup bits (defining JS search path, extending GI lookup, loading resources). https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1081
2020-03-05 17:44:27 +01:00
<file>ui/extension-row.ui</file>
<file>ui/extensions-window.ui</file>
</gresource>
</gresources>
Reference in New Issue Copy Permalink