From: Alan Third <alan@idiocy.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Evgeny Zajcev <lg.zevlg@gmail.com>,
Stefan Kangas <stefankangas@gmail.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Image transformation filter for upscaled images
Date: Mon, 8 Mar 2021 21:59:14 +0000 [thread overview]
Message-ID: <YEaeMojoJAuFMHAA@breton.holly.idiocy.org> (raw)
In-Reply-To: <87v9a1l4d7.fsf@gnus.org>
On Mon, Mar 08, 2021 at 10:31:16PM +0100, Lars Ingebrigtsen wrote:
> Alan Third <alan@idiocy.org> writes:
>
> > I don't know, I'd be inclined to go with adding an image option, like
> > ":filter smooth" or ":filter nearest" and letting mode authors choose
> > what they think is best.
>
> Yes, that's an excellent idea.
Not my idea, but certainly a good one. :)
> > (Also, I think :filter may be taken, so perhaps just ":smooth t/nil"
> > or something...)
>
> Sure. Or... :scaling-algorithm...
I was wrong, :filter is available, I'll have a bit more of a think
about what we want to call it.
As for default behaviour, I'm inclined to stick with what we have
where scaling down uses best and scaling up uses nearest neighbour but
any use of :filter (or whatever) over-rides the default. Anyone have
an opinion? Do we just want to use best everywhere by default?
--
Alan Third
next prev parent reply other threads:[~2021-03-08 21:59 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 19:12 Image transformation filter for upscaled images Evgeny Zajcev
2021-03-07 20:45 ` Alan Third
2021-03-07 22:35 ` Evgeny Zajcev
2021-03-07 23:27 ` Stefan Kangas
2021-03-08 0:42 ` Evgeny Zajcev
2021-03-08 2:31 ` Stefan Kangas
2021-03-08 13:34 ` Eli Zaretskii
2021-03-08 13:31 ` Eli Zaretskii
2021-03-08 18:58 ` Alan Third
2021-03-08 19:18 ` Lars Ingebrigtsen
2021-03-08 21:27 ` Alan Third
2021-03-08 21:31 ` Lars Ingebrigtsen
2021-03-08 21:59 ` Alan Third [this message]
2021-03-09 8:34 ` Evgeny Zajcev
2021-03-09 9:28 ` Alan Third
2021-03-09 9:46 ` Evgeny Zajcev
2021-03-09 14:16 ` Stefan Monnier
2021-03-09 13:09 ` Eli Zaretskii
2021-03-09 13:48 ` Evgeny Zajcev
2021-03-09 13:59 ` Lars Ingebrigtsen
2021-03-09 16:37 ` Eli Zaretskii
2021-03-09 17:04 ` Lars Ingebrigtsen
2021-03-09 18:01 ` Eli Zaretskii
2021-03-10 4:23 ` Yuri Khan
2021-03-10 14:44 ` Lars Ingebrigtsen
2021-03-09 13:16 ` Lars Ingebrigtsen
2021-03-09 13:50 ` Dov Grobgeld
2021-03-09 18:16 ` Alan Third
2021-03-09 18:12 ` Alan Third
2021-03-09 22:31 ` Basil L. Contovounesios
2021-03-09 23:59 ` Stefan Monnier
2021-03-10 13:37 ` Alan Third
2021-03-10 14:49 ` Lars Ingebrigtsen
2021-03-10 21:45 ` Alan Third
2021-03-11 16:53 ` Lars Ingebrigtsen
2021-03-12 1:38 ` Lars Ingebrigtsen
2021-03-12 2:01 ` Evgeny Zajcev
2021-03-12 18:32 ` Alan Third
2021-03-08 20:05 ` Evgeny Zajcev
2021-03-08 21:29 ` Alan Third
2021-03-08 13:27 ` Eli Zaretskii
2021-03-07 23:12 ` Stefan Monnier
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=YEaeMojoJAuFMHAA@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=lg.zevlg@gmail.com \
--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).