unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: "Juan José García-Ripoll" <juanjose.garciaripoll@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Interest in nt_load_image?
Date: Tue, 31 Mar 2020 15:14:01 +0200	[thread overview]
Message-ID: <CAAeL0SQWjwjM97dJvTAgLjU6-T_-fAJBVvemuR+6zdtO_3RRLQ@mail.gmail.com> (raw)
In-Reply-To: <86zhbx6jh1.fsf@csic.es>

[-- Attachment #1: Type: text/plain, Size: 1987 bytes --]

Hi, Juan José

On Tue, Mar 31, 2020 at 10:03 AM Juan José García-Ripoll <
juanjose.garciaripoll@gmail.com> wrote:

> I have build GDI+ as a built-in back-end with which to compile Emacs. An
> Emacs built with GDI+ requires UTF-16 support and thus will not run on
> Windows 98, but it will run on Windows XP on later. GDI+ support is
> optional because it can be selected at build time, not because it can be
> chosen at compilation time.

Assuming you mean "not because it can be chosen at run time", ok, but then
the
(not really) "official" builds of Emacs for Windows will either not use
GDI+, or
it'll be necessary to provide GDI+ and non-GDI+ builds. We still want to
support
Windows 9X.

> WIC and Direct2D are Windows' now standard display components, providing
> support for accelerated GPU-based processing. WIC can act as a canvas
> for rendering other components and would allow for a more up-to-date
> capability in terms of image processing.

Well, then it would be perhaps a worthy goal for (GDI+ builds of) Emacs to
detect
WIC at run-time and use it instead.

> > I mean, if as Eli suggests you're going to dynamically check for GDI+
> > support and revert back to the current API in Windows 9X,...
>
> Neither of us said this. It is a compilation parameter.

Eli said:

> We cannot do this at compile time, because we still try supporting
> ancient Windows versions where GDI+ is not available.  Moreover, I
> think it's good to let users have the ability to decide dynamically
> which image display capability they want.  It certainly makes sense to
> do that initially, while the GDI+ way is being tested in all kinds of
> real-life use cases.
> So all the compile-time tests will have to be rewritten as run-time
> tests, and we should provide variables to force Emacs use/not use
> GDI+, perhaps at image format granularity, and expose those variables
> to Lisp, so users could control that.

Did I misunderstand him?

[-- Attachment #2: Type: text/html, Size: 2280 bytes --]

  reply	other threads:[~2020-03-31 13:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29 19:33 Interest in nt_load_image? Juan José García-Ripoll
2020-03-29 21:55 ` Juan José García-Ripoll
2020-03-30  2:21 ` Eli Zaretskii
2020-03-30  7:54   ` Juan José García-Ripoll
2020-03-30 13:46     ` Eli Zaretskii
2020-03-30 14:36       ` Juan José García-Ripoll
2020-03-30 14:44         ` Juan José García-Ripoll
2020-03-30 15:50         ` Eli Zaretskii
2020-03-30 16:15           ` Juan José García-Ripoll
2020-03-30 16:37             ` Eli Zaretskii
2020-03-30 17:16               ` Stefan Monnier
2020-03-30 18:32                 ` Eli Zaretskii
2020-03-30 18:41                   ` Stefan Monnier
2020-03-30 18:57                     ` Eli Zaretskii
2020-03-30 19:39                       ` Stefan Monnier
2020-03-31 14:19                         ` Eli Zaretskii
2020-03-30 18:06               ` Juan José García-Ripoll
2020-03-30 18:47                 ` Eli Zaretskii
2020-03-30 18:53                   ` Eli Zaretskii
2020-03-30 23:21             ` Juanma Barranquero
2020-03-31  8:01               ` Juan José García-Ripoll
2020-03-31 13:14                 ` Juanma Barranquero [this message]
2020-03-31 14:50                   ` Stefan Monnier
2020-03-31 15:25                     ` Juanma Barranquero
2020-03-31 16:54                       ` Stefan Monnier
2020-03-31 15:13                   ` Juan José García-Ripoll
2020-03-31 15:28                     ` Juanma Barranquero
2020-03-31 13:31                 ` Eli Zaretskii
2020-03-30 15:14       ` Stefan Monnier
2020-03-30 15:57         ` Eli Zaretskii
2020-03-30 17:10           ` Stefan Monnier
2020-03-30 18:23             ` 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=CAAeL0SQWjwjM97dJvTAgLjU6-T_-fAJBVvemuR+6zdtO_3RRLQ@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=juanjose.garciaripoll@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).