From: Po Lu <luangruo@yahoo.com>
To: Richard Stallman <rms@gnu.org>
Cc: larsi@gnus.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Touchscreen support
Date: Tue, 21 Dec 2021 12:35:56 +0800 [thread overview]
Message-ID: <87ilviy3pv.fsf@yahoo.com> (raw)
In-Reply-To: <E1mzWZ3-00013I-KK@fencepost.gnu.org> (Richard Stallman's message of "Mon, 20 Dec 2021 23:15:49 -0500")
Richard Stallman <rms@gnu.org> writes:
> That sounds like a big problem, but it is described in a very abstract
> way. Can you present a concrete exanple of such a difference in
> abstractions?
For example, programs in GTK+ aren't supposed to create windows or
widgets manually anymore. Instead, GTK provides a system to create
"applications", which run in the background and respond to requests to
open files or to display a default window, and it also provides an
XML-based format for describing the layout of widgets and windows.
In GTK 4, menus cannot even be modified by applications on-the-fly
anymore. You are again supposed to use a GTK-specific XML format to
describe the menus of your application in a way that cannot be changed
at run-time.
What used to be a few ifdefs (and some code) away now requires you to
write a different XML file for each toolkit, and to redesign your
application to fit various unnecessary limitations imposed by the
toolkit developers.
> Would it be possible to invent a higher-level abstraction to unify
> these toolkits?
I'm not sure.
next prev parent reply other threads:[~2021-12-21 4:35 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87czlxkntg.fsf.ref@yahoo.com>
2021-12-16 7:31 ` Touchscreen support Po Lu via Emacs development discussions.
2021-12-16 7:58 ` Lars Ingebrigtsen
2021-12-16 8:02 ` Po Lu
2021-12-17 6:19 ` Po Lu
2021-12-17 7:17 ` Lars Ingebrigtsen
2021-12-17 12:29 ` Stefan Monnier
2021-12-17 12:36 ` Po Lu
2021-12-17 13:18 ` Stefan Monnier
2021-12-17 13:48 ` Po Lu
2021-12-17 16:00 ` Stefan Monnier
2021-12-18 0:02 ` Po Lu
2021-12-18 16:22 ` Stefan Monnier
2021-12-18 19:12 ` Stefan Monnier
2021-12-18 4:41 ` Richard Stallman
2021-12-18 4:53 ` Po Lu
2021-12-20 4:42 ` Richard Stallman
2021-12-20 4:59 ` Po Lu
2021-12-21 4:15 ` Richard Stallman
2021-12-21 4:35 ` Po Lu [this message]
2021-12-22 4:16 ` Richard Stallman
2021-12-22 4:39 ` Po Lu
2021-12-23 3:43 ` Richard Stallman
2021-12-23 4:46 ` Po Lu
2021-12-26 3:57 ` Richard Stallman
2021-12-26 5:02 ` Po Lu
2021-12-27 4:14 ` Richard Stallman
2021-12-27 6:05 ` Stefan Monnier
2021-12-28 4:19 ` Richard Stallman
2022-01-15 0:17 ` chad
2022-01-15 0:48 ` Po Lu
2022-01-16 5:07 ` Richard Stallman
2022-01-16 5:35 ` Po Lu
2021-12-18 7:48 ` Lars Ingebrigtsen
2021-12-18 14:46 ` Eli Zaretskii
2021-12-19 0:24 ` Po Lu
2021-12-19 8:14 ` Eli Zaretskii
2021-12-19 9:24 ` Po Lu
2021-12-19 9:32 ` Eli Zaretskii
2021-12-19 9:38 ` Po Lu
2021-12-19 11:31 ` Eli Zaretskii
2021-12-19 11:42 ` Po Lu
2021-12-19 17:58 ` Eli Zaretskii
2021-12-20 0:54 ` Po Lu
2021-12-20 15:18 ` Eli Zaretskii
2021-12-21 1:08 ` Po Lu
2021-12-21 12:11 ` Eli Zaretskii
2021-12-21 12:21 ` Po Lu
2021-12-21 14:17 ` Eli Zaretskii
2021-12-19 18:26 ` [External] : " Drew Adams
2021-12-20 4:42 ` Richard Stallman
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=87ilviy3pv.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
/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).