The place where random ideas get written down and lost in time.

2023-07-29 - Thought of the Day: DWM on Automation Computers?

Category DEV

So first, let’s make this clear: DWM is both terribly good, and terribly bad.

  • Excellent small footprint and minimal functionality.
  • Keyboard only usage is both excellent yet terrible. I generally don’t remember the shortcuts except for the 3 main ones: Alt-S (new shell), Alt-1..9 to select a workspace, and Shift-Alt-1...9 to move a window to a workspace (they call them “tags”).
  • A lot of programs aren’t designed for the “full screen / forced tiling” approach and require some kind of floating windows to be usable.
  • DWM has basically one “window model”: a main shell, and a stack of secondary windows opening on the right of it. It’s really designed to have one shell per workspace.

My window manager of choice is LXDE. It’s very light in resources, and in features, yet it’s a “proper” window manager. I could do without the session manager aspect.

As a thought exercise, how would I use Consist with DWM?

  • I have 3 shells that start. Ideally they could be tiled on space 1.
  • JMRI needs 3 windows: JMRI main, WiThrottle, and Conductor.
    • JMRI main + WiThrottles could be tiled on space 2.
    • Conductor should be tiled on its own space. Is that possible, or does it need to be with the rest of the app?
  • When debugging, I like to have Conductor + the JMRI shell window together.
  • When resetting a failed automation, I like to have Conductor + 1 or 2 new JMRI Throttle windows together.

That’s the part where DWM starts to suck. It’s not designed for this kind of functionality.


 Generated on 2025-01-18 by Rig4j 0.1-Exp-f2c0035