Desktop enviroment

@ wkp/desktop envs @ wkp / comparison of desktop envs.

desktop envs / community discussions

@ XFCE is building a new WM and compositor for Wayland

Devuan Desktop Enviroments

MATE

XFCE

wm :Openbox
panel :tint2
system monitor:conky
app menu:jgmenu

LXQt

@ wkp/LXQt @ lxqt-project.org

LXDE

@ wkp/LXDE

wm :Openbox
panel :tint2
system monitor:conky
app menu:jgmenu

KDE

Gnome

Desktop Envs NOT in Devuan

CAFE (fork of MATE)

usint CTK (fork of GTK3),

Bunsen

@ bunsenlab.org

wm :Openbox
panel :tint2
system monitor:conky
app menu:jgmenu

Desktop env / components

components / window manager

components / display manager

components / display server

components / windows

components / app menus

app menus / about

The current debian policy on its supported desktop menu systems @

In jwm and pekwm the main app menu seems to be filled only with a few of the installed apps

app menus / debian menu system

@refpage

pekwm in its static /etc/pekwm/config file includes a debian-menu that is a file generated and not packaged in the pekwm deb file.

app menus / jgmenu

@jgmenu

app menus / menumaker

@menumaker MenuMaker is a menu generation utility for X window managers on *NIX systems. It is capable of finding lots of installed programs and generating a root menu consistent across all supported X window managers, so one will get (almost) the same menu no matter which window manager is used.

app menus / examination of menu build in pekwm and jwm

/usr/share/menu/qutebrowser

?package(qutebrowser):needs="x11" section="Applications/Network/Web Browsing" \
        title="Qutebrowser" \
        longtitle="Qutebrowser Web Browser" \
        command="qutebrowser" \
        icon="/usr/share/pixmaps/qutebrowser.xpm"

Interstingly qutebrowser seem to follow a menu standard that no other programs follows. Thus a user of pekwm could be puzzled as to why only qutebrowser appears on the jwm and pekwm menu,