supershadoe/gnome-shell-extension-reboot-menu

GNOME extension to show systemd-boot entries to quickly reboot

Hi there 👋

I create stuff with clean and maintainable code, a good looking UI with decent UX (aesthetics are very important imo) and a short but unique and powerful list of features.

Check this list for stuff I have made a contribution to in the past.

Check out the pinned repos on my profile for stuff I have worked on.

gnome-shell-extension-reboot-menu's Issues

Use CSS to hide restartItem

• Use CSS to hide restartItem instead of destroying it on _enable() and reconstructing it on
  _disable().

For approval in GNOME extensions

Better UI/UX

The current extension is just a botched-up version of the shell script I made when I used to use
XFCE and uses Zenity as I couldn't be bothered to learn how to make an XFCE plugin and also XFCE's
whisker menu allows you to execute any executable for any of the listed system actions.

Currently, there are few problems with this botched up implementation.

• Firstly, the zenity window is a popup and not a system dialog. So, it doesn't block the entire shell area and show this reboot prompt.
• Secondly, we are blindly executing the reboot-menu.sh script asynchronously without considering the fact that we are having another window open. So, multiple reboot menus can be opened.
• Then there's the issue of zenity window not looking as nicely as other gnome stuff (and less touch-friendly, etc.)
• Also, we are executing another shell script which calls a bunch of executables(like sed, xargs, etc.) which can probably reduced by actual code.

Proposed implementation:

• A menu in the aggregate menu which contains all the names of the boot entries.
• On clicking on the entry, the should somehow set oneshot boot entry and then execute activateRestart() from original gnome-shell code.
  (OR)
• On clicking on the entry, the extension should show a custom system dialog which executes systemctl reboot --boot-loader-entry=

Boot entries not updating on refresh

When "Reload list of boot entries" is clicked, it is expected that created and modified boot entries will appear and deleted boot entries would disappear but that isn't the case here.

Investigation is required to know why.