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

14 lines
388 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 11:44:27 -05: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 08:51:53 -05:00
<gresource prefix="/org/gnome/Extensions@profile@">
<file alias="style.css">css/style.css</file>
</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 11:44:27 -05: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 08:51:53 -05: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 13:26:06 -05: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 11:44:27 -05:00
<file>ui/extension-row.ui</file>
<file>ui/extensions-window.ui</file>
</gresource>
</gresources>
Reference in New Issue Copy Permalink