In the Part 8 of the FreeBSD Desktop series I would like to describe key components of self made custom desktop environment such as:
- Window Manager
- Status Bar
- Task Bar
- Wallpaper Handling
- Application Launcher
- Keyboard/Mouse Shortcuts
- Locking Solution
- Blue Light Spectrum Suppress
Today we will focus on the fifth part – the Application Launcher. In the next series each of these components configuration would also be described along with eventual needed scripts.
You may also check earlier/other articles of the FreeBSD Desktop series:
- FreeBSD Desktop – Part 1 – Simplified Boot
- FreeBSD Desktop – Part 2 – Install (FreeBSD 11)
- FreeBSD Desktop – Part 2.1 – Install FreeBSD 12
- FreeBSD Desktop – Part 3 – X11 Window System
- FreeBSD Desktop – Part 4 – Key Components – Window Manager
- FreeBSD Desktop – Part 5 – Key Components – Status Bar
- FreeBSD Desktop – Part 6 – Key Components – Task Bar
- FreeBSD Desktop – Part 7 – Key Components – Wallpaper Handling
- FreeBSD Desktop – Part 8 – Key Components – Application Launcher
- FreeBSD Desktop – Part 9 – Key Components – Keyboard/Mouse Shortcuts
- FreeBSD Desktop – Part 10 – Key Components – Locking Solution
- FreeBSD Desktop – Part 11 – Key Components – Blue Light Spectrum Suppress
- FreeBSD Desktop – Part 12 – Configuration – Openbox
- FreeBSD Desktop – Part 13 – Configuration – Dzen2
- FreeBSD Desktop – Part 14 – Configuration – Tint2
- FreeBSD Desktop – Part 15 – Configuration – Fonts & Frameworks
- FreeBSD Desktop – Part 16 – Configuration – Pause Any Application
- FreeBSD Desktop – Part 17 – Automount Removable Media
While not being any crucial role of the desktop environment it have its uses and sometimes save time. As its not hard to add this ‘feature’ to our setup I will evaluate two light and fast solutions that fulfill that role:
Lets start with resources, the Rofi implementation of application launcher uses almost 3 times more RAM – 21 MB – then Dmenu solution – 8 MB.
PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 16952 vermaden 1 24 0 13860K 8968K select 0 0:00 1.76% dmenu 86078 vermaden 3 24 0 32980K 21712K select 0 0:00 2.54% rofi
The Dmenu is also faster while Rofi have more eye candy and colors.
As Dmenu suits better to this ‘minimalist’ yet functional desktop I will use it instead of Rofi, but feel free to experiment between them and choose best option for You.
This Dmenu setup – after being run – will cover the Dzen2 status bar with filtered commands fitting nicely into the setup, here is how it looks in action.
Desktop without Dmenu launched.
Desktop with Dmenu launched and with
alc characters inserted to ‘filter’ commands in the search of a calculator application.
While Dmenu is doing a good job here lets have a look how Rofi behaves in that role.
While I use a custom script for Dmenu – which I will present later in the series – the Rofi requires more simple command.
% rofi -show run -theme solarized_alternate -font "Monaco 8"
Here is how Rofi looks in action.
For the record, I also entered same
alc characters into Rofi to ‘filter’ commands in the search of a calculator application.
While Dmenu has very narrow ‘specialization’ the Rofi can also be used in other scenarios which are described on the project site.