From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org, julius.pfrommer@web.de
Subject: Re: Unifying code for drawing on a cairo context
Date: Sat, 23 Apr 2022 15:04:14 +0300 [thread overview]
Message-ID: <83wnfgngzl.fsf@gnu.org> (raw)
In-Reply-To: <87fsm4810z.fsf@yahoo.com> (message from Po Lu on Sat, 23 Apr 2022 19:58:04 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: "Pfrommer, Julius" <julius.pfrommer@web.de>, emacs-devel@gnu.org
> Date: Sat, 23 Apr 2022 19:58:04 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > In general, I don't think we'd object to having such Cairo-specific
> > code in one place. However, having GUI code common to all the GUI
> > backends in one place is more important, so if this Cairo-specific
> > module will make that common code less so, it would be a step
> > backward, IMO. IOW, as long as the effort to have Cairo-specific code
> > in one place doesn't "invade" on the common code, it is welcome, I
> > think.
>
> I think that we won't be able to get the Cairo code all in one place,
> without a large amount of code specific to each window system, which
> defeats the point of such refactoring.
Clearly, I was writing on the assumption that this would be possible,
without independently assessing whether in fact it is possible.
next prev parent reply other threads:[~2022-04-23 12:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 9:06 Unifying code for drawing on a cairo context Pfrommer, Julius
2022-04-23 9:18 ` Eli Zaretskii
2022-04-23 11:58 ` Po Lu
2022-04-23 12:04 ` Eli Zaretskii [this message]
2022-04-29 8:01 ` Pfrommer, Julius
2022-04-29 8:33 ` Po Lu
2022-04-29 8:35 ` Po Lu
2022-04-29 9:07 ` Pfrommer, Julius
2022-04-29 9:20 ` Po Lu
2022-04-29 10:43 ` Eli Zaretskii
2022-04-23 11:51 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wnfgngzl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=julius.pfrommer@web.de \
--cc=luangruo@yahoo.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.