From: tomas@tuxteam.de
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Emacs canvas support
Date: Thu, 30 Apr 2020 08:55:58 +0200 [thread overview]
Message-ID: <20200430065558.GA21455@tuxteam.de> (raw)
In-Reply-To: <jwvftcl6adj.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
On Wed, Apr 29, 2020 at 09:19:51PM -0400, Stefan Monnier wrote:
> > Now imagine there's a (graphical) line going from (text) display
> > line 3 to 7. You are not implying that we have to segment that
> > into four chunks, one per text line?
>
> I think it would make more sense to treat the overlaid canvas as
> a completely separate pixmap: when we get an request to redraw
> a particular area of the screen, we'd ask the current redisplay code to
> redraw the corresponding text content and then we'd ask the canvas code
> to draw on top of it. So for rendering of the canvas code we don't need
> to know which part of the canvas cover which characters, we just render
> the glyph matrix into a pixmap, render the canvas into another pixmap
> and then combine them onto the screen.
This is sounding more and more like a compositor :-)
Nit: perhaps we'd like to have pics below as well as above text.
Cheers
-- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2020-04-30 6:55 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <875zdikdge.fsf.ref@yahoo.com>
2020-04-29 6:34 ` Emacs canvas support Po Lu via Emacs development discussions.
2020-04-29 8:24 ` Eli Zaretskii
2020-04-29 9:57 ` Po Lu
2020-04-29 10:10 ` Eli Zaretskii
2020-04-29 10:22 ` Po Lu
2020-04-29 10:27 ` Po Lu via Emacs development discussions.
2020-04-29 11:47 ` Eli Zaretskii
2020-04-29 10:35 ` Eli Zaretskii
2020-04-29 10:41 ` Po Lu
2020-04-29 11:51 ` Eli Zaretskii
2020-04-29 12:12 ` Po Lu
2020-04-29 16:14 ` David Engster
2020-04-29 16:54 ` Eli Zaretskii
2020-04-29 17:16 ` tomas
2020-04-29 17:27 ` Eli Zaretskii
2020-04-29 17:38 ` Eli Zaretskii
2020-04-30 13:11 ` Arthur Miller
2020-04-30 14:18 ` Eli Zaretskii
2020-04-30 14:58 ` Arthur Miller
2020-04-30 17:30 ` Eli Zaretskii
2020-05-01 14:32 ` Arthur Miller
2020-04-29 18:51 ` tomas
2020-04-29 19:03 ` Eli Zaretskii
2020-04-29 19:08 ` tomas
2020-04-29 19:25 ` Eli Zaretskii
2020-04-29 19:59 ` tomas
2020-04-30 1:19 ` Stefan Monnier
2020-04-30 6:55 ` tomas [this message]
2020-04-30 12:03 ` Stefan Monnier
2020-04-30 12:50 ` tomas
2020-04-30 8:04 ` Po Lu
2020-04-30 12:08 ` Stefan Monnier
2020-04-30 13:55 ` Eli Zaretskii
2020-05-01 23:27 ` Po Lu
2020-05-02 6:51 ` Eli Zaretskii
2020-04-30 13:46 ` Eli Zaretskii
2020-04-30 14:37 ` Stefan Monnier
2020-04-30 17:27 ` Eli Zaretskii
2020-04-30 18:22 ` Stefan Monnier
2020-04-30 18:42 ` Eli Zaretskii
2020-04-30 14:27 ` Drew Adams
2020-04-30 13:33 ` Eli Zaretskii
2020-04-30 13:52 ` Arthur Miller
2020-04-29 19:23 ` David Engster
2020-04-30 13:29 ` Eli Zaretskii
2020-04-30 6:52 ` Corwin Brust
2020-04-29 17:08 ` Eli Zaretskii
2020-04-29 20:14 ` David Engster
2020-04-30 13:35 ` Eli Zaretskii
2020-04-29 20:48 ` Juri Linkov
2020-04-30 2:36 ` Eli Zaretskii
2020-04-30 20:20 ` Juri Linkov
2020-05-01 6:01 ` Eli Zaretskii
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=20200430065558.GA21455@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.