Poll: Should the Whisker Menu Be Changed? (Aesthetics)

Should the Whisker Menu Be Changed to look more appealing?

  • Yes, I think it should be changed.
  • No, I prefer it as it is.
  • I have no strong opinion either way.
  • I have suggestions for improvements or know a Xfce theme. (Please comment below.)
  • A different Desktop Environment should replace Xfce (Please comment below.)
0 voters

I think KDE should replace XFCE.
However I would like to know the comparison of known CVE’s history for each desktop environment.

Due to plans to port to Wayland - Development - Whonix Forum, resource constraints for running inside virtual machines, preferences of security and minimalism, choices are limited. At this time, LXQt seems the most likely next thing.

GNOME is highly unlikely. See:

Related:

History: We actually moved from KDE to Xfce. See: User Poll - XFCE vs KDE - KDE Deprecation Considered! - News - Whonix Forum

1 Like

I like minimalism and less code = less possibilities for vulnerabilities. So, I did - apt remove xfce4-whiskermenu-plugin - and I use xfce panel’s built-in applications menu or app-launcher. It is absolutely enough for me. :sunglasses: Thus I don’t need Whisker Menu at all.

1 Like

two suggestions for improvements related to this thread.

Kicksecure logo replacing the whisker menu icon. Same for Whonix workstation since they both use Xfce. Would be aesthetically pleasing and nice distro branding to the panel.

Keyboard shortcut easy application exploring like other desktops have but for the whisker menu


Examples

GNOME (Ubuntu, Fedora, etc.) → Super = Activities Overview
Linux Mint → Super = Start menu style panel

Just like @init38 suggested in another thread

Almost, yes, but…
Not whisker menu, because that’s a Xfce thing.

Kicksecure 18 will be based on LXQt. Rationale here:

The start menu icon will be the Kicksecure icon logo. (Kicksecure ™ Unified Design - Logos & Guidelines)

In short, Kicksecure LXQt start menu icon will be styled as Kicksecure icon logo.

This has already been implemented thanks to @arraybolt3.

1 Like