unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: scratch/icons 09509f4fa1 05/11: Import Material design icons
Date: Wed, 24 Aug 2022 18:40:53 +0800	[thread overview]
Message-ID: <87sfll2abu.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkmmQEFTXUqZKQzB07BOTdrL4q-ce9EUXOgdofs0feuJwDw@mail.gmail.com> (Stefan Kangas's message of "Wed, 24 Aug 2022 00:06:36 -0700")

Stefan Kangas <stefankangas@gmail.com> writes:

> There should be some kind of fallback for when SVG is not available,
> yes.  I'm not yet sure exactly what that will look like.  The problem
> with generating PBM versions AFAIK is that they don't scale, so maybe
> we'd want to prefer Unicode symbols in those cases (or even emojis,
> though I'm not exactly a huge fan).

We cannot put symbols in the tool bar, AFAIK.  (And what if no such
Unicode font exists, which is the situation under the xfont backend and
Windows 9X for most Unicode Emoji?)

I think relying on the normal, primitive, scaling is fine, should SVG
support not be available.  Modern systems that can display the Unicode
symbols will also be able to run librsvg.

> We don't need to have any different variants: the svg icons will use
> whatever foreground/background the current face has.

No, what I meant was to provide icons that have contrasting colors.
This makes the icons easier to visually identify.  For an example of
this, see how spell.xpm has a green checkmark put up against black text,
which makes it easier to spot in the toolbar than similar icons in an
Android program that uses single-color icons.

Thanks.



  reply	other threads:[~2022-08-24 10:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <166132324164.29491.8702393664945861865@vcs2.savannah.gnu.org>
     [not found] ` <20220824064044.65239C0088A@vcs2.savannah.gnu.org>
2022-08-24  6:45   ` scratch/icons 09509f4fa1 05/11: Import Material design icons Po Lu
2022-08-24  7:06     ` Stefan Kangas
2022-08-24 10:40       ` Po Lu [this message]
2022-08-24 11:28         ` Eli Zaretskii
2022-08-24 12:05           ` Po Lu
2022-08-24 12:11             ` Lars Ingebrigtsen
2022-08-24 12:28               ` Po Lu
2022-08-24 23:09                 ` Stefan Kangas
2022-08-24 12:21             ` Eli Zaretskii
2022-08-24 12:38               ` Po Lu
2022-08-24 12:09       ` Stefan Monnier
2022-08-24 12:28         ` Eli Zaretskii
     [not found] ` <20220824064044.DC0C2C0088A@vcs2.savannah.gnu.org>
2022-08-24  6:46   ` scratch/icons 67251e79f7 09/11: Use material icons in mpc toolbar Po Lu
2022-08-24  7:21     ` Stefan Kangas
     [not found] ` <20220824064044.B7530C0088A@vcs2.savannah.gnu.org>
2022-08-24  6:50   ` scratch/icons 4de626ea22 08/11: Support using icons.el in toolbar Po Lu
2022-08-24  7:20     ` Stefan Kangas
2022-08-24 10:31       ` Po Lu
2022-08-24 12:07     ` Stefan Monnier
2022-08-24 12:27       ` Po Lu

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=87sfll2abu.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --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).