From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: Interest in nt_load_image? Date: Tue, 31 Mar 2020 15:14:01 +0200 Message-ID: References: <86369r0xcv.fsf@csic.es> <83k1324m60.fsf@gnu.org> <86imimwa4t.fsf@csic.es> <838sji3qhx.fsf@gnu.org> <86lfnhsyei.fsf@csic.es> <83v9ml3kpx.fsf@gnu.org> <86r1x9rf7w.fsf@csic.es> <86zhbx6jh1.fsf@csic.es> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000009565ca05a22659d7" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="67933"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Emacs developers To: =?UTF-8?Q?Juan_Jos=C3=A9_Garc=C3=ADa=2DRipoll?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Mar 31 15:16:23 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jJGkg-000HXr-DP for ged-emacs-devel@m.gmane-mx.org; Tue, 31 Mar 2020 15:16:22 +0200 Original-Received: from localhost ([::1]:37758 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJGkf-0000w7-E4 for ged-emacs-devel@m.gmane-mx.org; Tue, 31 Mar 2020 09:16:21 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40711) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJGj3-0007LT-3b for emacs-devel@gnu.org; Tue, 31 Mar 2020 09:14:42 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jJGj1-0007Ws-TJ for emacs-devel@gnu.org; Tue, 31 Mar 2020 09:14:41 -0400 Original-Received: from mail-qk1-x72e.google.com ([2607:f8b0:4864:20::72e]:39745) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jJGj1-0007W4-Oz for emacs-devel@gnu.org; Tue, 31 Mar 2020 09:14:39 -0400 Original-Received: by mail-qk1-x72e.google.com with SMTP id b62so22886476qkf.6 for ; Tue, 31 Mar 2020 06:14:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=My/5CycVbl+yABLQa97h7VSuE7i/a2WKNZ6PRuLGMFM=; b=MDFnV8CLjtFU7RKLtd+AkHMPKY9G/2r0MqnGZlvQ5B6vdVpQT//T7/0oy4fhtBTxPi IeXWUPB5Cq2FSp7Tq2E6CAiveiZnfgByNIQ8E7q7YoycczURKujhHZIIh3Qo0hFBBEsW a0PVPztDMqM5EUO/espp3duuWhjd96LD0t0IJvgan35dD1GmuxTWnX3mtXwA5jHpPmlw uIoWKvnioKWmInw1qG9EiUSG+b3TP1AbGp3r+HL0vqp/GpB93yaKcYLVECix5tET7m1h O1WfPCH3tyaNdU5xBhljm0mPohUnEUwijRFQh81rD00loYjS5ohxJYRkTYWE32LbuiSW 6iYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=My/5CycVbl+yABLQa97h7VSuE7i/a2WKNZ6PRuLGMFM=; b=XFx0cEbC8d5FvtAC/SOyhccqBQbLBizKXO5h2aFHe/Q+D1WWUjKNKinAUiTHQehWyo 8UNu0iWMfL1jiT4c2XtlJjtkYL8rNWswEKQMmLn8oD41UNmIrBZ7KnooS98RNsQutgla fcxmZn9Xx4vDt4aaViH6vy4EhbwqbvRNiJamlFyOHgzRADBkvv8GX25mkKJTslWTMpUz OGi0L854tX/+++xlUSOteUnL9IVGhgDDYGmpB3j5zyz9TlIpGebh8SDGiTjgRLeU4EMq PcHNFGdbHcRYnr05LZVxkHWBOXcdSyL+AL/FWSP/gq/C2HJ7+2qgtGFsOdqQXjarE91c 8Krw== X-Gm-Message-State: ANhLgQ30iV77jLsYxmvexMBSl12U1FLvEDnqIBJ2BFyCQxUcWarDRZlD 8kRYdd+3Ya6hoQlR6nFeSJNLk0lcf+eHCZp79P0= X-Google-Smtp-Source: ADFU+vt38W/1jQR8ftcReeWXkD1QJweOi0DjTzoGt5Ug/WU00Q8/SYchgnJagDSD1Lf0ADWgpj+1YKhhI/A+iSE3Nos= X-Received: by 2002:a05:620a:20dc:: with SMTP id f28mr4833380qka.216.1585660478972; Tue, 31 Mar 2020 06:14:38 -0700 (PDT) In-Reply-To: <86zhbx6jh1.fsf@csic.es> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::72e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:246090 Archived-At: --0000000000009565ca05a22659d7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, Juan Jos=C3=A9 On Tue, Mar 31, 2020 at 10:03 AM Juan Jos=C3=A9 Garc=C3=ADa-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? --0000000000009565ca05a22659d7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi, Juan Jos=C3=A9

On Tue, Mar 31, 2020 at 10:03 AM= Juan Jos=C3=A9 Garc=C3=ADa-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 i= s
> 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 re= ally) "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 a= re Windows' now standard display components, providing
> support = for accelerated GPU-based processing. WIC can act as a canvas
> for r= endering other components and would allow for a more up-to-date
> cap= ability 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 goin= g 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 ve= rsions where GDI+ is not available.=C2=A0 Moreover, I
> think it'= s good to let users have the ability to decide dynamically
> which im= age display capability they want.=C2=A0 It certainly makes sense to
>= do that initially, while the GDI+ way is being tested in all kinds of
&= gt; 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.= =C2=A0

Did I misunderstand him?

--0000000000009565ca05a22659d7--