MX Fluxbox versus other Window Managers and Desktop Envioroments

[Jerry3904]

Been thinking about this some more, and have concluded that it would be more consistent for the next MXFB version to have the root menu's "All apps" open even more menus (which I was trying to avoid) than it would be to launch AppFinder, which is best suited for the dock.

Doesn't mean I like or will use it myself...

[jeffreyC]

Back about 10 years ago Linux Mint Fluxbox had a self updating menu mint-fm2, which was a rewrite in bash of marchfluxmenu which was in python 2.5.2+.

http://packages.linuxmint.com/pool/main/m/mint-fm2/

https://code.google.com/archive/p/marchfluxmenu/

[mowest]

Been thinking about this some more, and have concluded that it would be more consistent for the next MXFB version to have the root menu's "All apps" open even more menus (which I was trying to avoid) than it would be to launch AppFinder, which is best suited for the dock.

Doesn't mean I like or will use it myself...

Jerry, I agree with your thinking. I believe that fluxbox users from the past will appreciate the ability to get to all of their apps from the menu system. I also appreciate that MX-Fluxbox provides users with a few different options when it comes to launching their apps, but giving a full menu experience to users will be just another nice option. Some will prefer, some will prefer the XFCE4 Application Finder, and some will create idesk or dock launchers.

Personally, I like the functionality of clicking a key combination and typing in the name of the app to launch something. This is standard behavior in Gnome 3, XFCE Whisker menu, and Plasma too. I want to love FBrun, but its lack of "tab completion" or an updating visual list doesn't work for me because I don't always remember the name of the program exactly. I've been testing Rofi as a possible launcher to use in MX-Fluxbox for me. I don't know if it would be worth adding it to MX-Fluxbox because we have a similar tool with the XFCE Application Finder, but I'm testing it to see if it might be a nicer and more lightweight launcher for my use.

[Jerry3904]

Thanks. I agree that the problem is usually long time fb users, especially those coming from antiX. My goal from the beginning was to get 3 ways of dealing, and changing "All apps" to a menu of menus is consistent with that.

I use fbrun but it sure is limited, so am interested in finding an alternative.

[PPC]

@Jerry3984
There are many alternatives to fbrun, but some are not mainstream:
dmenu
j4dmenu (that uses .desktop files, allowing to search the apps description too) (https://github.com/enkore/j4-dmenu-desktop)
rofi (to use it as a basic app launcher: "rofi -show run", to use info from the .desktop files "rofi -modi drun -show drun" )
synapse (that I never used)
A combo of file/app searcher, that I use, low on resorces and fast - drill (https://github.com/yatima1460/Drill)

by far, the fastest is dmenu/j4dmenu- but it has an unusual interface. I use j4demu on my menu too- with a less "different" interface, and also showing the last run apps first:
[exec] (Search Apps) { ~/Downloads/j4-dmenu-desktop.sh --dmenu="dmenu -i -fn ubuntu -b -l 10" --usage-log=j4log.txt}

[Jerry3904]

I snooped around, and am now testing rofi. Very helpful entry (as always) in the Arch Wiki.

[figueroa]

Those wanting a lightweight XFCE replacement that behaves well with no fuss or muss, install LXDE from MXPI. LXDE is what I'm running on my MX-19 installation because the new XFCE does not hanle transparency in an x2go remote session. LXDE worked for me out-of-the-box with NO customizing except for having to install lxpolkit (required for root permissions on menu items) and obconf (provides an gui for configuration of OpenBox configuration items) . LXDE runs on top of OpenBox, so installing LXDE also gives you the option of running just the OpenBox WM without LXDE, which I don't like or use. lxpolkit and obconf were to be added to the MXPI package, but I just did a fresh trial install and they have not yet been added, so if you do install LXDE, be sure to install those also. Maybe if I had installed ALL the pending updates I would have found LXDE providing lxpolkit and obconf, but just in case, keep an eye out for them.

LXDE uses roughly 300-320Mi (free -h) in a local session not running any applications other than a terminal.

I have also installed these additional packages just to have the additional tools: gtk2-engines, gnome-disk-utility, gnome-system-tools, gucharmap, usermode, lxhotkey-plugin-openbox, lxhotkey-data, obconf, and task-lxde-desktop (this last one adds desktop-base, fonts-quicksand, task-desktop, task-lxde-desktop, tasksel, tasksel-data).

Confession: I am a long-time (10 or more years) LXDE user and fanboy. My views are jaded. Your mileage may vary, but I don't think LXDE will shoot you in the foot.

[mowest]

I snooped around, and am now testing rofi. Very helpful entry (as always) in the Arch Wiki.

I think rofi offers the functionality that you are looking for, and the ability to theme it in a way that fits nicely with the current theming and future default theming of MX-Fluxbox.

[clicktician]

How do you guys get apps started with gksu et. al. to work when you're not using XFCE.

I often use Openbox that you get for free if you just install LXDE. But like Dolphin says, not everything in XFCE works. Is there a compatibility trick, or do you just have to wing some alternative stuff?

[dolphin_oracle]

we don't use gksu

that said, look in the fluxbox ~/.fluxbox/startup file and you'll see an entry for the gnome policy kit authenticator. that's what we use.