Multiple displays and display & dpi awareness in acme would make my day!
Multi-display looks easy - we just need handling for adding a new "row",
which is already handily abstracted.

Fitt's law aware mouse movement would be nice too, particularly on large
screens.  You could slightly "trap" the mouse on narrow edges (scroll bars
and resize edges in particular) when the mouse is moving slowly.  Probably
a pain to tune, but would make acme much easier to use on large screens.

Paul


On Wed, Mar 19, 2014 at 12:02 PM, Bakul Shah <bakul@bitblocks.com> wrote:

> On Wed, 19 Mar 2014 04:36:34 EDT Caleb Malchik <cmalchik@gmail.com> wrote:
> > For my project, I would build a tiling window manager similar to dwm
> > (what I use on Linux). I think a dwm-style interface that could be
> > controlled from the keyboard would provide a nice contrast to what we
> > already have with rio, and as we see from dwm the implementation of such
> > an interface needn't be complex. Development would involve modifying the
> > rio source code to implement the basic functions of a
> > tiling/keyboard-controlled window manager one by one.
>
> I will throw out some rio/acme related ideas. Hope people find
> them interesting enough to want to experiment.
>
> - display size aware (when attached to an external display vs
>   the builtin one of a laptop).
> - dpi aware (pick the right size font)
> - borderless windows (adjoining windows have different color)
>   (but edges are sensitive to resizing etc)
> - auto splitting of windows. The idea is to see if window size
>   fiddling can be minimized (ideally it should /learn/ personal
>   preferences)
> - allow the window with "focus" to be made much much larger to
>   help a user's focus (make other windows less distracting --
>   IIRC there was a web based spreadsheet that did that. Don't
>   recall its name).
> - allow windows to be scrolled in lockstep (in x, y or both
>   directions)
> - support for multiple displays
> - allow programmatic control of all this via a synthetic FS
>
> Not sure if there exists a usable unification of acme + rio
> but that would be nice.
>
>