unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
Cc: David Kastrup <dak@gnu.org>
Subject: Emacs, colors and gdk-pixbuf.
Date: Sun, 13 Apr 2003 21:17:30 +0200	[thread overview]
Message-ID: <921D608D-6DE4-11D7-BB92-00039363E640@swipnet.se> (raw)

Hello.

Some time ago there was some discussion about improving image and
color handling in Emacs.  One suggestion as to use gdk-pixbuf to
handle images.  I have made some tests, the actual code to get
gdk-pixbuf in is not that big.  I haven't actually checked if this
does make color handling better.  But there are some issues I'd like
some comments on.

First, gdk-pixbuf is inherently single displayed.  This means that
Emacs would be limited to one display.  Since GTK also is 
single-displayed
(perhaps not 2.2, there has been talk about some changes, I haven't 
checked
this yet), we could make gdk-pixbuf the default for GTK.

The part of gdk-pixbuf is the part that renders into X11.  Emacs could
use its own version of this code, suitable modified.  Is that something
people think is OK (using private versions of other libraries)?  Must
license issues be investigated or is it OK to modify stuff from GTK?

Another thing is that gdk-pixbuf may have been compiled with image
support that is different from the one Emacs has today (i.e. gdk-pixbuf 
may not have, for example, TIFF support compiled in).  Should we
try to make a configure test to see what image types gdk-pixbuf 
supports,
and then fall back to "native" support for the others?  Or just fail
at runtime if an image type is used that gdk-pixbuf supports?

Comments welcome,

	Jan D.

             reply	other threads:[~2003-04-13 19:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-13 19:17 Jan D. [this message]
2003-04-13 20:31 ` Emacs, colors and gdk-pixbuf David Kastrup
2003-04-13 21:43   ` Jan D.

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=921D608D-6DE4-11D7-BB92-00039363E640@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=dak@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).