From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] GSoC proposal: Alternative window system
Date: Wed, 19 Mar 2014 12:02:37 -0700 [thread overview]
Message-ID: <20140319190237.76425B827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Wed, 19 Mar 2014 04:36:34 EDT." <53295712.1050505@gmail.com>
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.
next prev parent reply other threads:[~2014-03-19 19:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 8:36 Caleb Malchik
2014-03-19 8:56 ` Bence Fábián
2014-03-19 9:01 ` Shane Morris
2014-03-19 13:46 ` Peter A. Cejchan
2014-03-19 14:13 ` Aram Hăvărneanu
2014-03-19 14:17 ` erik quanstrom
2014-03-19 15:00 ` Bence Fábián
2014-03-19 15:26 ` erik quanstrom
2014-03-19 15:35 ` Anthony Sorace
2014-03-19 15:38 ` erik quanstrom
2014-03-19 15:49 ` Anthony Sorace
2014-03-19 16:16 ` Jeff Sickel
2014-03-19 15:31 ` Anthony Sorace
2014-03-19 15:35 ` erik quanstrom
2014-03-19 16:16 ` Aram Hăvărneanu
2014-03-19 19:02 ` Bakul Shah [this message]
2014-03-20 0:05 ` Paul Lalonde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140319190237.76425B827@mail.bitblocks.com \
--to=bakul@bitblocks.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).