unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Anand Tamariya <atamariya@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: SVG hack for display engine
Date: Mon, 15 Nov 2021 18:57:20 +0530	[thread overview]
Message-ID: <CADm7Y4=DjY7_wPgSzWkyXsB0ujFYUViK5nB5JwS-qx+z1htrRw@mail.gmail.com> (raw)
In-Reply-To: <8335nxtwo7.fsf@gnu.org>

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

In this hack, the elisp code navigates from (window-start) to (window-end)
reading a line of text from the associated buffer and displays the same in
SVG. I've used (read-event) and (lookup-key) to allow for key translations
for navigation commands. Hopefully with a tighter integration, all of this
will not be required.

Positioning of the point is one open area. We would need the bounding box
of text for accurate positioning. We have three sources for this - librsvg,
pango or the current display engine.

On Mon, Nov 15, 2021 at 6:15 PM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Anand Tamariya <atamariya@gmail.com>
> > Date: Mon, 15 Nov 2021 08:09:22 +0530
> >
> > How about using SVG for rendering in the display engine?
>
> Please elaborate what you mean by that.  How would the display engine
> work under this idea?
>
> The image you posted doesn't tell enough to understand what's
> involved, and thus it is very hard to think about possible
> implications of such a change.
>
> Thanks.
>

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

  reply	other threads:[~2021-11-15 13:27 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 [this message]
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
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='CADm7Y4=DjY7_wPgSzWkyXsB0ujFYUViK5nB5JwS-qx+z1htrRw@mail.gmail.com' \
    --to=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).