(25-08-2020, 09:14 AM)z3bra Wrote: The active window isn't necessarily the one that has focus. So as far as you're using wmctrl to perform an action, you should specify ":ACTIVE:" as the window name, rather than relying on `pfw` (and that's one less fork !). This would be more solid, and would fit your WM's philosophy better (fully EWMH controlled).

You're right, I'll use wmctrl's :ACTIVE: argument, as _NET_ACTIVE_WINDOW is supported and used by shod.

Yeah, dealing with tiling is a pita, particularly with the limitations imposed by wmutils (stateless, one event sending per time, the limitations of the shell-script language, etc). A tiling script will eventually become a giant behemoth when adding those variables I've cited. And dealing with different layouts is a problem mainly because of shell's lack of complex data structures. A binary tree division style tiling would be nearly impossible to maintain with wmutils. But, hey, maximization is an instance of tiling: the monocle layout, which is the simplest and most straightforward tiling layout.

As for using monitor information with wmutils, I've just found mmutils, that lists monitors, print their sizes and attributes, etc.

(24-08-2020, 09:43 PM)Ramiferous Wrote: Now I know I have much more reading to do, but I was shocked to see that this thread was still only on the first page! Can we bring this one back to life again as I am keen to try out wmutils, either as a stand alone window management or together with a wm such as cwm etc etc... But looking for advice, guidance, recommendations all that.

I think you should check out fyr's fwm, which is one of the most complete and coherent set of wmutils-based scripts I have found. You can use his scripts as a base for writing yours.

I think that using wmutils as a supplement for a simple wm (like cwm, windowchef and z3bra's glazier) is the way to start from.