lxqt-panel represents the taskbar of LXQt.

The elements available in lxqt-panel are called "plugin" technically. This applies e. g. to the source code where they reside in directories ./plugin-<plugin> like plugin-mainmenu. In contrast to this they are called "widgets" by the configuration GUI so far. Also, a more descriptive term is used to refer to distinct plugins within the GUI. E. g. the aforementioned plugin-mainmenu is called "Application menu" that way. Configuration dialogue "Add Plugins", see below, is listing all available plugins plus a short description and hence provides an overview of the available ones. Notes on some of the plugins, sorted by terms used within the GUI in alphabetical order, technical term in parenthesis:

Provides clock and calendar functionality and can display various time zones in addition.

A plugin to launch applications from the panel. By default it is empty and displays a message "Drop application icons here". Applications need to be available in panel's main menu and can be included into plugin-quicklaunch by drag & drop.

Status notifier plugin provides a notification area within the panel, that is an area where arbitrary applications can place informational icons. This is frequently used e. g. by chat or mail clients to inform about incoming messages or tools configuring the network to inform about connections. (So it's some kind of counterpart to the desktop notifications displayed by lxqt-notificationd). The difference between the two plugins is a technical one:

• plugin-tray is implementing the so-called System Tray Protocol. It's a specification that has been around for years but has some serious technical limitations and in particular won't work under Wayland. This plugin only translates "System Tray Protocol" entities into SNI ones, so it does not provide any visible area in panel.
• plugin-statusnotifier is implementing the so-called StatusNotifierItem (SNI) specification which can be considered a successor of the System Tray Protocol.

Both plugins are maintained in parallel as not all relevant applications are compatible with SNI so far. In particular both Qt 4 and all GTK applications need some kind of wrapper to deal with it. Both plugins can be used in parallel without any issue, applications supporting both specifications will normally chose to display their icons in plugin-statusnotifier.

As indicated by the name, a volume control. Technically Alsa, OSS and PulseAudio can be used as backend. The plugin itself is providing a control to adjust the main volume only but it allows for launching specific UIs of the backend in use like e. g. pavucontrol-qt to adjust PulseAudio.

The runtime dependencies are libxcomposite, libdbusmenu-lxqt, KGuiAddons, KWindowSystem, Solid, menu-cache, lxqt-menu-data, liblxqt and lxqt-globalkeys. Several plugins or features thereof are optional and need additional runtime dependencies. Namely these are (plugin / feature in parenthesis) Alsa library (Alsa support in plugin-volume), PulseAudio client library (PulseAudio support in plugin-volume), lm-sensors (plugin-sensors), libstatgrab (plugin-cpuload, plugin-networkmonitor), libsysstat (plugin-sysstat). All of them are enabled by default and have to be disabled by CMake variables as required, see below. In addition CMake and lxqt-build-tools are mandatory build dependencies. Git is optionally needed to pull latest VCS checkouts.

Code configuration is handled by CMake. CMake variable CMAKE_INSTALL_PREFIX has to be set to /usr on most operating systems, depending on the way library paths are dealt with on 64bit systems variables like CMAKE_INSTALL_LIBDIR may have to be set as well. By default all available plugins and features thereof are built and CMake fails when dependencies aren't met. Building particular plugins can be disabled by boolean CMake variables <plugin>_PLUGIN where the plugin is referred by its technical term like e. g. in SYSSTAT_PLUGIN. Alsa and PulseAudio support in plugin-volume can be disabled by boolean CMake variables VOLUME_USE_ALSA and VOLUME_USE_PULSEAUDIO.

To build run make, to install make install which accepts variable DESTDIR as usual.

Official binary packages are provided by all major Linux and BSD distributions. Just use your package manager to search for string lxqt-panel.

The panel is run as a daemon-like LXQt Module the launch of which can be adjusted in section "Basic Settings" of configuration dialogue LXQt Session Settings of lxqt-session.

To customize the panel itself there's a context menu, that is a menu opened by right-clicking the pointer device. It is comprising sections "<plugin>" and "Panel" which allow for configuring the plugin the pointer is currently over and the panel as a whole respectively.

In section "Panel" topics "Configure Panel" and "Manage Widgets" open different panes of a dialogue "Configure Panel" which allow for configuring the panel as a whole and the various plugins respectively. Pane "Widgets" allows for configuring and removing all plugins currently included in lxqt-panel. The plus sign opens another dialogue "Add plugins" which is used to add plugins. It comes with a list of all plugins plus some short descriptions and can hence serve as overview what plugins are available.

Sometimes right-clicking over particular plugins may bring up a context menu dealing with the respective plugin's functionality only which means the plugin in question cannot be configured the usual way. This affects e. g. plugin-quicklaunch as soon as items were added (the context menu is limited to topics dealing with the items included in plugin-quicklaunch). Currently there are two ways to deal with this. Some themes like e. g. Frost come with handles at the plugins' left end providing the regular context menu. Also, it can be assumed at least one plugin is included in the panel that's always featuring the regular context menu like e. g. plugin-mainmenu. Either way pane "Widgets" of "Configure Panel" can be accessed and used to configure the particular plugin.

Translations can be done in LXQt-Weblate