|
From: | Tomas Hlavaty |
Subject: | Re: Introducing emacs-webkit and more thoughts on Emacs rendering (was Rethinking the design of xwidgets) |
Date: | Tue, 01 Dec 2020 17:48:12 +0100 |
On Tue 01 Dec 2020 at 16:36, Arthur Miller <arthur.miller@live.com> wrote: > Tomas Hlavaty <tom@logand.com> writes: >> It would be more convenient, if an image was represented as elisp data >> instead of C data. > :-) I don't think you have thought well about it; Why would you say that? > but really nothing forbids you to try to reprsent images as lisp. What do you mean exactly? > You can take any de-compressed image and read in raw pixels in as a byte > buffer and just shuffle around numbers and see how it > works for you.Image is nothing but a bunch of numbers + some tiny > metadata on top of it. Take some of netpbm formats and you have "textual > image" you can manipulate on per-pixel level with lisp. Image in emacs is represented in C as "struct image". Image type in emacs is represented in C as "struct image_type". The issue is that there doesn't seem to be a way to extend those (and/or define new) in pure elisp.
[Prev in Thread] | Current Thread | [Next in Thread] |