Replace ‘Activities’ button text with an icon https://extensions.gnome.org/extension/2338/overview-button/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
human.experience 7eb6568c5f update media with icon / workspace name view and new ego logo 5 months ago
docs initial commit, full extension at version 2 8 months ago
media update media with icon / workspace name view and new ego logo 5 months ago
sbin project structure: move extensions under src/ 8 months ago
src add workspace name feature 5 months ago
.editorconfig initial commit, full extension at version 2 8 months ago
.eslintrc.json initial commit, full extension at version 2 8 months ago
.gitignore project structure: move extensions under src/ 8 months ago
LICENSE initial commit, full extension at version 2 8 months ago
Makefile add workspace name feature 5 months ago
README.md debug: change from busctl to dbus-send 8 months ago

README.md

Overview Button

Replace ‘Activities’ button text with an icon

screenshot

Features

  • Replaces “Activities” text with an icon to save space

Requirements

Gnome Shell

  • 3.28
  • 3.30
  • 3.32
  • 3.34

Installation

Gnome Extensions Site: https://extensions.gnome.org/extension/2338/overview-button/

Usage

Click button same way you would click “Activities” label.

Debugging and Development

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\]" \
;

Development tool-chain

Most development tasks can be performed use included Makefile.

System prerequisites

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.

Makefile

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:

make develop

Now you can make the installed tooling available in your PATH by sourcing the generated activate.sh This will also prepend your terminals BASH prompt with project name for easier recognition.

Activate the development environment:

source activate.sh

Note: to restore your environment run:

overview_button_deactivate

To test extension in X use:

make x11

To test extension in Wayland use:

make wayland

To build the extension use:

make build

To build a distribution (zip archive) use:

make dist

Linting

Any code submission will need to be linted against standards in the repository. Project ESLint specifications are located in .eslintrc.json.

To lint code use:

make lint

References