unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Anand Tamariya <atamariya@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	 Alexander Adolf <alexander.adolf@condition-alpha.com>,
	 Emacs Devel <emacs-devel@gnu.org>
Subject: Re: SVG hack for display engine
Date: Wed, 17 Nov 2021 12:46:47 +0800	[thread overview]
Message-ID: <874k8bs820.fsf@yahoo.com> (raw)
In-Reply-To: <CADm7Y4=qCedZcNX=mjiCBmfUsr2YoticZmzb5-fR_VJ6G8VE5A@mail.gmail.com> (Anand Tamariya's message of "Wed, 17 Nov 2021 10:03:25 +0530")

Anand Tamariya <atamariya@gmail.com> writes:

> This should mean minimal changes to the display engine and it
> continues to run as is for terminals. What do you think?

FWIW I am working on a port of Emacs to GTK 4, which doesn't use Cairo
(which has been deprecated by the GTK developers), instead using the
native GSK scene graph kit to draw.  It does something very similar to
what your SVG rendering would be like, keeping a tree of render nodes
around past calls to gtk_widget_draw, and modifying it from the RIF.

Getting it to work mostly correctly was extremely painful, and it still
struggles with leaks (where obscured render nodes are not pruned
correctly by xg_fixup_render_table) and the lack of the scroll
optimization.

(If someone wants details on this, wait a few weeks.  I will probably
have it in a usable state by then.)

Thanks.



  reply	other threads:[~2021-11-17  4:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15  2:39 SVG hack for display engine Anand Tamariya
2021-11-15 12:45 ` Eli Zaretskii
2021-11-15 13:27   ` Anand Tamariya
2021-11-15 14:02     ` Eli Zaretskii
2021-11-16  3:01       ` Anand Tamariya
2021-11-16  3:28         ` Po Lu
2021-11-16 12:56           ` Eli Zaretskii
2021-11-16 13:02             ` Po Lu
2021-11-16 12:55         ` Eli Zaretskii
2021-11-16 14:08           ` Alexander Adolf
2021-11-16 14:16             ` Eli Zaretskii
2021-11-16 14:22               ` Alexander Adolf
2021-11-17  4:33               ` Anand Tamariya
2021-11-17  4:46                 ` Po Lu [this message]
2021-11-26  1:33                   ` Gerry Agbobada
2021-11-17 13:47                 ` Eli Zaretskii
2021-11-17 23:47                   ` Anand Tamariya
2021-11-18  8:16                     ` Eli Zaretskii
2021-11-18 10:13                       ` Anand Tamariya
2021-11-18 11:21                         ` Eli Zaretskii
2021-11-18 13:29                           ` Anand Tamariya
2021-11-18 14:52                             ` Eli Zaretskii
2021-11-19  1:32                               ` Anand Tamariya
2021-11-19  7:07                                 ` Eli Zaretskii
2021-11-20 19:44                                 ` Alan Third
2021-11-22  2:48                                   ` Anand Tamariya
2021-11-22 10:59                                     ` Alan Third

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=874k8bs820.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=alexander.adolf@condition-alpha.com \
    --cc=atamariya@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).