unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Dmitry Gutov <dgutov@yandex.ru>,
	angelo.g0@libero.it, emacs-devel@gnu.org
Subject: references for usability - Re: Adding icon sets to Emacs -- and next steps for icons.el
Date: Wed, 7 Sep 2022 22:18:44 +0300	[thread overview]
Message-ID: <YxjulNLc3G5Mug4a@protected.localdomain> (raw)
In-Reply-To: <CADwFkmkfB8P2rSe+fUFc4Ypgr50JkxvoepVzMVq6qowHsb52rQ@mail.gmail.com>

* Stefan Kangas <stefankangas@gmail.com> [2022-08-25 02:10]:
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > But "the new one" looks black-and-white here?  I doubt losing colors
> > is going to be loved.
> 
> There is still color: we just use a single one (black).  All in all,
> black is not necessarily a bad choice: the text I'm reading now is
> black, as is the text in any paperback book.
> 
> But we do go from one distinct style to another.  This is true.  It is
> inevitable that some people will love a change like this, while others
> will hate it.  Others will probably be indifferent.

Usability 101: Introduction to Usability
https://www.nngroup.com/articles/usability-101-introduction-to-usability/

Usability Testing 101
https://www.nngroup.com/articles/usability-testing-101/

How Many Test Users in a Usability Study?
https://www.nngroup.com/articles/how-many-test-users/


-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



  parent reply	other threads:[~2022-09-07 19:18 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24 12:43 Adding icon sets to Emacs -- and next steps for icons.el Angelo Graziosi
2022-08-24 13:05 ` Dmitry Gutov
2022-08-24 13:22   ` Eli Zaretskii
2022-08-24 13:26     ` Visuwesh
2022-08-24 14:19       ` Eli Zaretskii
2022-08-24 14:32         ` Visuwesh
2022-08-24 16:23         ` Stefan Monnier
2022-08-24 16:34           ` Eli Zaretskii
2022-08-25  1:11       ` Po Lu
2022-08-25  1:35         ` Visuwesh
2022-08-24 13:36     ` Po Lu
2022-08-24 13:51       ` Angelo Graziosi
2022-08-24 16:40       ` Stefan Kangas
2022-08-24 13:46     ` Angelo Graziosi
2022-08-24 13:47     ` Dmitry Gutov
2022-08-24 13:58       ` Po Lu
2022-08-24 14:26         ` Dmitry Gutov
2022-08-25  1:10           ` Po Lu
2022-08-25  1:22             ` Dmitry Gutov
2022-08-25  2:34               ` Po Lu
2022-08-24 23:09     ` Stefan Kangas
2022-08-25  1:23       ` Po Lu
2022-08-25  5:39         ` Eli Zaretskii
2022-08-25  6:49           ` Po Lu
2022-08-25 11:01       ` Visuwesh
2022-09-07 20:03         ` Jean Louis
2022-09-08  8:18           ` Po Lu
2022-09-08  8:25             ` Dmitry Gutov
2022-09-08  8:37             ` Jean Louis
2022-09-08 10:38               ` Po Lu
2022-08-25 21:26       ` Rudolf Adamkovič
2022-09-08 11:00         ` Jean Louis
2022-09-09 11:04           ` Rudolf Adamkovič
2022-09-07 19:18       ` Jean Louis [this message]
2022-08-25  9:28   ` Lars Ingebrigtsen
2022-09-07 19:11 ` Jean Louis

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YxjulNLc3G5Mug4a@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=angelo.g0@libero.it \
    --cc=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stefankangas@gmail.com \
    /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 public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).