|human.experience 7eb6568c5f||5 months ago|
|docs||8 months ago|
|media||5 months ago|
|sbin||8 months ago|
|src||5 months ago|
|.editorconfig||8 months ago|
|.eslintrc.json||8 months ago|
|.gitignore||8 months ago|
|LICENSE||8 months ago|
|Makefile||5 months ago|
|README.md||8 months ago|
Replace ‘Activities’ button text with an icon
Gnome Extensions Site: https://extensions.gnome.org/extension/2338/overview-button/
Click button same way you would click “Activities” label.
If you encounter a problem you can enable the debug logs with:
dbus-send \ --session \ --type=method_call \ --dest=org.gnome.Shell \ /org/gnome/Shell \ org.gnome.Shell.Eval string:" window.overviewButton.debug = true; " \ ;
Then tail the logs using:
journalctl \ /usr/bin/gnome-shell \ --follow \ --output=cat \ | grep "\[overview-button\]" \ ;
Most development tasks can be performed use included Makefile.
Development can be done using nested Xorg Xephyr session + gnome-shell or directly forked off gnome-shell in Wayland.
Xephyr is available in most distributions, please use your package manager to install it.
Additionally NodeJS >= 11.x are used during development. Make sure it is installed as well using your package manager and available in the PATH.
A handy Makefile bootstrap capable of handling most development, once above system prerequisites are installed. It’s strongly suggested you use the Makefile as it sets up a sandboxed Gnome Shell Extension development environment.
Set up development tooling using:
Now you can make the installed tooling available in your PATH by sourcing
activate.sh This will also prepend your terminals BASH
prompt with project name for easier recognition.
Activate the development environment:
Note: to restore your environment run:
To test extension in X use:
To test extension in Wayland use:
To build the extension use:
To build a distribution (zip archive) use:
Any code submission will need to be linted against standards in the repository.
Project ESLint specifications are located in
To lint code use: