From: Yuan Fu <casouri@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: chad <yandros@gmail.com>,
"EMACS development team" <emacs-devel@gnu.org>,
"Clément Pit-Claudel" <cpitclaudel@gmail.com>,
"Yuri Khan" <yuri.v.khan@gmail.com>
Subject: Re: High-res Customize icons
Date: Wed, 22 Apr 2020 18:20:41 -0400 [thread overview]
Message-ID: <C49BE1B7-41B9-4B92-8BA0-17C70CA37090@gmail.com> (raw)
In-Reply-To: <87k127fd03.fsf@mail.linkov.net>
[-- Attachment #1: Type: text/plain, Size: 1459 bytes --]
>
> I see no alternative to current icons because ASCII art
> characters have own problems explained by Eli in
> https://lists.gnu.org/archive/html/emacs-devel/2019-09/msg00268.html
>
> This is why the tab-bar moved from Unicode characters to images,
> but another attempt to use SVG failed as was demonstrated in
> https://lists.gnu.org/archive/html/emacs-devel/2019-09/msg00414.html
>
> But in any case feel free to try other options.
>
> BTW, if you want to see a funny effect, try typing 'r' when point
> is on the arrow in the customize buffer - it will rotate the image :-)
>
> There are other image keys used in the customize buffer,
> e.g. '+' will zoom the image (function 'image-increase-size'),
> so maybe you could just increase image size instead of using
> 2x image files.
Aha, that’s pretty cool :-)
To be clear, I’m not looking for a larger icon, but one with higher resolution. “2x” basically means I make a 18x18 px image and render it in “9x9 size”, which looks better than a 9x9 image on a HiDPI screen. Maybe Apple can explain it better than I do: https://developer.apple.com/design/human-interface-guidelines/ios/icons-and-images/image-size-and-resolution/ <https://developer.apple.com/design/human-interface-guidelines/ios/icons-and-images/image-size-and-resolution/>. You can have a look at the images my previous message, the 9x9 one looks a bit fuzzy and the high-res one looks sharp.
Yuan
[-- Attachment #2: Type: text/html, Size: 2332 bytes --]
next prev parent reply other threads:[~2020-04-22 22:20 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 19:47 High-res Customize icons Yuan Fu
2020-04-22 2:23 ` Eli Zaretskii
2020-04-22 2:37 ` Clément Pit-Claudel
2020-04-22 5:47 ` chad
2020-04-22 12:24 ` Yuan Fu
2020-04-22 12:41 ` Yuri Khan
2020-04-22 13:54 ` Yuan Fu
2020-04-22 21:12 ` Juri Linkov
2020-04-22 22:20 ` Yuan Fu [this message]
2020-04-23 4:11 ` Werner LEMBERG
2020-04-23 14:52 ` Eli Zaretskii
2020-04-23 15:07 ` Clément Pit-Claudel
2020-04-23 17:49 ` Werner LEMBERG
2020-04-23 19:27 ` Eli Zaretskii
2020-04-23 19:35 ` Yuan Fu
2020-04-23 19:40 ` Eli Zaretskii
2020-04-23 19:59 ` Yuan Fu
2020-04-23 23:02 ` chad
2020-04-24 6:30 ` Eli Zaretskii
2020-04-24 11:00 ` Dmitry Gutov
2020-04-23 23:23 ` chad
2020-04-24 7:18 ` Eli Zaretskii
2020-04-25 3:30 ` Richard Stallman
2020-04-25 7:02 ` Eli Zaretskii
2020-04-25 12:37 ` Clément Pit-Claudel
2020-04-25 13:56 ` Eli Zaretskii
2020-04-22 13:35 ` Eli Zaretskii
2020-04-22 17:09 ` chad
2020-04-22 17:36 ` Eli Zaretskii
2020-04-22 18:28 ` chad
2020-04-22 18:38 ` Eli Zaretskii
2020-04-22 19:19 ` Yuan Fu
2020-04-22 19:28 ` Eli Zaretskii
2020-04-22 20:38 ` Yuan Fu
2020-05-01 13:46 ` Eli Zaretskii
2020-10-22 15:33 ` Yuan Fu
2020-10-23 16:39 ` Yuan Fu
2020-10-23 18:08 ` Eli Zaretskii
2020-10-27 19:17 ` Yuan Fu
2020-10-27 19:27 ` Eli Zaretskii
2020-10-27 22:26 ` Alan Third
2020-10-27 23:09 ` Yuan Fu
2020-10-28 0:05 ` Alan Third
2020-10-28 1:22 ` YAMAMOTO Mitsuharu
2020-10-29 5:31 ` Yuan Fu
-- strict thread matches above, loose matches on Subject: below --
2020-04-23 7:14 ndame
2020-04-23 7:25 ` ndame
2020-04-23 10:06 ` Stefan Kangas
2020-04-23 14:07 ` Stefan Kangas
2020-04-23 14:11 ` Stefan Kangas
2020-04-23 14:39 ` Clément Pit-Claudel
2020-04-23 14:46 ` Lars Ingebrigtsen
2020-04-23 15:00 ` Clément Pit-Claudel
2020-04-23 15:44 ` Stefan Monnier
2020-04-23 19:14 ` Eli Zaretskii
2020-04-23 20:33 ` Stefan Monnier
2020-04-24 6:51 ` Eli Zaretskii
2020-04-24 13:06 ` Stefan Monnier
2020-04-24 13:36 ` Eli Zaretskii
2020-04-24 15:13 ` Stefan Monnier
2020-04-24 15:46 ` Eli Zaretskii
2020-04-23 15:15 ` Eli Zaretskii
2020-04-23 15:17 ` Lars Ingebrigtsen
2020-04-23 16:40 ` Yuan Fu
2020-04-23 15:09 ` Eli Zaretskii
2020-04-23 16:19 ` Stefan Kangas
2020-04-23 16:35 ` Stefan Kangas
2020-04-23 15:08 ` Eli Zaretskii
2020-04-23 15:49 ` Clément Pit-Claudel
2020-04-23 16:34 ` Stefan Kangas
2020-04-23 19:56 ` Clément Pit-Claudel
2020-04-23 19:12 ` Eli Zaretskii
2020-04-25 2:55 ` Clément Pit-Claudel
2020-04-25 7:03 ` Eli Zaretskii
2020-04-25 13:12 ` Clément Pit-Claudel
2020-04-25 13:18 ` Stefan Kangas
2020-04-24 12:05 ` Eli Zaretskii
2020-04-24 15:11 ` ndame
2020-04-24 15:45 ` Eli Zaretskii
2020-04-24 16:07 ` Stefan Monnier
2020-04-24 16:29 ` Eli Zaretskii
2020-04-25 3:38 ` Richard Stallman
2020-04-28 13:55 ` Robert Pluim
2020-04-28 14:38 ` Eli Zaretskii
2020-04-29 12:30 ` Robert Pluim
2020-04-29 14:00 ` Eli Zaretskii
2020-04-25 3:34 ` Richard Stallman
2020-04-25 6:39 ` Eli Zaretskii
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=C49BE1B7-41B9-4B92-8BA0-17C70CA37090@gmail.com \
--to=casouri@gmail.com \
--cc=cpitclaudel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=yandros@gmail.com \
--cc=yuri.v.khan@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).