MX Linux Forum

Posted: **Fri Jan 31, 2020 6:21 am**

After a lot of hard work by the MX Devs and Community members, MX-Fluxbox 2.0 is ready for beta testing. The list of contributors is too long for me to spell out this early in the morning, but I am very grateful for the fantastic support the project has enjoyed.

Installation
URL: https://drive.google.com/file/d/1bHjyyV ... sp=sharing

md5sum: 236376ce1cb34c7b028ce6a6506c7113 4712752 mx-fluxbox_20.0mx19+1.tar.xz

Once that has installed, then use the command line to move files into Home:

Code: Select all

/usr/bin/mxflux_install.sh

An existing fluxbox folder will be backed up to ~/.fluxbox_BAK

Features
There are some great new and revised features:

--Two major new tools: mx-idesktool and wmalauncher. Both are covered in MX-Fluxbox Documentation (= ~/.fluxbox/doc/mxfl-docs.pdf) which can be easily accessed by pressing F1 or clicking the icon in the left corner.

Revised and updated from a 2004 script and converted to a gui, mx-idesktool makes it easy to create and manage iDesk icons. And they now can be dragged anywhere on the desktop, something that had been broken up until now. wmalauncher is a relatively new (2018) command-line app with great power to create launchers in the fluxbox "slit" and many options that I have barely begun to explore.

--An optional legacy toolbar setup, along with a return, available with one click off the menu (Look > Toolbar > Legacy). This allows new users, especially those coming from a legacy OS, to switch easily to a format with which they may be more familiar (and "as God intended," a MX user once said).

--Pre-made docks available with a single click off the menu (Look > Docks and launchers). Also a very easy dock template that enables users to set up exactly what they want.

dock5.png

--Greatly expanded (11pp) documentation covering fluxbox, iDesk and wmalauncher.

Known Issues
--legacy toolbar consists of a large menu icon in the left corner adjoining the toolbar at 97% screen width coming from the right end. Depending on resolution there can be a slight gap or a slight overlap, adjusted by making the toolbar 1% longer or shorter. I wish I could eliminate that but don't see a way to *glue* them together.

--mx-updater tends to disappear now and then, and I can't figure out how to prevent that.

Testing suggestions
--MX-Fluxbox is now under a feature freeze, so this is therefore not the moment for suggestions about things to add. I have already received excellent ones, and there are many already in the MX-Fluxbox Tips & Tricks thread.

--Please take a close look at the two big tools as well as the documentation covering them.

--Check out the pre-made docks, and try to make one of your own if you have the time and interest to test directions and functionality.

Deadline: we have 5 days or so before we need to begin to pull together the final version.

Thanks in advance for help.

Posted: **Fri Jan 31, 2020 9:15 am**

One thing I noticed, when trying to run with sudo I got this:

Code: Select all

sudo /usr/bin/mxflux_install.sh
mv: cannot move '/root/.fluxbox' to '/root/.fluxbox_BAK/.fluxbox': Directory not empty

I think it's safer to use

Code: Select all

sudo -E /usr/bin/mxflux_install.sh

to preserve the environment, otherwise $HOME might be "/root/" (I guess depending on various settings)

Posted: **Fri Jan 31, 2020 10:01 am**

Do you even need to use sudo to run the mxflux_install.sh script? I ran it without and as far as I can tell it's working.

Posted: **Fri Jan 31, 2020 10:08 am**

I don't think so. everything copies into the home folder. so user is fine.

when the script is run from mx-pi, it uses

Code: Select all

sudo -H -u $(logname) /usr/bin/mxflux_install.sh

I don't thing the -E for sudo works anymore in mx19 unless I'm remembering incorrectly.

Posted: **Fri Jan 31, 2020 10:11 am**

Yes, I didn't even consider that, it's in user folder, I think everything should be owned by user, you should not even use sudo in the first place (should we?), Jerry, can you please edit the instructions?

Posted: **Fri Jan 31, 2020 10:13 am**

On the road to DC, but will do it. I first tried without and it failed.

Posted: **Fri Jan 31, 2020 10:15 am**

Is that what you wanted?

Posted: **Fri Jan 31, 2020 10:16 am**

in any case that mv function looks like it fails if the backup directory exists already. probably better to backup to something like

.fluxbox_bak_.$(date +%Y%m%H%M%S)

it might also be better to exit the script if the backup fails. because then there is no backup.

after the mv

Code: Select all


if [ ! "$?" = "0" ]; then
	echo $"backup cannot be made, exiting"
	exit 1
fi

Posted: **Fri Jan 31, 2020 10:53 am**

Sort of on the same topic, from what I can see the MX-flux / "Set up fluxbox" entry provided by the mxflux.desktop file (/usr/share/mxflux/.fluxbox/components/mxflux.desktop) doesn't appear anywhere in the menu. It does if I copy or symlink it to /usr/share/applications.

But even then it doesn't work with the 'Exec=sh /usr/local/bin/mxflux_install.sh' line (the mxflux_install.sh script is installed in the /usr/bin directory).
It works when I change the Exec line to just: 'Exec=mxflux_install.sh' .

Posted: **Fri Jan 31, 2020 11:21 am**

kmathern wrote: Fri Jan 31, 2020 10:53 am Sort of on the same topic, from what I can see the MX-flux / "Set up fluxbox" entry provided by the mxflux.desktop file (/usr/share/mxflux/.fluxbox/components/mxflux.desktop) doesn't appear anywhere in the menu. It does if I copy or symlink it to /usr/share/applications.

But even then it doesn't work with the 'Exec=sh /usr/local/bin/mxflux_install.sh' line (the mxflux_install.sh script is installed in the /usr/bin directory).
It works when I change the Exec line to just: 'Exec=mxflux_install.sh' .

good catch. I missed that a .desktop file was still present.

the actually working desktop entry was removed from the package, mostly because I got confused about what jerry was telling me.

the mx-pi install routine runs the script manually. the 19.1 iso will have mx-fluxbox pre-installed. so the desktop entry would just be for updates?

it can of course be added back if folks think its necessary.

Posted: **Fri Jan 31, 2020 11:33 am**

Instead of cluttering the Home folder with fluxbox backups, why not put them into the folder existing restore-fluxbox? Would only mean a couple of changes.

Man it's a drag to type on a phone going down the highway...

Posted: **Fri Jan 31, 2020 11:35 am**

Jerry3904 wrote: Fri Jan 31, 2020 11:33 am Instead of cluttering the Home folder with fluxbox backups, why not put them into the folder existing restore-fluxbox? Would only mean a couple of changes.

Man it's a drag to type on a phone going down the highway...

don't type while driving! we aren't quite done solving the "bus" problem yet

putting in a sep. restore folder makes sense.

Posted: **Fri Jan 31, 2020 11:38 am**

Wife is driving... but the bumps!

Posted: **Fri Jan 31, 2020 12:13 pm**

We could clean it up even more by using the restore folder. Then all I would need to change would be
.restore-fluxbox
to
.restore/fluxbox

Posted: **Fri Jan 31, 2020 1:23 pm**

Installation by the method described was quick and easy.

Using and modifying the Dock was straightforward. When creating my own Dock, the Launcher directions describe the save location as $HOME/fluxbox/script, but it should be $HOME/fluxbox/scripts.

Chris

Posted: **Fri Jan 31, 2020 3:01 pm**

Thanks. Typo noted.

Posted: **Sat Feb 01, 2020 7:05 am**

I wonder if we can or should change the login box to include a "Session" button so that it will be easier for users to find fluxbox? I like what we have had for a while, but it is so subtle that I bet we will see users, especially new users, asking how they get there. Going to look for some images...

Posted: **Sat Feb 01, 2020 7:23 am**

hi jerry

right clicking on the panel does not bring up any of the toolbar placement and size options for me

i have to go through the menu ... settings / toolbars / placement

Posted: **Sat Feb 01, 2020 7:29 am**

@junoluna: yup, that change happened a few weeks ago, likely IMO with the upgraded fluxbox. As I mention in the documentation--maybe not with enough emphasis--you can center-click (scroll wheel) over the pager (and maybe an empty toolbar) and that works.

Posted: **Sat Feb 01, 2020 7:30 am**

Back to my login issue: one easy way to make it more visible is to move the session icon to the center of the top bar so it sits by itself. Looks much better to me already.

Maybe changing themes might make it even more visible, off to fool around...

Posted: **Sat Feb 01, 2020 7:43 am**

thanks

center click works fine

Posted: **Sat Feb 01, 2020 4:43 pm**

So I can get some eyes on this revised code, here in the mxflux_install script with 1) backups placed now inside .restore/fluxbox/, 2) all backups dated per DO's code, 3) new backups of iDesk components if .idesktop is present.

I did not include DO's error message if the backup of existing fluxbox fails because I hope to avoid having to back through the translation process--but will if people really think it's necessary. Likewise I changed only the location URL inside MESSAGE, thinking that it could be done as a batch sed inside the existing translations folder, along with a change in the one translation that has since been made.

Code: Select all

#!/bin/bash

#mx-fluxbox-install

##ASSUMPTIONS##
#1) that fluxbox and idesk have been installed
#2) that this script has been placed in /usr/bin/mxflux/
#3) that the tarball from https://github.com/jerry3904/mx-fluxbox has been extracted and placed in 
#/usr/share/mxflux/

TEXTDOMAINDIR=/usr/share/locale 
export TEXTDOMAIN="mx-fluxbox"

MESSAGE=$"This will install into your Home folder components that MX-flux requires in order to run.  Any existing fluxbox configuration will be backed up as <i>$HOME/.restore/fluxbox/fluxbox_BAK</i>"
END_MSG=$"To start a fluxbox session: log out, select <i>fluxbox</i> from the pull-down menu in the upper right corner, and log back in."

##begin message box
yad --text="


<b>$MESSAGE</b>" --title=$"OK to proceed?" --window-icon=/usr/share/icons/mxflux.png --geometry=400x40 --text-align=center 
##end message box

if [ ! "$?" = "0" ]; then
    exit 0
fi

#set up fluxbox

if [ -d "$HOME/.fluxbox" ]; then
    mv $HOME/.fluxbox $HOME/.restore/fluxbox/fluxbox_bak_.$(date +%Y%m%H%M%S) 
fi

if [ ! "$?" = "0" ]; then
	exit 1
fi

cp -r /usr/share/mxflux/.fluxbox "$HOME"

#set up idesk

if [ ! -d "$HOME/.idesktop/" ]; then
    mkdir -p "$HOME"/.idesktop/
    else 
    cp -r $HOME/.idesktop $HOME/.restore/fluxbox/idesktop_.$(date +%Y%m%H%M%S)
    cp $HOME/.ideskrc $HOME/.restore/fluxbox/ideskrc_.$(date +%Y%m%H%M%S)
fi

cp /usr/share/mxflux/.fluxbox/components/idesk/fluxhelp.lnk "$HOME"/.idesktop/fluxhelp.lnk

cp /usr/share/mxflux/.fluxbox/components/idesk/.ideskrc "$HOME"/.ideskrc

cp /usr/share/mxflux/.fluxbox/components/.fehbg "$HOME"/.fehbg

#set up the system monitors
cp -r /usr/share/mxflux/.fluxbox/components/.gkrellm2 "$HOME"/.gkrellm2

sleep 2

#start concluding message
yad --text="


<b>$END_MSG</b>" --title=$"All done!" --window-icon=/usr/share/icons/mxflux.png --geometry=400x40 --text-align=center 
#end concluding message

Posted: **Sat Feb 01, 2020 4:46 pm**

I also changed the two toolbar scripts, legacy and userlast, but not worth reviewing here IMO.

Posted: **Sun Feb 02, 2020 7:56 am**

This thread seems to be running out of steam...

Could someone who doesn't already know it please do a bit of testing on MX-idesktool? A lot of work went into that app and we would like to see how users respond.

Posted: **Sun Feb 02, 2020 9:32 am**

Jerry3904 wrote: Sun Feb 02, 2020 7:56 am This thread seems to be running out of steam...

Could someone who doesn't already know it please do a bit of testing on MX-idesktool? A lot of work went into that app and we would like to see how users respond.

I was able to create an icon that launched Firefox, and had a Firefox icon that could be dragged anywhere with the right mouse button.

I didn't find it totally intuitive, but would have no trouble repeating it for other things.

Chris

Posted: **Sun Feb 02, 2020 9:45 am**

Thanks, Chris. Which part was not totally intuitive?

Posted: **Sun Feb 02, 2020 9:49 am**

chrispop99 wrote: Sun Feb 02, 2020 9:32 am
Jerry3904 wrote: Sun Feb 02, 2020 7:56 am This thread seems to be running out of steam...

Could someone who doesn't already know it please do a bit of testing on MX-idesktool? A lot of work went into that app and we would like to see how users respond.
I was able to create an icon that launched Firefox, and had a Firefox icon that could be dragged anywhere with the right mouse button.

I didn't find it totally intuitive, but would have no trouble repeating it for other things.

[Later...]

I didn't like the default icon text colour, so I changed it in .idesk.rc to a pale grey that roughly matches the MX Logo on the wallpaper. The RGB code is #B3B3B3.

Chris

Posted: **Sun Feb 02, 2020 9:55 am**

I didn't like the default icon text colour

Sorry, but which icon? The Help one with the question marks?

Posted: **Sun Feb 02, 2020 9:57 am**

Jerry3904 wrote: Sun Feb 02, 2020 9:45 am Thanks, Chris. Which part was not totally intuitive?

The creation tool 'Left click command'. The layout of that pane is odd; Between the first line beginning NOTE, and the second line beginning runs, there seems to be too much space, so the second line looks like it is referring to the text entry box for the left-click command. It's like a carriage return is in the wrong place. If that spacing could be revised it would be clearer. Also, perhaps the wording for that text entry box could be something like 'Application to run'?

(Trivial - after 'Left click command', there are two colons.)

Chris

Posted: **Sun Feb 02, 2020 9:59 am**

Jerry3904 wrote: Sun Feb 02, 2020 9:55 am
I didn't like the default icon text colour
Sorry, but which icon? The Help one with the question marks?

No, the text that appears under the created icon. It's a sort of kingfisher blue by default.

Chris

Posted: **Sun Feb 02, 2020 10:02 am**

Oh, that. That text is optional, and I don't ever fill it in--maybe we should change the dialogue or something.

Posted: **Sun Feb 02, 2020 10:34 am**

Hi Jerry, I would love to help by testing. But I don't know what I am supposed to do with that file. Maybe I need to wait until it is installable by MXPI? Of course that will mean I can't help in test phase.

Installation
URL: https://drive.google.com/file/d/1bHjyyV ... sp=sharing

md5sum: 236376ce1cb34c7b028ce6a6506c7113 4712752 mx-fluxbox_20.0mx19+1.tar.xz

Once that has installed, then use the command line to move files into Home:
CODE: SELECT ALL

/usr/bin/mxflux_install.sh
An existing fluxbox folder will be backed up to ~/.fluxbox_BAK

If someone can spell it out for me then maybe I can get started. I extracted the files but I don't see how to "install". There is .deb file. Is that what I use to "install"? I don't want to move forward until I know what I am supposed to do. I'm sure this is obvious to most but not to me.

Seaken64

Posted: **Sun Feb 02, 2020 10:36 am**

1. download the file

2. use gdebi to install the deb. in thunar you can just click on the deb and select the gdebi right click action.

3. after installation of the deb, run the mxflux_install.sh script.

4. logout, select the fluxbox session from the session chooser in the upper right part of the login screen, and log back in.

Posted: **Sun Feb 02, 2020 11:55 am**

Thank you D_O, I will follow your instructions.

Posted: **Sun Feb 02, 2020 12:48 pm**

I got it installed. After gdebi finished, I just blindly entered the code in the first post:

Code: Select all

/usr/bin/mxflux_install.sh

and it started. I recognized the dialog boxes informing me what was about to happen. But up until that point I was unsure what was going to happen. I guess this is why some people fear the command line. It's a little unsettling to not know what is going to happen. Now I can make some assumptions after having done it. But I have never done this before and was not sure what that command was going to do. Now I see it ran the script. So my assumption is that a file with the .sh at the end is a type of script. And this script was placed in the /usr/bin/ sub-directory by the .deb installation file. Do I have that right? And MX has the stuff necessary to run this script without any special attention from the user? And this type of script is harmless? Or we can at least trust the instructions as written by the devs?

I'm such a newbie! But learning.

Thanks for the help getting it installed. I am using the beta version now on this machine and posting this from that install. I found a couple of things and will report in next messages.

Seaken64

Posted: **Sun Feb 02, 2020 1:01 pm**

All that you find unsettling will be invisible when we get to Final.

I would like more testing of mx-idesktool. For instance: can people see icons at all when they navigate to /usr/share/icons/papirus/48x48/apps ? I can see icons with other sets, but not that one.

Posted: **Sun Feb 02, 2020 1:06 pm**

I started by reading the PDF help doc. There is a typo on page 2 where it reads:

How can I make it look like other legacy systems such as Windows?

The menu trail should be: Menu>Look>Toolbar>Legacy

The dialog that pops up also has a similar typo. It says Menu>Settings>Toolbar>Userlast but it should be: Menu>Look>Toolbar>User last

I just stumbled across these typos since I was curious about the Legacy look. But I was more interested in reading about the idesk tool. More on that in next message.

Seaken64

Posted: **Sun Feb 02, 2020 1:14 pm**

Thanks. I have been trying to catch all the leftover items from earlier versions, but obviously have not yet cleaned them all up yet.

Posted: **Sun Feb 02, 2020 1:40 pm**

I attempted to add a desktop icon for my preferred browser SeaMonkey. I tried to do it like most new users would do it - without reading the manual!

(Actually I did read the MX-Fluxbox help doc under section "II. iDesk" to get me started. Therein is shown a picture of the mx-idesktool dashboard. That's as far as I read - for now. I will read all the docs in a few minutes. I just wanted to see if it was intuitive enough for me to get an icon launcher in the desktop)

I could not find the mx-idesktool on the menu. I was looking for "mx-idesktool" or "mx-idesk" tool. But I did stumble in to it on the "Look" menu under "Desktop icons" (Menu>Look>Desktop icons). I also found it by using F2 and entering "mx-idesktool".

I started with double-clicking New - Add a New Icon. I entered my caption as SeaMonkey then clicked Next. (I did intuitively understand what the caption was). I left the Left-Click Command field blank (Here I did not intuitively know that this is where I should put the executable file path) and clicked Next. I browsed to the sub-directory that had the seamonkey.png icon file in it and clicked on it then clicked on Next. The screen blinked and a message came on saying desktop was updated.

I looked at the icon and it is HUGE! (I'll read up on sizing). The caption was in a light-bluish color as mentioned by Christopher. If I left-click on it the dialog box for the Icon Management Tool comes on screen, but with nothing on the list and with two buttons - Cancel and OK. If I right-click on it the icon blinks but nothing happens.

I went back and re-read the thread where Christopher shared his own attempt. I gathered from that that I had to make an entry in the Left-Click Command entry box. He had suggested that maybe it should read Application to Launch, or something similar. That gave me a clue.

I went back and did it again and made the entry in the Left Click Command entry box. Now it works to launch SeaMonkey. But there is still nothing on right-click and the Icon Management Tool dialog box comes up along with SeaMonkey.

I can delete the icons, and move them. But I did at first try to move with the left-click-and-drag action which is normal for Windows. That doesn't work. But right-click-and-drag does work (probably in the docs that I haven't read yet).

I'll go back and read all the docs and try it again later.

Seaken64

Posted: **Sun Feb 02, 2020 1:42 pm**

Jerry3904 wrote: Sun Feb 02, 2020 1:01 pm All that you find unsettling will be invisible when we get to Final.

I would like more testing of mx-idesktool. For instance: can people see icons at all when they navigate to /usr/share/icons/papirus/48x48/apps ? I can see icons with other sets, but not that one.

Yes, I figured it will be more newbie friendly when completed. I don't mind the discomfort since this is all a learning process for me and I am on experimental systems. I don't use critical systems for testing and learning.

I'll do more with the mx-idesktool throughout the day.

Seaken64

Posted: **Sun Feb 02, 2020 2:13 pm**

Thanks for looking carefully at mx-idesktool. It seems we need to edit the text, which we inherited from the original script written 15 years ago.

Posted: **Sun Feb 02, 2020 4:38 pm**

I did some tests in mx-idesktool

The tool works to create the icon/launcher on the desktop.

Left-click does launch the program. But it also launches a blank dialog box entitled Icon Management Tool. This dialog box has two buttons in the lower right corner, Cancel and OK. It closes if either button is clicked.

Right-click does not open the mx-idesktools dialog with it's list of actions. When I go through the mx-idesktool entries on the "View or Edit an Icon" selection the right-click command is entered as "mx-idesktool SeaMonkey.lnk". But right-clicking does not start the mx-idesktools program.

If I open the SeaMonkey.lnk file in Featherpad I can see "Command[1]" line entered as:

Command[1]: mx-idesktool SeaMonkey.lnk

I also noted that if I edited the file previously by hand (in Featherpad) and then use mx-idesktool to "View or Edit" then the file gets over-written by mx-idesktools and my previous edits are gone. I guess that would be normal behavior but I would suggest a warning to pop up or an automatic renaming of the file.

If I edit the *.lnk file I can set the size and position, colors, etc. The mx-idesktools does not support those settings.

Seaken64

Posted: **Sun Feb 02, 2020 5:10 pm**

Thanks very much for this careful testing and description, it is just what we needed. I can confirm this behavior.

The app has some serious problems still, some of which unfortunately we thought we had already solved. We have work to do if it is to be included in Final.

Posted: **Mon Feb 03, 2020 11:19 am**

A couple of suggestions about mx-idesktool:
when using mx-idesktool- maybe make it show by default some folder with lots of icons for apps (in .png format) that the user can select as default (ex: /icons/hicolor/22X22/apps) ?
And maybe include, out of the box, a Papirus icon-set in .png format and make it the default icon folder? ( there's already a thread on that...)
(A foolproof idea would be have mx-idesktool add icons using the information of the applications .desktop files, but that would imply a rewrite...)

Some suggestions about the menu:
- add "printer" to the Settings menu (its probably the most used setting missing there, for users that intend to use MX-fluxbox for office work)
- maybe instead of a off of sight menu have a "toggle" menu to turn conky, monitors, desktop icons, etc on and off? Having to click one place to deactivate a setting and then search for a way to reactivate it again can be confusing...
- the menu looks huge... maybe move entries, like "repo" and "wiki" to a sub-menu?
- shouldn't the "Acessories" menu be in the second section (near "All apps"?), it's where the rest of the applications are...
- In Look - Desktop icons - make mx-idesktool automaticaly refresh the icons, so it also serves as a way to autamticaly toggle on desktop icons?
- In out of sight - use "desktop icons" instead of "idesk icons", maybe "desktop idesk icons" if you want to be more precise and still easy understandable by newbies...

Some suggestions about the Desktop:
- the help file icon is handy for new users, why not also display icons for the most common applications the help newbies get started? (Browser, File Manager, Thunderbird, maybe terminal?) You can make idesk position the icons spaced far enough so those icons always show up fine in any screen resolution. That would probably make users just stick with the default setting, and not have to use a (memory draining) dock?

@Jerry: there's probably a more user friendly way to allow users to edit the dock than providing a text template?

Verdict:
This beta is looking even more user friendly and feature rich, but it's not for the main MX crowd... Having to manually edit a text file to have a dock, and having to manually search for the application and icon to add to the desktop is acceptable for advanced users, not for "normal" users that love MX because it provides a GUI for almost every single thing they want to do...

P.

Posted: **Mon Feb 03, 2020 1:39 pm**

Thanks for the careful look and good suggestions to think about. Some of those (icons, for example) are already in process.

Posted: **Tue Feb 04, 2020 6:14 am**

@PPC: this project is *only* 3 months old, and those missing gui apps are on the list for the next cycle after we get all this stabilized. Rome was not built...

Posted: **Tue Feb 04, 2020 6:38 am**

I downloaded the tar file to install Fluxbox, but the md5sum I get with the downloaded file is:

156eb30a9851d1964a0d0bfe06465824 mx-fluxbox_20.0.tar.xz

Has the file on the server been changed?

Posted: **Tue Feb 04, 2020 6:55 am**

Just downloaded again, extracted, right-clicked the tarball file with this result:

Code: Select all

└─> md5sum mx-fluxbox_20.0.tar.xz 
156eb30a9851d1964a0d0bfe06465824  mx-fluxbox_20.0.tar.xz

Looks like it has--likely because the package name has been changed I guess.

Posted: **Tue Feb 04, 2020 7:58 am**

- the help file icon is handy for new users, why not also display icons for the most common applications the help newbies get started? (Browser, File Manager, Thunderbird, maybe terminal?) You can make idesk position the icons spaced far enough so those icons always show up fine in any screen resolution.

This one interests me, thanks. Will probably put just email, browser and file manager (though I personally prefer a clean desktop).

Posted: **Tue Feb 04, 2020 8:14 am**

What do people think of this (using Moka icons)? I selected 32x32 to keep the visual impact minimal, but 48x48 could also be used I suppose.

Posted: **Tue Feb 04, 2020 8:20 am**

Here it is using 48x48 (looks better to me):

Posted: **Tue Feb 04, 2020 8:27 am**

With increasing use of ever higher resolution screens, 48x48 is possibly the best option.

Chris

Posted: **Tue Feb 04, 2020 8:38 am**

And here, finally, using a Moka icon (wine-help) for the FAQ: like this the most now.

Posted: **Tue Feb 04, 2020 8:40 am**

in your startup file, try exporting the gtk variables instead of just making variables. similar to the qt plugin variables.

Posted: **Tue Feb 04, 2020 8:48 am**

dolphin_oracle wrote: Tue Feb 04, 2020 8:40 am in your startup file, try exporting the gtk variables instead of just making variables. similar to the qt plugin variables.

Where do I find that code? Do you mean like this?

Code: Select all

export gtk-theme-name="Adwaita"
export gtk-icon-theme-name="hicolor"
export gtk-font-name="Sans 12"

Posted: **Tue Feb 04, 2020 8:49 am**

its in your fluxbox startup file.

~/.fluxbox/startup I think.

Posted: **Tue Feb 04, 2020 8:51 am**

@dolphin_oracle: check above

Posted: **Tue Feb 04, 2020 9:29 am**

Posted: **Tue Feb 04, 2020 9:32 am**

Jerry3904 wrote: Tue Feb 04, 2020 8:38 am And here, finally, using a Moka icon (wine-help) for the FAQ: like this the most now.

This looks great!

Posted: **Tue Feb 04, 2020 9:41 am**

Jerry3904 wrote: Tue Feb 04, 2020 8:38 am And here, finally, using a Moka icon (wine-help) for the FAQ: like this the most now.

@Jerry:
That desktop looks so polished that if you put that screen-grab on Distrowatch I bet users will come flocking to see what MX-fluxbox is all about! It has every general functionality that a normal user wants from a OS available with a single click, also keeping the desktop clean and smooth looking (much better Help icons, the previous one seemed it came from the dark ages- this one even seems to blend into the default desktop image).
(The only other icon I can imagine could be useful for every day MX users would be the XfCE4 app launcher, maybe? I almost didn't suggest that, the desktop looks so nice that one more icon may be too much - let users over-crowd the desktop if they want to...)

P.

Posted: **Tue Feb 04, 2020 9:58 am**

Glad you like it, thanks again for the suggestion.

Posted: **Tue Feb 04, 2020 1:33 pm**

Jerry3904 wrote: Tue Feb 04, 2020 8:48 am
dolphin_oracle wrote: Tue Feb 04, 2020 8:40 am in your startup file, try exporting the gtk variables instead of just making variables. similar to the qt plugin variables.
Do you mean like this?
Code: Select all
export gtk-theme-name="Adwaita"
export gtk-icon-theme-name="hicolor"
export gtk-font-name="Sans 12"

Nope, that makes FB choke and screen cycles back to login.

Posted: **Tue Feb 04, 2020 1:54 pm**

might as well take them out then, because they are not doing anything.

Posted: **Tue Feb 04, 2020 8:24 pm**

is there a reason for the crazy launch command for apt-notifier?

Posted: **Tue Feb 04, 2020 8:32 pm**

I checked that with Kent, and he said it was good. Took it right off Application Autostart IIRC

Posted: **Wed Feb 05, 2020 11:25 am**

I have the doc set so that it starts automatically on logon. However, every time I log on, the icons on the dock appear in a different order. Is there any way to ensure that the dock always starts with the icons in a set order, preferably the order that you want them to appear?

Posted: **Wed Feb 05, 2020 11:32 am**

Not the way we have it. The fluxbox documentation talks about how to do it if you set it up yourself. Don't have that reference right now but I think it's one of the links at the end of the Help document (F1).

Posted: **Wed Feb 05, 2020 11:42 am**

I had that very same problem when testing wmalauncher, David, Jerry...
The way I solved was adding a sleep command after each wmalauncher command (if you want to be on the safe side, add it also before the first command). Sleep 0.5 works, you may try with a ever smaller value.
Example:
wmalauncher --command firefox --icon /usr/share/icons/Papirus/64x64/apps/firefox.svg & sleep 0.5 &&
wmalauncher --command thunar --icon /usr/share/icons/Papirus/64x64/apps/thunar.svg & sleep 0.5 &&

P.

Posted: **Wed Feb 05, 2020 12:34 pm**

That would be cool, thanks

Posted: **Wed Feb 05, 2020 6:56 pm**

Just discovered that I can lock the 4 beautiful default Moka icons in place by changing the line in ~/.ideskrc

Code: Select all

locked false

to

Code: Select all

locked true

I would like to do this b/c it is so easy to get them out of line when clicking them. But then all iDesk icons would be locked in place until the user changed the line back again.

Hmmm, what to do?

LATER: going to do it, users can always delete the icons and start again using mx-idesktool

Posted: **Wed Feb 05, 2020 7:11 pm**

I wonder how hard it would be to add an entry to mx-idesktool: "Lock/Unlock icons" ?

Posted: **Wed Feb 05, 2020 7:33 pm**

what does it have to do...edit the idesk file and restart idesk?

Posted: **Wed Feb 05, 2020 7:42 pm**

Just refreshing the desktop doesn't do it, and double middle clicking (!) doesn't either. Looks like it needs to log out and have the user log back in.

Would probably require 3 new strings, but I've got to go back to Roy for translations anyway.

1) "This will lock all icons in place"
2) "This will unlock all icons in place"
3) "You will need to log out and back in for the new settings to take effect" << pretty much exists already in the toolbar scripts

Posted: **Wed Feb 05, 2020 8:12 pm**

I wrote a toggle. pushing your way. no need to log out/log in.

there are 2 new strings. you can change them in your strings area...no need to change the code below, its all variables.

you could sort of do it already by using the .idesk config option, changing the variable, and then using refresh function.

Posted: **Wed Feb 05, 2020 8:21 pm**

Nice. I know it could be done with existing tools, but people would have to know or be told how to do it...

Posted: **Wed Feb 05, 2020 8:41 pm**

I added a confirming box with this code:

Code: Select all

unlock_icons()
{
#grep for Locked: true and if present change to Locked: false

local test toggle

test="$(grep Locked: "${HOME}/.ideskrc" |grep true)"

if [ -n "$test" ]; then
    sed -i s/Locked.*/'Locked: false'/ "${HOME}/.ideskrc"
    else
    sed -i s/Locked.*/'Locked: true'/ "${HOME}/.ideskrc"
fi

$DIALOG  --title "$TEXT5" --width 250 --height 30 \
		 --text="$TEXT22"	\
		 --button="OK"

refresh

}

Look OK?

Posted: **Wed Feb 05, 2020 8:45 pm**

it doesn't hurt anything

Posted: **Wed Feb 05, 2020 9:06 pm**

Also changed your second text for easier translation: "Permit/prevent icon movement"

Posted: **Thu Feb 06, 2020 8:58 am**

PPC wrote: Wed Feb 05, 2020 11:42 am Example:
wmalauncher --command firefox --icon /usr/share/icons/Papirus/64x64/apps/firefox.svg & sleep 0.5 &&
wmalauncher --command thunar --icon /usr/share/icons/Papirus/64x64/apps/thunar.svg & sleep 0.5 &&

I couldn't get it to work that way, but it did work fine when I altered it (using your example):

Code: Select all

 wmalauncher --command thunar --icon /usr/share/icons/Papirus/64x64/apps/thunar.svg & sleep 0.1

BTW: we've started work on a mx-dockmaker, not sure when it will be ready!

Posted: **Fri Feb 07, 2020 9:36 am**

Is there any way to have the doc in Fluxbox always visible? I like having the facility to just click once to activate an application that I frequently use. It would be nice to replicate the functionality of the panel in XFCE.

Posted: **Fri Feb 07, 2020 10:00 am**

It is always visible (icon in upper left corner) unless you removed it.

It would be nice to replicate the functionality of the panel in XFCE.

Two very different systems, there is no "replication" possible.

Posted: **Sat Feb 08, 2020 11:11 am**

Hello Jerry3904 and Everyone
hi David P , mx-fluxbox is the same sports car as xfce, with just a different shifting pattern. Key F6 is a new habit?
Bring your panel. Or by all means call the fully loaded panel from xfce with Run xfce4-panel to participate with fluxboxwm; hide xfce panel for fluxbox session and we will never know. Other docks available to create to user preference. Launchers in mx-fluxbox are in development.

Posted: **Sat Feb 08, 2020 11:17 am**

Hello Jerry,

I have managed to achieve what I wanted. There is a setting in the init file that controls whether or not a window will obscure the slit when it is maximized. On my system it was set to true. Setting it to false means that the slit "holds its territory and is always visible", as it says in the wiki. Changing this setting now means that I am able to open frequently used applications with a single click, regardless of whether I already have an application window maximized, as the dock (or launcher) resides in the slit. This is what I was trying to achieve.

The setting in question in the init file and its current setting on my machine is:

session.screen0.slit.maxOver: false

Posted: **Sun Feb 09, 2020 3:44 pm**

Oh, DOCK! I thought you said "Doc". Now I get it.

Posted: **Wed Feb 12, 2020 11:41 pm**

Hello Jerry3904 and Everyone
MX-19_64 mx-fluxbox
We move windows with alt+left-click-hold, so why not move icons the same way [trialed.]
Snap set false.
success with this:
table Actions
Lock: control right doubleClk
Reload: middle doubleClk
Drag: alt left hold
EndDrag: left singleClk
Execute[0]: left doubleClk
Execute[1]: right singleClk

Press key Alt+hold left mouse button to drag and drop idesk icon (if not locked.)
The exec0 with left single-click calls the command0 upon Drop.
The exec0 with left double-click no open app upon Drop, but you have double-click to execute icon normal.
The Lock toggle does work. control+right-double-click; all icons.
That brings up the mid-measure observation that the right-click edit menu is not available to an icon that has blank the command1 line.
create a command1 response on a per icon basis.
idesk is a real gem.

MX Linux Forum

MX-Fluxbox 2.0 beta testing thread

MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread

Re: MX-Fluxbox 2.0 beta testing thread