I finally got around to do some work on GuARD, but I didn’t feel like debugging or writing documentation. For quite some time e16 annoyed me because it lacks configurability and several key features. Because of this I used wbar, since e16 didn’t bring its own app launcher. This is just one of the more obvious downsides.
I finally decided to upgrade to e17, which I use at my desktop for several years now. At first I was unsure if e17 would meet GuARD’s need for lightweight applications. It turns out that the memory usage is only a few MB higher than with e16, that was a nice surprise. As I am running GuARD mostly in a virtual machine, I could tweak the processing power as well. I gave it only one of my four cores and set the maximum usage to 50%. My host system is set up to run at 1200MHz unless the usage of the specific core rises above 60%. Since this will never be the case I gave GuARD effectively a 600MHz cpu. It still ran smoothly.
This encouraged me to remove wbar and use e17’s internal modules to get the job done. Namely using engage, which features a taskbar as well, a thing that was missing so far. Unfortunately I still didn’t find a way to display mounted filesystems in a more userfriendly way (allowing unmounting/ejecting). Still it is much easier and cleaner to configure things now, plus it looks better
Here are two before—after screenshots (click to enlarge):