gnome-shell/subprojects/extensions-app/js/org.gnome.Extensions.src.gresource.xml.in

<?xml version="1.0" encoding="UTF-8"?>
<gresources>
  <gresource prefix="/org/gnome/Extensions@profile@/js">
    <file>extensionManager.js</file>
    <file>extensionRow.js</file>
    <file>extensionsWindow.js</file>
    <file>main.js</file>

    <file>misc/config.js</file>
    <file>misc/extensionUtils.js</file>
  </gresource>
</gresources>
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: Support building a separate Devel app Follow the pattern used by most GNOME applications and add a profile build option that allows building a Devel app instead of the regular release. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3612 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1661> 2021-01-22 19:29:07 +01:00			`<gresource prefix="/org/gnome/Extensions@profile@/js">`
extensions-app: Split out ExtensionManager The extension handling is currently intertwined with the UI. Splitting it out provides a clearer separation, and will allow us to switch to a model-based UI later. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3067> 2023-12-18 20:20:26 +01:00			`<file>extensionManager.js</file>`
extensions-app: Move classes to their own files Using a single source file is getting unwieldy, so start splitting it up. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3067> 2023-12-19 15:14:19 +01:00			`<file>extensionRow.js</file>`
			`<file>extensionsWindow.js</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>main.js</file>`

			`<file>misc/config.js</file>`
			`<file>misc/extensionUtils.js</file>`
			`</gresource>`
			`</gresources>`