MX-23 Fluxbox development
Re: MX-23 Fluxbox development
@i_ri I've just moved a revision of what you have submitted to GitHub where we will pursue development. Thanks for your ideas.
Production: MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: MX-23 Fluxbox development
Hello
mx-idesktool
Open the Icon Chooser to the session icon theme directory.
Add SESSICONTHEMED (no care about remembering what it is if the task is to change icon. Remembering the icon is best when making changes other than icon. leave it the way it is. or You want Papirus, we did icondir; SESSICONTHEMED can be icondir.) it bounces again icondir to gtk-icon-theme-name(?)
help; okay? does this open to your icon-theme directory?
around line 500 in function geticon
less force
set this for icondir, around line 125, and leave filename as iconplaceholder.
mx-idesktool
Open the Icon Chooser to the session icon theme directory.
Add SESSICONTHEMED (no care about remembering what it is if the task is to change icon. Remembering the icon is best when making changes other than icon. leave it the way it is. or You want Papirus, we did icondir; SESSICONTHEMED can be icondir.) it bounces again icondir to gtk-icon-theme-name(?)
help; okay? does this open to your icon-theme directory?
around line 500 in function geticon
Code: Select all
cd "${iconplaceholder%/*}"
if grep -q icon-theme $HOME/.gtkrc-2.0; then
SESSICONTHEME=$(gawk -F'"' '/^gtk-icon-theme/ {print $2}' $HOME/.gtkrc-2.0)
SESSICONTHEMED=/usr/share/icons/${SESSICONTHEME}
fi
icon="$($DIALOG --title="Commands" \
--width=600 --height=500 --center \
--button="$TEXT7":3 --button="$TEXT8":1 \
--button="$TEXT9":0 --title "$TEXT23" \
--text="$TEXT19": \
--file-selection="${iconplaceholder}" \
--file-filter="png, svg | *.png *.PNG *.svg *.xpm" \
--filename="${SESSICONTHEMED}")"
set this for icondir, around line 125, and leave filename as iconplaceholder.
Code: Select all
icondir=/usr/share/icons/Papirus/48x48/categories/
if grep -q icon-theme $HOME/.gtkrc-2.0; then
SESSICONTHEME=$(gawk -F'"' '/^gtk-icon-theme/ {print $2}' $HOME/.gtkrc-2.0)
#set this icon directory available
icondir=/usr/share/icons/${SESSICONTHEME}
fi
Re: MX-23 Fluxbox development
FOR LATER
What @siamhie wrote about mouse cursor in the b1 feedback thread is what I have found out too. We would want to modify it to include ~/.icons/. The first 17 lines (up to the gsettings command) of this script I found would seem to get us started:
What @siamhie wrote about mouse cursor in the b1 feedback thread is what I have found out too.
It seems to me it would be possible to create a small yad front end for the terminal codefirst run "sudo update-alternatives --config x-cursor-theme" and select a theme.
I then edit ~/.config/gtk-3.0/settings.ini and change the gtk-cursor-theme-name entry to match the x-cursor-theme selection.
Code: Select all
jb@mx:~$ sudo update-alternatives --config x-cursor-theme
[sudo] password for jb:
There are 3 choices for the alternative x-cursor-theme (providing /usr/share/icons/default/index.theme).
Selection Path Priority Status
------------------------------------------------------------
0 /usr/share/icons/Adwaita/cursor.theme 90 auto mode
1 /usr/share/icons/Adwaita/cursor.theme 90 manual mode
* 2 /usr/share/icons/DMZ-Black/cursor.theme 30 manual mode
3 /usr/share/icons/DMZ-White/cursor.theme 50 manual mode
Press <enter> to keep the current choice[*], or type selection number:
Code: Select all
#!/usr/bin/env bash
fifo="/tmp/themes_script.fifo"
mkfifo "$fifo"
declare -a themes
find /usr/share/icons -maxdepth 2 -type d -name "cursors" -printf "%P\n" > "$fifo" &
find ~/.icons -maxdepth 2 -type d -name "cursors" -printf "%P\n" >> "$fifo" &
while IFS= read -r line
do
themes+=("${line%/*}")
done < "$fifo"
rm "$fifo"
echo ">>> Please enter the number of new theme for cursor"
select opt in "${themes[@]}"
do
if [ $REPLY -le ${#themes} ]
then
gsettings set org.gnome.desktop.interface cursor-theme \'$opt\' &&
exit 0
else
echo "Improper argument" > /dev/stderr
exit 1
fi
done
Production: MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
POST MX-23 RELEASE
POST MX-23 RELEASE
I want to keep this going so I don't lose stuff.
I want to keep this going so I don't lose stuff.
Production: MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: MX-23 Fluxbox development
I had a comment on my intro video that got me thinking:
--a desktop file with title maybe "Default shortcuts"
--some attractive, user-friendly document of the keys file contents
--an icon (key ring, bunch of keys?)
If others like the idea, let's start a dedicated thread.
I answered with this:IMHO best have a launcher on the panel to a pic/ image or even text file with the fluxkey combinations.
That seems to me like a good idea ATM, we'd needWe don't put lots of launchers on the panel by default. There is already a conky available and the keys (text) file itself, but your comment makes me think about adding an icon to the Settings Manager.
--a desktop file with title maybe "Default shortcuts"
--some attractive, user-friendly document of the keys file contents
--an icon (key ring, bunch of keys?)
If others like the idea, let's start a dedicated thread.
Production: MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: MX-23 Fluxbox development
May be something is missing here:
Booted with Japanese locale, which indicates root-menu is not usable: Perhaps only a font issue?
Also Catalan (ca_ES) may need some considerations:
Booted with Japanese locale, which indicates root-menu is not usable: Perhaps only a font issue?
Also Catalan (ca_ES) may need some considerations:
You do not have the required permissions to view the files attached to this post.
Re: MX-23 Fluxbox development
@user-green would you be able to confirm fehlix's finding, maybe in a Live session if you don't have Fluxbox installed? You will need to right-click the desktop to see the menu he is talking about.
I will look into the Catalan question--I have my sources...
I will look into the Catalan question--I have my sources...
Production: MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
- user-green
- Posts: 326
- Joined: Sat Mar 14, 2020 1:40 am
Re: MX-23 Fluxbox development
Hello, Jerry3904
I tested MX-23_fluxbox_x64.iso as LiveUSB.
This issue is something to do with "Override option" in font settings. It will be fixed by checking all of them as attached below:
I tested MX-23_fluxbox_x64.iso as LiveUSB.
This issue is something to do with "Override option" in font settings. It will be fixed by checking all of them as attached below:
You do not have the required permissions to view the files attached to this post.
Re: MX-23 Fluxbox development
@user-green Very helpful, many thanks!
Production: MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: MX-23 Fluxbox development
Hi, everyone!
I'm still around, and I do drop by to check the forum now and then. The reason I've not been posting is because my last machine that ran MX died on me long ago, and I decided to center my efforts in making antiX (that I used on all my computers, even dual booting it with MX, on my old work desktop pc) easier to use.
I do like the way the latest MXFB looks and feels - I love particularly the Rofi menu, how efficient it is, how customizable it is- it's almost, almost perfect... except one detail - if using the categories menu, the fact that the menu disappears and comes back showing the category (at least on the virtualized version that I tested) breaks a tiny bit the "illusion" the user is using a real "system menu"- that's probably the single "flaw" I noticed.
I do like the fact that the default tint2 toolbar (like I recommended, long ago) displays previews of running windows.
I still recommend that the default fluxbox toolbar should include, at least, a "menu" button. like currently antiX does with it's default fluxbox implementation (it shows a Menu and a "show desktop" toolbar entry). I would go as far recommending using a font with default symbols, and use it to display generic "File Manager" and "Web browser" quick launcher "glyphs" on Fluxbox toolbar.
Since I'm not currently a MXFB user, I have no right to "complain", but the tint2 simpledock configuration (maybe adapted from the model I proposed in the past?) does use a lot less resources than the default MXFB toolbar (that uses more RAM for each new icon). I recall having proposed a yad GUI to add/remove quick launch icons to tint2 files- It would be a major change, swapping the default "dock", but I do think it would mean that the end product would be lighter and no features would be lost.
I do like the fact that MXFB and antiX Fluxbox (with the FT10 package installed and enabled) do look very similar (since I started developing FT10 when I was helping out with MXFB's tint2 adoption).
Extremely nice OS (and my back-up, in case I ever have to stop using antiX for some reason).
P.
I'm still around, and I do drop by to check the forum now and then. The reason I've not been posting is because my last machine that ran MX died on me long ago, and I decided to center my efforts in making antiX (that I used on all my computers, even dual booting it with MX, on my old work desktop pc) easier to use.
I do like the way the latest MXFB looks and feels - I love particularly the Rofi menu, how efficient it is, how customizable it is- it's almost, almost perfect... except one detail - if using the categories menu, the fact that the menu disappears and comes back showing the category (at least on the virtualized version that I tested) breaks a tiny bit the "illusion" the user is using a real "system menu"- that's probably the single "flaw" I noticed.
I do like the fact that the default tint2 toolbar (like I recommended, long ago) displays previews of running windows.
I still recommend that the default fluxbox toolbar should include, at least, a "menu" button. like currently antiX does with it's default fluxbox implementation (it shows a Menu and a "show desktop" toolbar entry). I would go as far recommending using a font with default symbols, and use it to display generic "File Manager" and "Web browser" quick launcher "glyphs" on Fluxbox toolbar.
Since I'm not currently a MXFB user, I have no right to "complain", but the tint2 simpledock configuration (maybe adapted from the model I proposed in the past?) does use a lot less resources than the default MXFB toolbar (that uses more RAM for each new icon). I recall having proposed a yad GUI to add/remove quick launch icons to tint2 files- It would be a major change, swapping the default "dock", but I do think it would mean that the end product would be lighter and no features would be lost.
I do like the fact that MXFB and antiX Fluxbox (with the FT10 package installed and enabled) do look very similar (since I started developing FT10 when I was helping out with MXFB's tint2 adoption).
Extremely nice OS (and my back-up, in case I ever have to stop using antiX for some reason).
P.