On Mon, Feb 12, 2007 at 04:54:22PM -0500, Yannick Delbecque wrote: > > I came across another kind of situation where a horizontal layout is > preferable: audio editing. Most audio editors display samples > horizontally (I don't know why this have become the standard way),
Possibly the same reason we have widescreen movies, TVs, and monitors: our eyes are next to each other horizontally, not vertically, so our visual area is more like a flattened rectangle than a tall one. :-) > and I often need to have some terms opened with an audio editor on > the same view. It is thus natural to want to have the terms in a row > below or above the editor and the editor alone in its own row. I agree with this specifically, and in general that there are good uses for rows (I miss them from ion). It does seem to me that the proposed managed area solution, while nice from a "we don't have to complicate the codebase / usage model any further" point of view, is less than completely satisfactory. Too "ad hoc". If one felt that introducing rows complicated navigation too much, one could always simply not bind any keys to the relevant functions, thus effectively disabling rows altogether. Surely this is why we have such a programmable window manager: so it can be tweaked and customised for local preferences? One size will never fit all perfectly. -Andy -- Andy Gimblett Computer Science Department University of Wales Swansea http://www.cs.swan.ac.uk/~csandy/
