I am an avid Fluxbox WM user ...
The Fluxbox Window Manager is closely based on Blackbox WM.
Fluxbox WM and Openbox WM - can use the xorg-system-core, with NO desktop environment. Much like what Crunchbang and Archbang have done.
Fluxbox is still closely based on Blackbox. Some say that, Fluxbox is the natural progression of Blackbox. Fluxbox is a basic Blackbox; with a few more things added for user-friendliness. Not to take anything away from the base-Blackbox build ... the BB-Devs did an awesome job. I use many of the BB scripts, themes/styles and apps with Fluxbox -- they seems to be pretty much forward and backward compatible.
Openbox, was also, based on Blackbox but has grown more separate from the BB-base, with using and building it's own configs and apps. Although, Openbox seems to be growing in popularity, with more Linux OS-distro systems using Openbox - as the default Window Manager.
There are advantages, pros and cons, to using either Openbox and/or Fluxbox.
Fluxbox has:
A self-updating 'right-click' Menu
It's own Fb-panel/taskbar (no need for tint2)
A built-in Composer
Does not use a GUI or .xml files but everything is a simple Script
Easy to use and Configure.
There are already hundreds of fb-styles (themes) available.
As light-weight on resources (or lighter) than using Openbox.
Fluxbox Resources:
Fluxbox: http://fluxbox.org (http://fluxbox.org)
Fb-Wiki: http://fluxbox-wiki.org (http://fluxbox-wiki.org)
How-To: http://fluxbox-wiki.org/index.php?title=Category:Howtos (http://fluxbox-wiki.org/index.php?title=Category:Howtos)
FAQ: http://fluxbox-wiki.org/index.php?title=Faqs (http://fluxbox-wiki.org/index.php?title=Faqs)
http://LostintheBox.com (http://lostinthebox.com) (Forum)
http://box-look.org (http://box-look.org) (themes and more)
http://tenr.de/ (http://tenr.de/) (themes/styles)
https://wiki.archlinux.org/index.php/Fluxbox (https://wiki.archlinux.org/index.php/Fluxbox)
http://wiki.debian.org/FluxBox (http://wiki.debian.org/FluxBox)
Hey thanks for this vrkalak! Will check some of those links out for sure...
I must say, I've tried FluxBox and it's - - - not OpenBox. Just kidding ...
I did find it very interesting and as you said "A self-updating 'right-click' Menu" is a nice feature.
If I recall it has "icon support" in the menus as well.
And it had one feature that OpenBox doesn't have and that's transparency in the menus, but 'compton' added that to OB. It isn't 'native' to OB though so it can't be controlled like it can in FluxBox.
I too am going to check out those links .. and just maybe take FB for another test drive.
One Distro 3 sessions: XFOBFB :D :D
Fluxbox and gkrellm what was i was using in my "early years", and its still a solid and sturdy wm, with very much less bloat around :)
Sure you can use conky, i mean conky runs everywhere, even in command line :) but.... gkrellm is sexy, it can even monitor other hosts (yes your server too, if you have one)
Anyway, thanks for reminding me vrkalak :)
Early thoughts and questions on flux
I want to run everything from ~/.fluxbox/menu, and as I followed the instructions to modify ~/.fluxbox/init and add:
session.menuFile: ~/.fluxbox/menu
I found it was already there.. but it did not seem to work until I did a Reconfigure and looking at it this morning, it seems to have a limit as to how long the menu can be? Not sure, will have to check on that more... I was removing an [end] that was cutting off the bottom
I do not understand how or where to make compositing work, everything I read said it was using xcompmgr for compositing which is not used in VSIDO... Since we already have Compton, I just slid that in in the startup and it works perfectly
I need to know how to turn off the panel, not just hide it... It is controlling the systray items and will not let another systray app (tint2) work because it appears to still be on ... anyone know how to turn that off completely?
Thanks for this thread and those links vrkalak, I am having a blast and am definitely not bored anymore 8)
Regarding the systemtray and the toolbar..
I had to remove systemtray from the list of items in in ~/.fluxbox/init on the line session.screen0.toolbar.tools, then set session.screen0.toolbar.visible to false. Now the tint2 systray is working
@Sector11 - Regarding icons in the menu, it is done the same way you can put icons in the OB menu but just like icons in the OB menu, I think they look crappy and have removed them
Quote from: dizziegkrellm is sexy, it can even monitor other hosts (yes your server too, if you have one)
Interesting! ???
I'll be taking a look at this later today.
Thanks.
I used gkrellm before I discovered conky more than 7 years ago now... It did do what I wanted at the time, but conky proved to be much more robust with so many more options
I may have to look at gkrellm again, let me know your thoughts about it if you test it jst_joe
I used gkrellm for a few weeks before discovering conky. I thought, during that time, "This is great!"
Not hard to see which direction I went after that. ::)
^ Agreed.. It was me searching for something that gkrellem could not do and I needed done that led me to Conky
Quote from: VastOneI may have to look at gkrellm again, let me know your thoughts about it if you test it jst_joe
After reading up on it I don't really see the advantage of running it on my web server (considering it's here in the same room).
If it were in a remote location I could see some advantages, but as it stands I can't justify opening up an extra port.
After figuring out the transparency of Fluxbox, I was able to turn off Compton...
Booting now with the Liquorix 3.7.0-9 kernel and Fluxbox, I am down to an eve 100 MiB on boot and now claim Fluxbox as my default WM
Now onto figuring out the Slit mess, if I am reading it correctly it is somewhat akin to Conky
WOW!!! You're saying "Bye bye" to Xfce4. :o
You are impressed.
EDIT: Just installed the latest - looked at FluxBox ... I'm still using OB 8)
For the time being, I guess until Fluxbox pisses me off... :o
The Slit thing is cool but all the 'dock' slit apps are Windowmakers dockets and look like something out of the 90's...
If you are talking this WindoMaker (http://step.polymtl.ca/~coyote/picturesd/linux/windowmaker_normal.jpg) I know what you mean.
Opinion Alert: That looks like an MS Windows v1 reject.
Quote from: VastOne on February 27, 2013, 11:45:30 PM
After figuring out the transparency of Fluxbox, I was able to turn off Compton...
Booting now with the Liquorix 3.7.0-9 kernel and Fluxbox, I am down to an eve 100 MiB on boot and now claim Fluxbox as my default WM
Now onto figuring out the Slit mess, if I am reading it correctly it is somewhat akin to Conky
It's a dock. Not sure exactly how it works, but I have always had it center top and out of the way. I thought you was using it already, didn't know it was specific to fluxbox.
Feeling really stupid right know! ??? I've been using fluxbox with Ubuntu for a couple of years. It's small and quick. When I downloaded #!, I tried OB then returned back to FB. Just more familiar with it I guess. With Vsido, I used XCFE for awhile then switched back to FB. I THOUGHT you were using the slit to anchor Conky to the top! DUH Not in XFCE.
The best way I can describe the slit is that it is a relocatable dock that you can fasten Conky or whatever you want to it. I have Conky and bbrun fastened to it at the moment. I loved your Conky just the way it was but I added the date and time to the end of it. I used the slit to move it back up and center were you had it originally in XFCE.
Hope that helps.
J
^ It does help Jmagick! Thanks, I do appreciate it..
Fluxbox is really growing on me
How does one go about updating the menu?
I thought when I used Fluxbox on antiX it had an "update menu" script/link. That was my only time trying out Fluxbox, and I thought it was one of the features, as compared to Openbox's manual menu config.
-- jeff
Good question... I Have not installed anything new since using it. I know there are a couple of packages ... I know kendall_tristan created FM3 but it does not handle anything in the exec line except the command. In VSIDO's menu there is 'launch' as part of the exec line which checks to make sure the app is not open already and does not launch a new instance
I am going to test a few things and will get back to you on what is happening with the menu and auto-updating
Im about to install the new ISO and play with fluxbox a bit and if that doesnt work Im just going to install Gnome3 and be done with it :D
Here is an excellent read... Fluxbox Menu Management (https://wiki.archlinux.org/index.php/Fluxbox#Menu_Management)
Got to love the ArchWiki
This is a good starting point for a discussion on how VSIDO Fluxbox menus should be done
I will check with AntiX to see if their menu generator is available
I was under the impression that fluxbox had an auto updating menu. Is this not correct?
Quote from: lwfitz on March 04, 2013, 12:17:59 AM
Im about to install the new ISO and play with fluxbox a bit and if that doesnt work Im just going to install Gnome3 and be done with it :D
Blasphemy ! Do that and Be GONE!!! ???
I will let you know in a bit lwfitz... Testing now
I have tested several of these auto-update menu programs and I am not happy with any of them.. All of them take your current menu and replace it which is in no way 'updating' per se
Even the AntiX auto generating one does the same thing and removes everything from their default menu and replaces it
Most of us are used to OB and the menu system... I have no issue with Fluxbox and the need to manually update it for now ... I will keep searching
a-ha.
Never hurts to ask; I borked a previous VSIDO install before you included Fluxbox by adding it, but something went wrong and everytime I used it, I was thrown back to the login screen. An endless loop.
Sometimes it takes awhile to get to know these WM.
Thanks for looking into it, though.
Sure...
I saw that endless loop chain one time too... It was because for some reason the install of Fluxbox did not have the correct rights on the directory and it could not write what was needed
Where VastOne beat me to the punch by saying
Blasphemy ! Do that and Be GONE!!! ???
Can we have him drawn and quartered?
The nerve!
Quote from: VastOne on March 04, 2013, 01:15:36 AM
Sure...
I saw that endless loop chain one time too... It was because for some reason the install of Fluxbox did not have the correct rights on the directory and it could not write what was needed
Okay, so it wasn't just me :D
Shortly thereafter, I added that second internal harddrive, so I just re-did my install, but used the most current ISO, which had FB on it. Saved a few steps.
One thing you have to remember when using the Fluxbox WM, that after you Add/Install/Remove/Edit something, you need to 'refresh' (Recogfigure) the WM.
Yes, the Menu is auto-updating but sometimes I have to 'refresh' the Menu or in the Terminal do a "sudo update-menus" That's all that is needed, with Debian.
Interesting...
I installed audacious
I then ran ran sudo update-menus but nothing changed
Is it possible something else needs to be installed?
Thanks vrkalak
Interesting it is... I've used FB for quite awhile, this seems to be an issue only with certain programs.
When I installed Darktable, it auto updated to the menu but, with the install of Digikam it did not update into the menu. Did the same thing in Ubuntu and #!.
Don't remember which program in #! as I have always manually added them in the past no matter which distro. Be curious to see the fix for this.
J
HAHAHA Sector11! At least I didnt say KDE!
↑ :-[ Oh oh ... that be worse.
mauh :D mauh :D
I have to say, I am totally blown away by fluxbox right now. Its like Openbox on crack ??? ???
Im in love all over again!
^OB on crack!!! Yeah for sure a good way to put it! I'm really liking it as well and have now switched to using it as my default WM. @VastOne, the flickering issue with the Tint2 panel is gone after I removed the ability for it to autohide. Not sure if that is relevant or not, but since then it has functioned perfectly...
Quote from: VastOne on February 27, 2013, 11:45:30 PM
After figuring out the transparency of Fluxbox, I was able to turn off Compton...
Booting now with the Liquorix 3.7.0-9 kernel and Fluxbox, I am down to an eve 100 MiB on boot and now claim Fluxbox as my default WM
Now onto figuring out the Slit mess, if I am reading it correctly it is somewhat akin to Conky
Don't know if you have this all figured out yet so I'll post anyway. If you want compositing with real transparency, you can add your compton/xcompmgr script to the $HOME/.fluxbox/startup file - this file is like the openbox autostart.sh file. Fluxbox does not always play nice with compositors though; something about the window name/class conventions issued by fluxbox - I didn't find much of an answer when googling the issue. I have it working and will post a scrot.
The slit in fluxbox is a dock. Any app that can be docked can reside in the slit, and there is a $HOME/.fluxbox/slitlist file where apps can be defined to automatically dock in the slit. If you use a one line conky like myself (any conky will do this) change own_window_type to dock and it will park in the slit and always - by default anyway - be above maximized windows and remain visible. Note that with own_window_type set to dock, the x,y displacement of the conky window is ignored, it goes where the dock/slit is set.
Aye, I ended up using Compton and it works quite well with Fluxbox... The only issue I see is on boot with my Conky panel, I have to open it and save it twice for transparency to actually work with it ... It has a chalk white film over it until I do that
I do use the Slit for that top panel, and it works out great... One of the things I had always wanted with that panel was the ability to autohide it. With Slit, I can do that
Thanks PackRat...
No problem.
As promised, the screenshot. Fluxbox - latest built from git sources, compton, real transparency in urxvt-unicode (requires an .Xdefault setting), tabbed urxvt, and conky in the slit so that maximzed windows do not cover all that useful info:
(http://t.imgbox.com/acbnH48n.jpg) (http://imgbox.com/acbnH48n)
I have a couple of apps that are behaving strangely in Fluxbox that I cannot make sense of
I have these apps open
iceweasel
medit
filezilla
terminal
spacefm
If I use alt tab I can tab switch to medit, terminal and spacefm with no issues... but trying to get to iceweasel or filezilla, neither one of these will come to the foreground, they will only stay in the background
I actually have to minimize spacefm, terminal and medit to be able to get to iceweasel and filezilla
If I close everything but iceweasel and filezilla, I can tab between the two of them with no issues
If I have those two open, and open any one of medit terminal or spacefm, the behavior starts again, meaning that it does not need to be all three of them started
The same thing happens if I use the mouse to click on any one these apps, it is not just the alt tab function that causes it
Anyone else seeing anything like this?
Yes, I duplicated the problem you're having. Although, using Alt-Shift-Tab cycled through all of them.
edit - did some searching; looks like it is related to the focus model. I was using click-to-focus which I think is the default. Switching over to mouse focus, or mouse focus strict solves the problem on my system. I can also get the Alt-Tab working as expected if I leave it as click-to-focus, but turn off the Auto Raise option.
This focus model pretty much makes things behave the way I want:
(http://t.imgbox.com/acyiuFUq.jpg) (http://imgbox.com/acyiuFUq)
Edit - too weird -
If I change the default:
Mod1 Tab :NextWindow {groups} (workspace=[current])
Mod1 Shift Tab :PrevWindow {groups} (workspace=[current])
to:
Mod1 Tab :NextWindow (workspace=[current])
Mod1 Shift Tab :PrevWindow (workspace=[current])
in the $HOME/.fluxbox/keys file, the Alt-Tab and Alt-Shift-Tab works as expected with the default focus model. Eliminating {groups}, however, results in tabbed windows not being treated as a group.
Final Edit - I couldn't duplicate the issue on my desktop computer. Desktop is Debian Wheezy, and the laptop is Debian Sid and has a touch-pad. Other than that, pretty much the same setup.
rkwurth asked a question in the #! forum -- http://crunchbang.org/forums/viewtopic.php?pid=321189#p321189 (http://crunchbang.org/forums/viewtopic.php?pid=321189#p321189)
This solution should work on any window manager actually. If you have wmctrl and zenity installed, you can have a popup dialog of open apps to switch to (a common Alt-Tab behavior for other wm's)
The code:
wmctrl -ia `wmctrl -l | cut -d' ' -f1,4- | zenity --list --column Window | cut -d' ' -f1`
can be bound directly to a key binding or used from a script. Downside is that it will show all the running apps (and switch to them) regardless of the desktop.
A wise man once said "screenshot or it didn't happen!"
(http://s23.postimg.org/xivh621kn/July_1373683395_1366x768.jpg) (http://postimg.org/image/xivh621kn/)
There is also a program called superswitcher that apparently does this - and other things - but I have never used it:
https://code.google.com/p/superswitcher/ (https://code.google.com/p/superswitcher/)
Without trying it, doesn't fbpager or bbpager do something like screen switching? :) Maybe I'm totally wrong too. :-[
They are pagers like the Xfce workspace switcher.
fbpager is no longer developed and is actually discouraged by the fluxbox devs on the website and wiki. I don't think bbpager or obpager (blackbox and openbox pagers) are being developed anymore either. There are some other pagers out there, but I never really cared for them from an aesthetic standpoint.
It's actually pretty easy to set up tint2 in pager only mode for fluxbox and get to match up with your fluxbox theme and transparency; doesn't use a lot of resources.
Quote from: PackRat on July 23, 2013, 12:50:57 PM
It's actually pretty easy to set up tint2 as a pager only for fluxbox and get to match up with your fluxbox theme and transparency; doesn't use a lot of resources.
Hmmmm... I need to look into that and use those resources. I have been using FluxBox for quite sometime I still have not delved into all of what it is capable of
Thanks for the tip
Just set up tint2 to display multiple desktops only; tinker with the padding and some basic math and tint2 will function as a pager and be scaled to your screen's aspect ratio. Kind of stylish. The main difference is that the tint2 icons will be aligned with the taskbar, they don't float in their relative positions like they do on an authentic pager.
edit - picture is worth 1000 characters:
(http://s7.postimg.org/oy8i5b0jr/2013_07_23_scrot.jpg) (http://postimg.org/image/oy8i5b0jr/)
and the tint2rc
# Tint2 config file
# Generated by tintwizard (http://code.google.com/p/tintwizard/)
# For information on manually configuring tint2 see http://code.google.com/p/tint2/wiki/Configure
# Background definitions
# ID 1
rounded = 0
border_width = 0
background_color = #000000 0
border_color = #FFFFFF 0
# ID 2
rounded = 3
border_width = 2
background_color = #DAD7D0 10
border_color = #575238 66
# ID 3
rounded = 3
border_width = 2
background_color = #DAD7D0 10
border_color = #AE573C 66
# ID 4
rounded = 2
border_width = 0
background_color = #DAD7D0 0
border_color = #A52A2A 66
# ID 5
rounded = 2
border_width = 0
background_color = #DAD7D0 66
border_color = #111111 66
# ID 6
rounded = 2
border_width = 1
background_color = #A52A2A 4
border_color = #7C2E21 100
# Panel
panel_monitor = all
panel_position = top center horizontal
panel_items = T
panel_size = 40% 36
panel_margin = 0 32
panel_padding = 0 0 12
panel_dock = 0
wm_menu = 0
panel_layer = bottom
panel_background_id = 1
# Panel Autohide
autohide = 0
autohide_show_timeout = 0.3
autohide_hide_timeout = 2
autohide_height = 2
strut_policy = none
# Taskbar
taskbar_mode = multi_desktop
taskbar_padding = 1 1 4
taskbar_background_id = 2
taskbar_active_background_id = 3
# Tasks
urgent_nb_of_blink = 8
task_icon = 1
task_text = 0
task_centered = 1
task_maximum_size = 64 36
task_padding = 6 2
task_background_id = 4
task_active_background_id = 4
task_urgent_background_id = 6
task_iconified_background_id = 1
task_tooltip = 1
# Task Icons
task_icon_asb = 50 0 0
task_active_icon_asb = 90 0 0
task_urgent_icon_asb = 100 0 0
task_iconified_icon_asb = 50 0 0
# Fonts
task_font = sans 7
task_font_color = #FFFFFF 68
task_active_font_color = #FFFFFF 83
task_urgent_font_color = #FFFFFF 83
task_iconified_font_color = #FFFFFF 68
font_shadow = 0
# System Tray
systray = 1
systray_padding = 0 4 5
systray_sort = ascending
systray_background_id = 0
systray_icon_size = 16
systray_icon_asb = 70 0 0
# Clock
time1_format = %H:%M
time1_font = sans 8
time2_format = %A %d %B
time2_font = sans 6
clock_font_color = #FFFFFF 74
clock_padding = 1 0
clock_background_id = 0
clock_rclick_command = orage
# Tooltips
tooltip_padding = 2 2
tooltip_show_timeout = 0.7
tooltip_hide_timeout = 0.3
tooltip_background_id = 2
tooltip_font = sans 10
tooltip_font_color = #000000 80
# Mouse
mouse_middle = none
mouse_right = close
mouse_scroll_up = toggle
mouse_scroll_down = iconify
# Battery
battery = 0
battery_low_status = 10
battery_low_cmd = notify-send "battery low"
battery_hide = 98
bat1_font = sans 8
bat2_font = sans 6
battery_font_color = #FFFFFF 74
battery_padding = 1 0
battery_background_id = 0
# End of config
Thanks for the feedback PackRat. :)
Is fbpanel no longer maintained as well? :)
Last version is 2010 so I would say it is no longer maintained. Looks like bmpanel2 isn't maintained either.
@PackRat - thanks, what are the options without composting : tint2, lxpanel, ... ? :'(
What are you trying to do? Are you replacing fluxbox's native panel, or just want to add a pager?
If you just want a pager app, there is netwmpager: http://crunchbanglinux.org/wiki/netwmpager_howto (http://crunchbanglinux.org/wiki/netwmpager_howto)
If you want a launcher there is wbar - https://code.google.com/p/wbar/ (https://code.google.com/p/wbar/)
That is the default launcher in siduction, has animations like increased icon size and movement.
Adeskbar is another launcher - http://adeskbar.tuxfamily.org/ (http://adeskbar.tuxfamily.org/)
lxpanel is the only complete panel I know of that is probably still developed. The Xfce panel should have at least partial functionality in fluxbox, or you may still be able to use fluxbox as the window manager for xfce.
edit - The xfce panel appears to work just fine in fluxbox - I was thinking it lost a lot of funtionality. If you're just looking for a pager, you can create a panel that has the xfce pager as the only item.
(http://s10.postimg.org/wksl02vrp/Screenshot_07242013_11_20_21_AM.jpg) (http://postimg.org/image/wksl02vrp/)
edit 2 - the xfce logout dialog is what does not work, so you would need to exit from fluxbox.
Hi PackRat I'm just look for alternatives to tint2 that are still being maintained. I'm happy with xfce and fluxbox, but always on the look out for any improvements. Thanks for you reply Ozi
found a pager app called neap - sits in the system tray:
neap pager app (http://code.google.com/p/neap/wiki/Welcome)
Nice find PackRat. I'll definitely check it out...
Quote from: vrkalak on February 25, 2013, 10:31:25 PM
I am an avid Fluxbox WM user ...
The Fluxbox Window Manager is closely based on Blackbox WM.
Fluxbox WM and Openbox WM - can use the xorg-system-core, with NO desktop environment. Much like what Crunchbang and Archbang have done.
Fluxbox is still closely based on Blackbox. Some say that, Fluxbox is the natural progression of Blackbox. Fluxbox is a basic Blackbox; with a few more things added for user-friendliness. Not to take anything away from the base-Blackbox build ... the BB-Devs did an awesome job. I use many of the BB scripts, themes/styles and apps with Fluxbox -- they seems to be pretty much forward and backward compatible.
Openbox, was also, based on Blackbox but has grown more separate from the BB-base, with using and building it's own configs and apps. Although, Openbox seems to be growing in popularity, with more Linux OS-distro systems using Openbox - as the default Window Manager.
There are advantages, pros and cons, to using either Openbox and/or Fluxbox.
Fluxbox has:
A self-updating 'right-click' Menu
It's own Fb-panel/taskbar (no need for tint2)
A built-in Composer
Does not use a GUI or .xml files but everything is a simple Script
Easy to use and Configure.
There are already hundreds of fb-styles (themes) available.
As light-weight on resources (or led light (http://www.niceledlights.com)) than using Openbox.
Very impressive indeed.. Never thought like this but now I will surely use Fluxbox WM.. Thanks for the information
Ya know... quoting an entire thread doesnt make you state a fact, it just make you look dumb, so please state what you want to say, without quoting a page full of what we've already read. Thank you :)
Messing around with adding pseudo tiling behavior in fluxbox while downloading V-raptor.
Getting mixed results:
(http://t.imgbox.com/adcRGV5L.jpg) (http://imgbox.com/adcRGV5L) (http://t.imgbox.com/abeuQOLv.jpg) (http://imgbox.com/abeuQOLv) (http://t.imgbox.com/ablVqj0a.jpg) (http://imgbox.com/ablVqj0a)
The code if anyone interested wants to tinker with it. Started out as an exercise in using MacroCmd and ToggleCmd for some keybindings:
Mod1 Shift l :MacroCmd {MoveTo 0 0 UpperLeft} {ResizeTo 683 200} {MaximizeVertical}
Mod1 Shift r :MacroCmd {MoveTo 0 0 UpperRight} {ResizeTo 683 200} {MaximizeVertical}
Mod1 Shift t :MacroCmd {MoveTo 0 0 UpperLeft} {RezizeTo 200 393} {MaximizeHorizontal}
Mod1 Shift b :MacroCmd {MoveTo 0 0 LowerLeft} {ResizeTo 100 393} {MaximizeHorizontal}
Mod4 Shift h :MacroCmd {ResizeTo 682 364} {MoveTo 0 0 UpperLeft}
Mod4 Shift j :MacroCmd {ResizeTo 682 364} {MoveTo 0 0 UpperRight}
Mod4 Shift k :MacroCmd {ResizeTo 682 364} {MoveTo 0 0 LowerLeft}
Mod4 Shift l :MacroCmd {ResizeTo 682 364} {MoveTo 0 0 LowerRight}
Wow! That is really nice. I am curious as to what the tiling users will see in this
Thanks for sharing!
Quote from: VastOne on September 16, 2013, 03:18:36 AM
Wow! That is really nice. I am curious as to what the tiling users will see in this
Thanks for sharing!
I see..... (get ready for this) Possibilities, very nicely done Packrat ;D
^, ^^ muchas gracias
Started out as an exercise in using MacroCmd and ToggleCmd (see fluxbox wiki for details) - I chose window placement to see if I could replicate the Win-Left/Right/Up/Down behavior of Windows 7. Used only native fluxbox commands and have hit a couple snags when multiple windows are open - tiling to the right doesn't always work - but will if the key binding is invoked again; unfortunately, I do not know of a way for fluxbox to resize a window based on a percentage of the desktop, not pixels (my commands are for 1366x768 laptop, adjust for your monitors). I suspect that using scripts with wmctl and/or xdotool smoother tiling is possible. Adding ToggleDecor to the command string would probably be beneficial too.
(http://s9.postimg.org/fxcza7zln/September_1379333385_1366x768.jpg) (http://postimg.org/image/fxcza7zln/)
as far as I know, pytile works with fluxbox - but that's cheating ;)
the object with this exercise is to use fluxbox's internal commands to get the desired results.
Edit - Received a telepathic message from Captain Obvious this morning (in my world she looks like Salma Hayek); if 50% is used instead of, say 50, with the ResizeTo command, fluxbox will interpret that as 50% of the desktop real estate and account for the fluxbox toolbar and anything docked in the slit (conky in my instance) rather than 50 pixels.
(http://t.imgbox.com/abj6KUmt.jpg) (http://imgbox.com/abj6KUmt) (http://t.imgbox.com/adixvOHe.jpg) (http://imgbox.com/adixvOHe)
now just have to solve issue of tiling to right.
Edit #2 - last one, I promise - MacroCmd is read left to right so the order matters:
ToggleDecor --> ResizeTo --> MoveTo = the proper order, all the windows are tiled as desired.
(http://t.imgbox.com/acxKkBQk.jpg) (http://imgbox.com/acxKkBQk) (http://t.imgbox.com/aboNnxpg.jpg) (http://imgbox.com/aboNnxpg) (http://t.imgbox.com/abzZHrDS.jpg) (http://imgbox.com/abzZHrDS)
and the code, one chain to untile the active window:
# manual tiling with key chains - useing chains to avoid clash with keybindings #
Ctrl a Mod4 h :ArrangeWindowsHorizontal
Ctrl a Mod4 v :ArrangeWindowsVertical
Ctrl a Mod4 l :MacroCmd {ResizeTo 50% 50%} {MoveTo 0 0 UpperLeft} {MaximizeVertical}
Ctrl a Mod4 r :MacroCmd {ResizeTo 50% 50%} {MoveTo 0 0 UpperRight} {MaximizeVertical}
Ctrl a Mod4 t :MacroCmd {ResizeTo 50% 50%} {MoveTo 0 0 UpperLeft} {MaximizeHorizontal}
Ctrl a Mod4 b :MacroCmd {ResizeTo 50% 50%} {MoveTo 0 0 LowerLeft} {MaximizeHorizontal}
Ctrl a Mod1 h :MacroCmd {ToggleDecor} {ResizeTo 50% 50%} {MoveTo 0 0 UpperLeft}
Ctrl a Mod1 j :MacroCmd {ToggleDecor} {ResizeTo 50% 50%} {MoveTo 0 0 UpperRight}
Ctrl a Mod1 k :MacroCmd {ToggleDecor} {ResizeTo 50% 50%} {MoveTo 0 0 LowerLeft}
Ctrl a Mod1 l :MacroCmd {ToggleDecor} {ResizeTo 50% 50%} {MoveTo 0 0 LowerRight}
Ctrl a Mod4 m :MacroCmd {ToggleDecor} {Resize 60% 40%} {MoveTo 0 0 Center}
enough for now, time to back up files and set up for Velociraptor install.
loving the pseudo tiling stuff there packrat. kinda surprised no one was meddling with it sooner. of all the features, i think that's the stuff i missed the most in openbox. all that fill to edges stuff, etc.
^ They are are basically move and resize command combinations; should be doable in openbox and pekwm.
Very interesting ectropy. Not sure I follow all of it but starting to see why I am not getting many auto adds to my menu. I guess that would be none. I assume that when the /usr/share/applications/*.desktop file has a Categories line that you don't have setup it is not going to create it, so there fore it is not going to show. Is that right? I am going to research this, I really have never paid much attention to desktop entries before so a whole 'nother rabbit hole to jump down. Thanks ... I think ::)
I'll post this here since I don't want to start a new topic just for this configuration.
These are the layers (highest to lowest) defined by fluxbox:
2 - Above Dock
4 - Dock
6 - Top
8 - Normal
10 - Bottom
12 - Desktop
What's important to note for this configuration is that, in fluxbox, the Desktop is an actual named layer that is below everything including the Normal layer (Normal is where open windows are sitting as you're working).
This key binding will provide (toggle actually) the typical show desktop functionality:
Mod1 F12 :ToggleCmd {ShowDesktop} {DeIconify all originquiet}
so Alt-F12 will show desktop, Alt-F12 again will return the windows to their previous positions.
However, since Desktop is a layer, what the ShowDesktop command actually does is iconify all windows that are not residing on the Desktop layer, or docked in the slit (the upper conky in these screenshots) - this includes conky windows which typically reside on the bottom layer of a window manager (Bottom is layer 10):
(http://s21.postimg.org/qqew8rx37/fluxbox_one.png) (http://postimg.org/image/qqew8rx37/) (http://s21.postimg.org/t90l9gitf/July_1436058167_1600x900.jpg) (http://postimg.org/image/t90l9gitf/)
If you want conky (or another app) to remain open when ShowDesktop is invoked, use the ~/.fluxbox/apps file to place those windows on the Desktop Layer (12).
For conky, in the ~/.fluxbox/apps:
[app] (name=Conky) (class=Conky)
[Layer] {12}
[end]
and conky windows will remain visible when ShowDesktop is invoked. For conky, this can be refined further by using the:
own_window_class <some class name>
own_window_title <some title name>
in the conkyrc to give each conky a unique class and name. The ~/.fluxbox/apps file can then be configured for individual conky windows.
Thanks these tips, PackRat.
Discovered fluxbox has key modes. (http://fluxbox-wiki.org/category/howtos/en/Keymodes.html)
Key modes are a method to extend your keybindings. To check them out, I used the wiki example to set up move and resize modes -
# MoveMode
Mod4 w Mod4 m :KeyMode MoveMode
MoveMode: None Up :MoveUp 5
MoveMode: None Down :MoveDown 5
MoveMode: None Left :MoveLeft 5
MoveMode: None Right :MoveRight 5
MoveMode: Shift Up :MoveUp 10
MoveMode: Shift Down :MoveDown 10
MoveMode: Shift Left :MoveLeft 10
MoveMode: Shift Right :MoveRight 10
# ResizeMode
Mod4 w Mod4 r :KeyMode ResizeMode
ResizeMode: None Up :ResizeVertical -5
ResizeMode: None Down :ResizeVertical 5
ResizeMode: None Left :ResizeHorizontal -5
ResizeMode: None Right :ResizeHorizontal 5
ResizeMode: Shift Up :MacroCmd {ResizeTo 50% 50%} {MoveTo 0 0 UpperLeft}
ResizeMode: Shift Down :MacroCmd {ResizeTo 50% 50%} {MoveTo 0 0 UpperRight}
ResizeMode: Shift Left :MacroCmd {ResizeTo 50% 50%} {MoveTo 0 0 LowerLeft}
ResizeMode: Shift Right :MacroCmd {ResizeTo 50% 50%} {MoveTo 0 0 LowerRight}
Very handy. Have to remember to ESC (default key) to exit the mode.
scrot or it didn't happen -
(http://s17.postimg.org/qunpi99i3/resize_mose.jpg) (http://postimg.org/image/qunpi99i3/)
i3 has this feature, and I think pekwm. Not sure of any others.
Huh, got this wiki page in my FB documentation folder some time ago, but never went through it... Thanks for the reminder. Time to learn a bit more.
BTW, Do you ever sleep? :P
I have 2 kids and a year old dog. So no. :D
Aaaah... truly a non ideal environment for peaceful sleeping. Please, forward my compliments to your kids and hyperactive dog for keeping you awake and restless in our benefit. :D
Hello, at the request of PackRat, I'm posting how to use bbpager with Flux:
install bbpager and wmctrl and put the following two lines in the startup file before exec fluxbox:
(sleep 1s && bbpager) &
(sleep 2s && wmctrl -r bbpager -b add,below) &
screenshot (upper left hand corner) http://vsido.org/index.php?topic=1014.msg11748#msg11748
colors are a little dim in the screenshot, but it works very nicely
Couple shots of fluxbox -
(http://en.zimagez.com/miniature/august14720894461600x900.jpg) (http://en.zimagez.com/zimage/august14720894461600x900.php) (http://en.zimagez.com/miniature/scrot-shot-wed241472088904.jpg) (http://en.zimagez.com/zimage/scrot-shot-wed241472088904.php)
One thing fluxbox is missing out of the box is a pager - fbpager and obpager are still in the repos, but no longer developed, and have some limits aesthetically. Since Vsido uses tint2 by default, it's easy enough to configure tint2 to display multiple desktops and get pager functionality that way. But, if you don't want to run a 3rd party application, limited pager capability can be quickly set up by configuring the fluxbox Iconbar.
By default, the Iconbar is enabled and set to show all the windows on the active workspace. A quick look at the configuration options in the menu (screenshot) shows there are several other options available. Note that Icons refers to iconified windows, not the mini icon associated with an application. If you do not want to display the mini icons with the window in the iconbar, clear the "show pictures" option.
None - don't display the iconbar
Icons - only iconified windows, all workspaces
NoIcons - only open windows, all workspaces
WorkspaceIcons - iconified windows on active workspace
WorkspaceNoIcons - open windows on active workspace
Workspace - Open and iconified windows on active workspace
All Windows - Open and Iconified windows, all workspaces
Workspace is the default.
Changing to All Windows will display all the open and iconified windows on all desktops (file manager and gimp are open on Workspace 2 in the screenshot) and clicking on the application in the iconbar has two potential outcomes: If the window is open, you will switch to the workspace and the application window will be raised and focused. If the application window is iconified, it will be moved to the current workspace, raised and capture focus.
Unfortunately, unlike tint2 pager mode, only the current workspace is numbered on the fluxbox toolbar, so visually the user cannot tell which workspace the window actually occupies.
Update to the faux tiling, ToggleDecor key bindings -
(https://cdn.scrot.moe/images/2017/09/10/screen-import-Saturday_1505003613.th.png) (https://www.scrot.moe/image/6wTGv)
key bindings/chains to add to $HOME/.fluxbox/fluxbox-keys
! this will tile tint2 panel
!Mod1 Shift m :ArrangeWindowsHorizontal
!Mod1 Shift n :ArrangeWindowsVertical
Ctrl a Mod4 h :MacroCmd {ResizeTo 48% 98%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod4 j :MacroCmd {ResizeTo 48% 98%} {MoveTo 1% 1% UpperRight}
Ctrl a Mod4 k :MacroCmd {ResizeTo 98% 48%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod4 l :MacroCmd {ResizeTo 98% 48%} {MoveTo 1% 1% LowerLeft}
Ctrl a Mod4 v :MacroCmd {SetDecor BORDER} {ResizeTo 48% 98%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod4 b :MacroCmd {SetDecor BORDER} {ResizeTo 48% 98%} {MoveTo 1% 1% UpperRight}
Ctrl a Mod4 n :MacroCmd {SetDecor BORDER} {ResizeTo 98% 48%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod4 m :MacroCmd {SetDecor BORDER} {ResizeTo 98% 48%} {MoveTo 1% 1% LowerLeft}
Ctrl a Mod1 h :MacroCmd {ResizeTo 48% 48%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod1 j :MacroCmd {ResizeTo 48% 48%} {MoveTo 1% 1% UpperRight}
Ctrl a Mod1 k :MacroCmd {ResizeTo 48% 48%} {MoveTo 1% 1% LowerLeft}
Ctrl a Mod1 l :MacroCmd {ResizeTo 48% 48%} {MoveTo 1% 1% LowerRight}
Ctrl a Mod1 v :MacroCmd {SetDecor BORDER} {ResizeTo 48% 48%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod1 b :MacroCmd {SetDecor BORDER} {ResizeTo 48% 48%} {MoveTo 1% 1% UpperRight}
Ctrl a Mod1 n :MacroCmd {SetDecor BORDER} {ResizeTo 48% 48%} {MoveTo 1% 1% LowerLeft}
Ctrl a Mod1 m :MacroCmd {SetDecor BORDER} {ResizeTo 48% 48%} {MoveTo 1% 1% LowerRight}
Ctrl a Mod4 c :MacroCmd {SetDecor 0x66f} {ResizeTo 85% 95%} {MoveTo 0 0 Center}
Ctrl a Mod4 x :MacroCmd {SetDecor BORDER} {ResizeTo 85% 95%} {MoveTo 0 0 Center}
# Ctrl a Mod4 d :ToggleDecor
Mod1 Shift F12 :MacroCmd {SetDecor TAB}
Mod1 Shift d :ToggleCmd {ShowDesktop} {DeIconify all originquiet}
never ending modifications - added some chains to undecorate and tile:
# manual tiling with key chains - using chains to avoid clash with keybindings #
! this will tile tint2 panel
!Mod1 Shift m :ArrangeWindowsHorizontal
!Mod1 Shift n :ArrangeWindowsVertical
Ctrl a Mod4 h :MacroCmd {ResizeTo 48% 98%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod4 j :MacroCmd {ResizeTo 48% 98%} {MoveTo 1% 1% UpperRight}
Ctrl a Mod4 k :MacroCmd {ResizeTo 98% 48%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod4 l :MacroCmd {ResizeTo 98% 48%} {MoveTo 1% 1% LowerLeft}
Ctrl a Mod4 v :MacroCmd {SetDecor BORDER} {ResizeTo 48% 98%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod4 b :MacroCmd {SetDecor BORDER} {ResizeTo 48% 98%} {MoveTo 1% 1% UpperRight}
Ctrl a Mod4 n :MacroCmd {SetDecor BORDER} {ResizeTo 98% 48%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod4 m :MacroCmd {SetDecor BORDER} {ResizeTo 98% 48%} {MoveTo 1% 1% LowerLeft}
Ctrl a Mod1 h :MacroCmd {ResizeTo 48% 48%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod1 j :MacroCmd {ResizeTo 48% 48%} {MoveTo 1% 1% UpperRight}
Ctrl a Mod1 k :MacroCmd {ResizeTo 48% 48%} {MoveTo 1% 1% LowerLeft}
Ctrl a Mod1 l :MacroCmd {ResizeTo 48% 48%} {MoveTo 1% 1% LowerRight}
Ctrl a Mod1 v :MacroCmd {SetDecor BORDER} {ResizeTo 48% 48%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod1 b :MacroCmd {SetDecor BORDER} {ResizeTo 48% 48%} {MoveTo 1% 1% UpperRight}
Ctrl a Mod1 n :MacroCmd {SetDecor BORDER} {ResizeTo 48% 48%} {MoveTo 1% 1% LowerLeft}
Ctrl a Mod1 m :MacroCmd {SetDecor BORDER} {ResizeTo 48% 48%} {MoveTo 1% 1% LowerRight}
Ctrl a Mod4 c :MacroCmd {SetDecor 0x66f} {ResizeTo 85% 95%} {MoveTo 0 0 Center}
Ctrl a Mod4 x :MacroCmd {SetDecor BORDER} {ResizeTo 85% 95%} {MoveTo 0 0 Center}
# Ctrl a Mod4 d :ToggleDecor
Mod1 Shift F12 :MacroCmd {SetDecor TAB}
Mod1 Shift d :ToggleCmd {ShowDesktop} {DeIconify all originquiet}
Current key bindings for tiling - makes use of the key pad on this laptop, no numlock is stated (numlockx in the ~/.fluxbox/startup)
# manual tiling with key chains - using chains to avoid clash with keybindings #
! this will tile tint2 panel
!Mod1 Shift m :ArrangeWindowsHorizontal
!Mod1 Shift n :ArrangeWindowsVertical
Ctrl a Mod4 h :MacroCmd {ResizeTo 48% 98%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod4 j :MacroCmd {ResizeTo 48% 98%} {MoveTo 1% 1% UpperRight}
Ctrl a Mod4 k :MacroCmd {ResizeTo 98% 48%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod4 l :MacroCmd {ResizeTo 98% 48%} {MoveTo 1% 1% LowerLeft}
Ctrl a Mod4 KP_4 :MacroCmd {SetDecor BORDER} {ResizeTo 48% 98%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod4 KP_6 :MacroCmd {SetDecor BORDER} {ResizeTo 48% 98%} {MoveTo 1% 1% UpperRight}
Ctrl a Mod4 KP_8 :MacroCmd {SetDecor BORDER} {ResizeTo 98% 48%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod4 KP_2 :MacroCmd {SetDecor BORDER} {ResizeTo 98% 48%} {MoveTo 1% 1% LowerLeft}
Ctrl a Mod1 h :MacroCmd {ResizeTo 48% 48%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod1 j :MacroCmd {ResizeTo 48% 48%} {MoveTo 1% 1% UpperRight}
Ctrl a Mod1 k :MacroCmd {ResizeTo 48% 48%} {MoveTo 1% 1% LowerLeft}
Ctrl a Mod1 l :MacroCmd {ResizeTo 48% 48%} {MoveTo 1% 1% LowerRight}
Ctrl a Mod1 KP_7 :MacroCmd {SetDecor BORDER} {ResizeTo 48% 48%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod1 KP_9 :MacroCmd {SetDecor BORDER} {ResizeTo 48% 48%} {MoveTo 1% 1% UpperRight}
Ctrl a Mod1 KP_1 :MacroCmd {SetDecor BORDER} {ResizeTo 48% 48%} {MoveTo 1% 1% LowerLeft}
Ctrl a Mod1 KP_3 :MacroCmd {SetDecor BORDER} {ResizeTo 48% 48%} {MoveTo 1% 1% LowerRight}
Ctrl a Mod1 KP_8 :MacroCmd {ResizeTo 70% 48%} {MoveTo 0% 1% Top}
Ctrl a Mod1 KP_2 :MacroCmd {ResizeTo 70% 48%} {MoveTo 0% 1% Bottom}
Ctrl a Mod4 c :MacroCmd {SetDecor 0x66f} {ResizeTo 85% 95%} {MoveTo 0 0 Center}
Ctrl a Mod4 x :MacroCmd {SetDecor BORDER} {ResizeTo 85% 95%} {MoveTo 0 0 Center}
Ctrl a Mod1 F12 :ToggleDecor
Mod1 Shift F12 :MacroCmd {SetDecor TAB}
Mod1 Shift d :ToggleCmd {ShowDesktop} {DeIconify all originquiet}
Mod1 Shift F10 :MacroCmd {ToggleDecor} {Maximize}
Was reading through the man page for fluxbox to look for something I spotted in the ~/.fluxbox/init file (the fluxbox resource file) and I came across this:
Quotesession.titlebar.{left|right}: buttons
The buttons or icons to place in the titlebar of decorated windows.
You may specify any number, space-delimited.
The available options are:
Close Maximize MenuIcon Minimize Shade Stick LHalf RHalf
Default left: Stick
Default right: Shade Minimize Maximize Close
LHalf and RHalf are buttons to quickly place a window into the left
and right half of the current monitor.
I never knew abouit the LHalf and RHalf buttons before; I've seen lhalf.pixmap and rhalf.pixmap settings in themes before, but thought it was a reference to the window.
So I checked them out, and sure enough it's a button to tile left/right on the screen:
(https://cdn.scrot.moe/images/2018/03/15/fluxbox_tile.th.png) (https://scrot.moe/image/6S1ry)
Unfortunately, they do not toggle like the Maximize, Shade, and Stick button do so the use is limited. Still, and interesting feature of fluxbox.
Revisited faux tiling. Fluxbox supports key binding modes like i3, so set up some faux tiling grids:
(https://cdn.scrot.moe/images/2019/06/27/scrot-shot-June_27_1561651511.th.png) (https://www.scrot.moe/image/xPEMb)
pertinent section of the ~/.fluxbox/keys file for regular tiling and the move mode
## manual tiling with key chains
##=================================================##
# built-in tiling in fluxbox
# these macros will tile tint2 and polybar panel
# ArangeWindows
# Mod1 Shift m :ArrangeWindowsHorizontal
# Mod1 Shift n :ArrangeWindowsVertical
# ArrangeWindowsStackRight
# ArrangeWindowsStackLeft
# ArrangeWindowsStackTop
# ArrangeWindowsStackBottom
# Quarter screen decorated
#===================================================##
#Ctrl a Mod1 KP_7 :MacroCmd {SetDecor 0x67f} {ResizeTo 50% 50%} {MoveTo 0 0 UpperLeft}
#Ctrl a Mod1 KP_9 :MacroCmd {ResizeTo 50% 50%} {MoveTo 0 0 UpperRight}
#Ctrl a Mod1 KP_1 :MacroCmd {ResizeTo 50% 50%} {MoveTo 0 0 LowerLeft}
#Ctrl a Mod1 KP_3 :MacroCmd {ResizeTo 50% 50%} {MoveTo 0 0 LowerRight}
#Ctrl a Mod1 KP_4 :MacroCmd {ResizeTo 50% 100%} {MoveTo 0 0 Left}
#Ctrl a Mod1 KP_6 :MacroCmd {ResizeTo 50% 100%} {MoveTo 0 0 Right}
#Ctrl a Mod1 KP_8 :MacroCmd {ResizeTo 100% 50%} {MoveTo 0 0 Top}
#Ctrl a Mod1 KP_2 :MacroCmd {ResizeTo 100% 50%} {MoveTo 0 0 Bottom}
#Ctrl a Mod1 KP_5 :Maximize
Ctrl a Mod1 KP_7 :MacroCmd {SetDecor 0x67f} {ResizeTo 48% 48%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod1 KP_9 :MacroCmd {SetDecor 0x67f} {ResizeTo 48% 48%} {MoveTo 1% 1% UpperRight}
Ctrl a Mod1 KP_1 :MacroCmd {SetDecor 0x67f} {ResizeTo 48% 48%} {MoveTo 1% 1% LowerLeft}
Ctrl a Mod1 KP_3 :MacroCmd {SetDecor 0x67f} {ResizeTo 48% 48%} {MoveTo 1% 1% LowerRight}
Ctrl a Mod1 KP_4 :MacroCmd {SetDecor 0x67f} {ResizeTo 48% 98%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod1 KP_6 :MacroCmd {SetDecor 0x67f} {ResizeTo 48% 98%} {MoveTo 1% 1% UpperRight}
Ctrl a Mod1 KP_8 :MacroCmd {SetDecor 0x67f} {ResizeTo 98% 48%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod1 KP_2 :MacroCmd {SetDecor 0x67f} {ResizeTo 98% 48%} {MoveTo 1% 1% LowerLeft}
Ctrl a Mod1 KP_5 :MacroCmd {SetDecor 0x67f} {ResizeTo 98% 98%} {MoveTo 0 0 Center}
# Quarter screen undecorated
##===================================================##
Ctrl a Mod4 KP_7 :MacroCmd {SetDecor BORDER} {ResizeTo 48% 48%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod4 KP_9 :MacroCmd {SetDecor BORDER} {ResizeTo 48% 48%} {MoveTo 1% 1% UpperRight}
Ctrl a Mod4 KP_1 :MacroCmd {SetDecor BORDER} {ResizeTo 48% 48%} {MoveTo 1% 1% LowerLeft}
Ctrl a Mod4 KP_3 :MacroCmd {SetDecor BORDER} {ResizeTo 48% 48%} {MoveTo 1% 1% LowerRight}
Ctrl a Mod4 KP_4 :MacroCmd {SetDecor BORDER} {ResizeTo 48% 98%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod4 KP_6 :MacroCmd {SetDecor BORDER} {ResizeTo 48% 98%} {MoveTo 1% 1% UpperRight}
Ctrl a Mod4 KP_8 :MacroCmd {SetDecor BORDER} {ResizeTo 98% 48%} {MoveTo 1% 1% UpperLeft}
Ctrl a Mod4 KP_2 :MacroCmd {SetDecor BORDER} {ResizeTo 98% 48%} {MoveTo 1% 1% LowerLeft}
Ctrl a Mod4 KP_5 :MacroCmd {SetDecor BORDER} {ResizeTo 98% 98%} {MoveTo 0 0 Center}
Ctrl a Mod1 KP_0 :MacroCmd {SetDecor 0x67f} {ResizeTo 80% 98%} {MoveTo 0 0 Center}
Ctrl a Mod4 KP_0 :MacroCmd {SetDecor BORDER} {ResizeTo 80% 98%} {MoveTo 0 0 Center}
Ctrl Mod1 KP_7 :MoveTo 1% 1% UpperLeft
Ctrl Mod1 KP_8 :MoveTo 1% 1% TopCenter
Ctrl Mod1 KP_9 :MoveTo 1% 1% UpperRight
Ctrl Mod1 KP_4 :MoveTo 1% 1% LeftCenter
Ctrl Mod1 KP_5 :MoveTo 0 0 Center
Ctrl Mod1 KP_6 :MoveTo 1% 1% RightCenter
Ctrl Mod1 KP_1 :MoveTo 1% 1% LowerLeft
Ctrl Mod1 KP_2 :MoveTo 1% 1% BottomCenter
Ctrl Mod1 KP_3 :MoveTo 1% 1% LowerRight
Shift Mod1 KP_7 :MoveTo 0 0 UpperLeft
Shift Mod1 KP_8 :MoveTo 0 0 TopCenter
Shift Mod1 KP_9 :MoveTo 0 0 UpperRight
Shift Mod1 KP_4 :MoveTo 0 0 LeftCenter
Shift Mod1 KP_5 :MoveTo 0 0 Center
Shift Mod1 KP_6 :MoveTo 0 0 RightCenter
Shift Mod1 KP_1 :MoveTo 0 0 LowerLeft
Shift Mod1 KP_2 :MoveTo 0 0 BottomCenter
Shift Mod1 KP_3 :MoveTo 0 0 LowerRight
# modes - use ESC to exit mode
# MoveMode ===========================================##
Ctrl w Mod4 m :KeyMode MoveMode
MoveMode: Ctrl KP_7 :MacroCmd {ResizeTo 33% 33%} {MoveTo 1% 1% UpperLeft}
MoveMode: Ctrl KP_8 :MacroCmd {ResizeTo 33% 33%} {MoveTo 1% 1% TopCenter}
MoveMode: Ctrl KP_9 :MacroCmd {ResizeTo 33% 33%} {MoveTo 1% 1% UpperRight}
MoveMode: Ctrl KP_4 :MacroCmd {ResizeTo 33% 33%} {MoveTo 1% 1% LeftCenter}
MoveMode: Ctrl KP_5 :MacroCmd {ResizeTo 33% 33%} {MoveTo 1% 1% Center}
MoveMode: Ctrl KP_6 :MacroCmd {ResizeTo 33% 33%} {MoveTo 1% 1% RightCenter}
MoveMode: Ctrl KP_1 :MacroCmd {ResizeTo 33% 33%} {MoveTo 1% 1% LowerLeft}
MoveMode: Ctrl KP_2 :MacroCmd {ResizeTo 33% 33%} {MoveTo 1% 1% BottomCenter}
MoveMode: Ctrl KP_3 :MacroCmd {ResizeTo 33% 33%} {MoveTo 1% 1% LowerRight}
MoveMode: Shift KP_7 :MacroCmd {ResizeTo 36% 48%} {MoveTo 1% 1% UpperLeft}
MoveMode: Shift KP_8 :MacroCmd {ResizeTo 60% 48%} {MoveTo 1% 1% TopCenter}
MoveMode: Shift KP_9 :MacroCmd {ResizeTo 36% 48%} {MoveTo 1% 1% UpperRight}
MoveMode: Shift KP_4 :MacroCmd {ResizeTo 60% 98%} {MoveTo 1% 1% UpperLeft}
MoveMode: Shift KP_5 :MacroCmd {ResizeTo 60% 98%} {MoveTo 0 0 Center}
MoveMode: Shift KP_6 :MacroCmd {ResizeTo 60% 98%} {MoveTo 1% 1% UpperRight}
MoveMode: Shift KP_1 :MacroCmd {ResizeTo 36% 48%} {MoveTo 1% 1% LowerLeft}
MoveMode: Shift KP_2 :MacroCmd {ResizeTo 60% 48%} {MoveTo 1% 1% BottomCenter}
MoveMode: Shift KP_3 :MacroCmd {ResizeTo 36% 48%} {MoveTo 1% 1% LowerRight}
Entering a mode is like a key chain, ESC exits the mode.
Unfortunately, other key bindings like ALT - Tab window switching is suspended when in a mode, but selecting, moving etc .. with the mouse still appear to work.
Fluxbox on dual monitors -
(https://scrot.cloud/images/2021/02/03/2021-02-03-09-07-56.md.png) (https://scrot.cloud/image/B6n1q) link to image (https://scrot.cloud/images/2021/02/03/2021-02-03-09-07-56.png)
(https://scrot.cloud/images/2021/02/03/2021-02-03-09-10-46.md.png) (https://scrot.cloud/image/B6mxJ) link to image (https://scrot.cloud/images/2021/02/03/2021-02-03-09-10-46.png)
Wife has been working from home for about a year due to the plague. At her office, she uses dual monitors so went out and got a second monitor a couple months ago. Unfortunately, fluxbox does not support different workspaces on different monitors (that I'm aware of; if this can be done please share!). However, the toolbar and iconbar can span the monitors in a dual monitor setup:
Fluxbox Menu --> Configure --> Toolbar --> On Head --> All Heads.
Other than having to look to the right to see the clock and system tray not a whole lot of difference for me.