On 2005-05-17, David Tweed <[EMAIL PROTECTED]> wrote: > Obviously with an average of 12 clients per frame it's > often impossible to read anything distinctive in the > tabs due to the small space. I've played around with > pull-down menus listing all available windows but > never really got anything that didn't give a huge long > list of windows to read.
A version of wcirculate that lists only windows (or other objects) ina particular frame (in a menu in the frame) might be useful, at least for displaying full titles. <http://iki.fi/tuomov/repos/ion-scripts-3/scripts/wcirculate.lua> In its current form it displays a list of client windows in order of activation history (next most recent first) in a "grabbed menu" that is closed once all modifier keys have been released and that can only be cycled with a given key. Numbered entries might improve it for this purpose. If you have groups of windows with rather similar names, another interesting thing to try would involve what I call flattened submenus. Normally submenus look like ----------- | Foosub1 | ---------- Foosub2 | | Foo -> |---------- | Bar -> | ---------- Flattened submenus would look as follows ------------------- | Foo -> Foosub1 | | Foosub2 | | Bar -> Barsub1 | | Barsub2 | | Barsub3 | ------------------- Navigation would be similar to normal menus until a submenu is activated. Going down or up in a submenu beyond its limits would, however wrap to the next entry or its submenu. All submenus are always visible; flattened submenus are not practical for _huge_ menus (but then again, menus in general are not), but I believe all entries being visible they would be nicer to navigate for some purposes than normal submenus, and since you can quickly skip from Foo to Bar, they're faster than a plain flat menu. Of course, flattened submenus require more work than just a simple script, and if your windows don't have descriptive titles, no textual menus are going to help. -- Tuomo
