MX Fluxbox Screenshots

[Jerry3904]

What exactly is the object in the upper right corner?

[Amiga-MX]

In the very very right top, there is an artefact caused by 2nd monitor when screenshot near conky, if is that what you mean.

The panel below that artefact is a conky instance.


MXMLGO

[kobaian]

I hope this solution will end the eternal war between the House of Rofi and the House of Appfinder.












How does it work?

I have created three files in the ~/.config/tint2/scripts directory: tint2launcher, defaultlauncher and switchlauncher.
The first one - tint2launcher is a short bash script that replaces the command under the MX-Logo on the Tint2 panel:

Code: Select all

#!/bin/bash

tint2launch=$(cat ~/.config/tint2/scripts/defaultlauncher)

if [[ $tint2launch -eq 1 ]] ; then

rofi -show drun && exit 0

else

xfce4-appfinder & exit 0

fi

The second one - defaultlauncher - stores the variable that indicates the preferred application-launcher:

Code: Select all

1

The third one - switchlauncher - is the bash script that allows to switch between the two launchers:

Code: Select all

#!/bin/bash

tint2launch=$(cat ~/.config/tint2/scripts/defaultlauncher)
TITLE=$"Change your app-launcher"
MESSAGE1=$"Your current application-launcher is <b>Rofi</b>.
  Do you want to switch to <b>XFCE4-Appfinder</b>?"
MESSAGE2=$"Your current application-launcher is <b>XFCE4-Appfinder</b>.
  Do you want to switch to <b>Rofi?</b>"
BUTTON1=$"Yes"
BUTTON2=$"No"

if [[ $tint2launch -eq 1 ]] ; then

yad --title="$TITLE" --borders=18  --center --on-top --image=dialog-question-symbolic --skip-taskbar  --window-icon=dialog-question \
	--text="  $MESSAGE1" \
	--button="$BUTTON1!dialog-yes!:1" \
	--button="$BUTTON2!dialog-no!:0" \


else

yad --title="$TITLE" --borders=18  --center --on-top --image=dialog-question-symbolic --skip-taskbar --window-icon=dialog-question \
	--text="  $MESSAGE2" \
	--button="$BUTTON1!dialog-yes!:2" \
	--button="$BUTTON2!dialog-no!:0" \

fi

ret=$?

[[ $ret -eq 0 ]] && exit 0

if [[ $ret -eq 1 ]]; then
    sed -i 's/1/0/' ~/.config/tint2/scripts/defaultlauncher && exit 0

elif [[ $ret -eq 2 ]]; then
    sed -i 's/0/1/' ~/.config/tint2/scripts/defaultlauncher && exit 0
    
fi

And the last thing is to create the button that contains the following lines to execute the new commands:

Code: Select all

button_lclick_command = bash ~/.config/tint2/scripts/tint2launcher
button_rclick_command = bash ~/.config/tint2/scripts/switchlauncher

[Amiga-MX]

That's fantastic.

Just hope all the ecosystem to have some king of telestransporting module like the bridge you have extended. The utility is highly spicy. The environment is flavored.

I've heard good things about rofi at codely.tv. It seems rofi is making few mac developer returning to linux, just because the launch utility, among others.

I personally appreciate, what you made.

Just one last question. What about to have both, is there any inter-dependency between appfinder and rofi ?

Nowadays, and depending to my anime state y use both in several manner at a time. Usually appfinder at a time almost always opened on the bottom left column and rofi at the bottom right modulus. I wish to have a picture but rofi jumps off as soon I pressed print screen.

MX-FB is even more acrobatic now.

Thanks for your help.

[ceeslans]

I hope this solution will end the eternal war between the House of Rofi and the House of Appfinder.
...
How does it work?

I have created three files in the ~/.config/tint2/scripts directory: tint2launcher, defaultlauncher and switchlauncher.
The first one - tint2launcher is a short bash script that replaces the command under the MX-Logo on the Tint2 panel
The second one - defaultlauncher - stores the variable that indicates the preferred application-launcher
The third one - switchlauncher - is the bash script that allows to switch between the two launchers
...
And the last thing is to create the button that contains the following lines to execute the new commands:

Code: Select all

button_lclick_command = bash ~/.config/tint2/scripts/tint2launcher
button_rclick_command = bash ~/.config/tint2/scripts/switchlauncher

@kobaian that is absolutely lovely. Tried it out (of course adapting the necessary code to call 'jgmenu' instead of absent 'xfce4-appfinder' ) and it works a treat.
The nice thing is that the switch can be applied in any tint2rc theme. Will have to look how to accomodate calls for different rofi themes/config.rasi files (like e.g your iconic theme, which I guess is different for bottom- or top position?)
In any case: thanks for this clever solution!

[Jerry3904]

Wow, that looks great! Clever concept and coding. Haven't tried it yet b/c it's still early in the morning over here, but will later.

The larger question IMO is whether we need to supply both in the first place. I was sort of thinking, once we have tested the rofi-as-applauncher, that we would just have one. Appfinder could then always be installed via Package Installer (not currently possible), and the Debian menu is installed anyway by default with mxfb-accessories and would just need to be activated.

Have to think about that some more...

[Melber]

@kobaian very nicely done

[wdscharff]

I know that many roads lead to Rome and having a choice is also a good thing.
I can't even remember the last time I used fbrun or xfce4-appfinder.
Even my guests use either rofi or the root menu.
I probably wouldn't even notice if the appfinder and fbrun were gone.

When I switched from xfce to fluxbox, it was different for the first few months, but then it disappeared from my focus:)

[siamhie]

Nowadays, and depending to my anime state y use both in several manner at a time. Usually appfinder at a time almost always opened on the bottom left column and rofi at the bottom right modulus. I wish to have a picture but rofi jumps off as soon I pressed print screen.

I use gimp for that specific purpose. It has a screenshot utility built-in with a timed delay. (File>Create>Screenshot)

gimp.png

[Jerry3904]

I use Screenshot (xfce4-screenshoter) which is much faster and easier than going through Gimp for a delayed shot.