all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: John Yates <john@yates-sheets.org>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: Taming some chaos
Date: Fri, 16 Oct 2015 18:36:58 +0300	[thread overview]
Message-ID: <5621199A.1030109@yandex.ru> (raw)
In-Reply-To: <CAJnXXohZUPzRrS1rpHtgAfs1ZjZnVG9_TNt9Hbe_yHH3xOS21g@mail.gmail.com>

On 10/14/2015 02:47 PM, John Yates wrote:

> Window management
>
> Too many packages explicitly choreograph how windows are managed,
> where and when they should be split, where buffers should be displayed
> and whether or not any previous window configuration should be restored.
> Such logic is articulated in terms of detailed manipulation of a simplistic
>   "current-window / other-window" model no matter how poorly it maps to
> the user's actual configuration.  In essence such packages have taken on
> managing the presentation layer even when that is not their main focus.

I agree. One could point to display-buffer-alist, a third-party packages 
like shackle or popwin, but even then the user has to operate 
lower-level primitives of window management.

Some higher abstraction and UI would do us some good. But it's not like 
it's trivial to even design that.

> It does not have to be that way.  In the X world there are any number of
> window manages (both tiling and overlapping).  The overwhelming majority
> of applications run correctly irrespective of the user's choice of Wm.

X has it easier: each application usually gets its own frame. And they 
can have modal windows (there's nothing really corresponding to that in 
Emacs).

> Fonts and colors schemes
> ...

> Surely given Emacs' support for
> inheritance within the faces framework we should be able to introduce a
> vocabulary of basic concept faces from which packages then would be
> encouraged to inherit.

font-lock-*-face? And faces in lisp/faces.el, the list of which can be 
extended.

> Trying to wrestle that many faces into a coherent color scheme
> and trying to achieve any degree of commonality across packages is
> excruciating.  I have to believe there are members of our community who
> are familiar with color palette UX strategies and technologies (e.g. iPhone
> or Android Material style guidelines).  Hopefully someone will come forward
> and propose a model.  In my vision an Emacs user would choose a palette
> (likely along with a mapping of palette items to visual roles).

That would be nice as well.



  reply	other threads:[~2015-10-16 15:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 11:47 Taming some chaos John Yates
2015-10-16 15:36 ` Dmitry Gutov [this message]
2015-10-16 23:20 ` John Wiegley
2015-10-17 15:16   ` John Yates
2015-10-18  5:30     ` John Wiegley

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=5621199A.1030109@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=john@yates-sheets.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.