brl/gnome-shell
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
gnome-shell/subprojects/extensions-tool/src/gnome-extensions-tool.gresource.xml

16 lines
614 B
XML
Raw Normal View History

extensions-tool: Implement create command This implements more functionality of the existing tool and, as 'reload' is an unreliable feature that doesn't work more often than not, the last bit that we will replicate. The command follows the original for the most part, with the most important difference being the installed template, which doesn't provide any sample functionality and uses modern JS syntax. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1234
2018-08-27 03:24:10 +02:00
<?xml version="1.0" encoding="UTF-8"?>
<gresources>
<gresource prefix="/org/gnome/extensions-tool">
extensions-tool: Add template metadata When we allow users to choose between different templates, we should provide some context for each template to facilitate that choice. Add that metadata in the form of a .desktop file, which allows us to specify name and description, and is well supported by our translation infrastructure. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/812
2019-11-09 00:20:08 +01:00
<file>templates/00-plain.desktop</file>
extensions-tool: Add small indicator template Adding an additional icon to the top bar is one of the more common patterns used by extensions. Make this easier by providing a template for it. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/812
2019-11-06 10:44:28 +01:00
<file>templates/indicator.desktop</file>
<file>templates/indicator/extension.js</file>
<file>templates/indicator/stylesheet.css</file>
extensions-tool: Prepare for alternative templates The template used when creating a new extension is intentionally minimal, as the sample code in the old extensions-tool proved to be annoying more often than not. However as we support per-command options, we don't have to limit ourselves to a single template, and can offer alternatives for common use cases. To prepare for that, namespace the existing template by moving it into a subfolder. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/812
2019-11-06 10:06:11 +01:00
<file>templates/plain/extension.js</file>
<file>templates/plain/stylesheet.css</file>
extensions-tool/create: Optionally include prefs We currently only create boilerplate code for the actual extension. Now that libadwaita has largely standardized preference UIs, it makes sense to allow creating the prefs.js boilerplate as well. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2889>
2023-08-14 01:08:56 +02:00
<file>templates/prefs.js</file>
extensions-tool: Add quick settings template Extending quick settings has become popular enough to justify a template. Add a small indicator+quick-item example that exercises the previously added API. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2894>
2023-08-14 17:51:35 +02:00
<file>templates/quick-settings.desktop</file>
<file>templates/quick-settings/extension.js</file>
<file>templates/quick-settings/stylesheet.css</file>
extensions-tool: Implement create command This implements more functionality of the existing tool and, as 'reload' is an unreliable feature that doesn't work more often than not, the last bit that we will replicate. The command follows the original for the most part, with the most important difference being the installed template, which doesn't provide any sample functionality and uses modern JS syntax. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1234
2018-08-27 03:24:10 +02:00
</gresource>
</gresources>
Reference in New Issue Copy Permalink