One of the features which I have posted about recently, is the Plasma 5 add-on called ‘Latte-Dock’. Specifically I wrote, How the user can install version 0.6.0 of this add-on, if it isn’t in the package repositories. What I had also written was, that a safe practice in using Latte-Dock would be, to keep the default Plasma 5 application-launcher in his panel, as a back-up, so that he will always have an application-launcher to click on, even if Latte-Dock crashes.
Well since then I have learned that a more avant-garde way exists to use Latte-Dock, which is, to place the default application-launcher onto the dock as well. This can easily be done because the default application launcher is a widget like any other, which can be dragged to this dock. As an additional detail, a method exists to get v0.6.0 of Latte-Dock to open the application launcher, by just pressing the Super Key, assuming that it has been added to the dock. The instructions I’ve just linked to do not count for later versions of Latte-Dock because those versions already have a check-box in their GUI, which does the same thing.
Hence, I’ve decided to be more progressive in my test-setup for Latte-Dock, and have also placed my only application-launcher onto this dock:
There is one detail which the reader should note however. I have kept one quick-launcher in the upper-left-hand corner of the screen, in the Plasma panel: The launcher that restarts Latte-Dock from the GUI with one click. The reason I have kept this safeguard is the observation that Latte-Dock can still crash from time to time, which means that the user would be without an application launcher, until he or she gets to restart the dock.
But this way, the layout of that desktop is even more different from the Windows-like layout – common to Plasma 5 and KDE 4 – than it only was a few days ago.
(Update 3/21/2021, 20h25: )
By now, ‘latte dock’
no longer works on the computer I name ‘Phosphene’. But I also think I know why. What latte-dock now does, when launched, is, to run apparently without error messages, but, not to display on the desktop.
In the meantime, what I have done is, to install two parallel desktop-managers, one of those still being ‘Plasma 5′, and the other being ‘LXDE’, because I have practical use for LXDE. When this is successful under Debian, it leads to a log-in screen, from which a user sitting in front of the computer can decide which Desktop Environment he or she would like to log in with. From there, in principle, it should still be possible to use latte-dock as the launcher, if the user logged-in to a Plasma 5 session.
However, in order to get this to work, I also needed to install more than one display manager, and then to reconfigure my display managers (globally – ‘above all sessions’). Previously, I had ‘sddm’ as my display manager. But presently, Phosphene’s active display manager is ‘lightdm’.
(Update 3/26/2021, 0h45: )
After much time and contemplation, I was able to get Latte Dock to work again!
Apparently, what had first caused the app to stop working, was the mere need to be recompiled, against updated libraries. However, I had forgotten to heed advice which I had given myself, on my own blog, about how to do so. The short-term result of that was, that parts of Latte Dock were installed to ‘/usr/share’, while other parts of it were installed to ‘/usr/local/share’. Apparently, when a QML script loads a module, it will search in both locations for the folder-names, that identify the module. And then, If, in an inconsistent fashion, the meta-data in one of the folders does not load properly, the QML Script which tried to import that, will itself fail to load…
I now have it sorted out, and Latte Dock, v0.6.0, works again, on my Debian 9 / Stretch computer, which only has Plasma 5.8 and Qt Libraries 5.7.1 .
(Screen-Shot Added 3/26/2021, 11h10: )