Hi,

Here's my personal list of whishes which came up during usage of
this great WM. I thought about implementing them for myself but never
had the time. Maybe some of them are already implemented, but i don't
follow the changes all the time ...

- I would like to define a static frame layout (i.e. frame sizes) for each
  workspace which i can restore with a defined key.

  Background:
  I have configured workspaces for various types of applications
  which are more or less complex. Often i need to temorarily
  resize certain frames, but eventually switch back to the
  original layout. It would be much easier to do this
  by just pressing a key.

  An additional function needs to be present to store the current layout
  of a workspace to the workspaces.lua file.

- The minimize horizontally operation currently decreases the
  size of the frames to be hidden. Instead it should work line
  minimize vertically (at least i think it's done that way), i.e.
  the hidden clients should remain the same size, but just be invisible.

  Background:
  Some applications (like terminals) produce unreadable screen contents
  when something new is written into the window while it is minimized.
  Some even crash (try opening a Solaris dtterm into a minimized frame).

Furthermore, when a frame is minimized and i exit ion, the size is stored
into workspaces.lua. When i start ion again, the frame comes up minimized,
which is not very convenient.


- Implement key binding for double-click.

  Example: pressing a key once does a "bring window to front", pressing
  twice (within a given period of time) sends it to the back.
  I think this would decrease the number of required keys and modifiers.

- Specify directions in a winprop's "target" stemement instead of frame names.

Example: target="@west" opens the client on the frame left of the current one.

Background:
I have applications for which i created tons of winprops so that all windows
appear in specific frames of a specific workspace. Problem: it's not possible
to start a second instance of this applicationon in a second screen, since all
windows are sent to the same frame as defined in the kludges file.


Since most screen layouts usually contain 3 or 4 frames (at least for me),
each of them can be addressed using directions regardless which one is currently
active.


Cheers,

Felix.

Reply via email to