[Fluxbox-users] ClientMenu structure

[Thomas Lübking]

I'd like to ask about (strong) positions regarding the structure of the Client
menu.

Right now, every window is "stashed" in a submenu - either of the
assigned workspace or the one for iconified windows.
The only direct (and somehow most prominent) items are those to edit the
workspaces - something I personally do rather seldom ;-)

I wonder whether it would be considered feasible to list the windows of
the current workspace in the top level menu - maybe even all if the
total amount of windows is "rather low™" (eg. < 17)?

The other aspect is the collection of the iconified windows.
This crosses workspace assignments, so if you've eg. a minimized xterm
on every workspace, finding the one on the present workspace is a rather
nasty hide-and-seek game (depending on how unique the title is)
In addition, windows are always de-iconified on the current workspace,
ie. unminimizing implies a setup change, rather than a workspace
switch.

Wrt. to the flattening, I'd rather list them under their workspace,
indicating their state (by theme or pre/suffix) and use the same
behavior for selecting iconified and not iconified windows (switch to
their workspace rather than changing _NET_WM_DESKTOP.

This however isn't relevant enough to me to keep around conflict prone
local only commits ;-)

Cheers,
Thomas

------------------------------------------------------------------------------

[Alessandro DE LAURENZIS]

Hello Thomas,

On Tue, 16 Aug 2016 21:31:01 +0200

Post by Thomas Lübking
I'd like to ask about (strong) positions regarding the structure of
the Client menu.
Right now, every window is "stashed" in a submenu - either of the
assigned workspace or the one for iconified windows.
The only direct (and somehow most prominent) items are those to edit
the workspaces - something I personally do rather seldom ;-)
I wonder whether it would be considered feasible to list the windows
of the current workspace in the top level menu - maybe even all if the
total amount of windows is "rather low™" (eg. < 17)?
The other aspect is the collection of the iconified windows.
This crosses workspace assignments, so if you've eg. a minimized xterm
on every workspace, finding the one on the present workspace is a
rather nasty hide-and-seek game (depending on how unique the title is)
In addition, windows are always de-iconified on the current workspace,
ie. unminimizing implies a setup change, rather than a workspace
switch.
Wrt. to the flattening, I'd rather list them under their workspace,
indicating their state (by theme or pre/suffix) and use the same
behavior for selecting iconified and not iconified windows (switch to
their workspace rather than changing _NET_WM_DESKTOP.

I consider the current ClientMenu scheme a real weakness; the structure
you're proposing makes much more sense.

So: yes, please!