unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: "Juanma Barranquero" <lekktu@gmail.com>
Cc: Thien-Thi Nguyen <ttn@gnuvola.org>, emacs-devel@gnu.org
Subject: Re: image scaling
Date: Fri, 22 Feb 2008 15:38:27 -0500	[thread overview]
Message-ID: <87fxvkk9q4.fsf@stupidchicken.com> (raw)
In-Reply-To: <f7ccd24b0802220306h71c52816r52be4137ab52217@mail.gmail.com> (Juanma Barranquero's message of "Fri\, 22 Feb 2008 12\:06\:04 +0100")

"Juanma Barranquero" <lekktu@gmail.com> writes:

>>  Maybe the scaling is part of a series of operations,
>>  the end of which would be displayable but not the middle.
>
> I'm not sure I understand. A series of operations (presumably, image
> transformations of some sort) without the image library support? We do
> that today, manipulating for example PNG images without (statically or
> dynamically) linking libpng?

Suppose, for example, we "outsource" image transformations to a
specific external library.  For the sake of argument, let's say this
library is libpng.

One way to do this is to have Emacs use libpng internally to store and
manipulate (e.g. rescale) images, instead of the pixel buffer system
we currently use.  Alternatively, Emacs might keep the pixel buffer
system, but perform image manipulations by converting the image into a
png internally, calling the relevant libpng function to rescale it or
whatever, and then converting it back.

We would thus be using libpng to perform image manipulations, for
arbitrary images and not just pngs.  The trouble is that if libpng is
not available, all this functionality would disappear (not just for
pngs, but also for gifs or whatever other images *are* supported).  In
that case, how would we handle this at the Lisp interface level?




  reply	other threads:[~2008-02-22 20:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21  4:21 image scaling Stefan Monnier
2008-02-21  8:42 ` Mathias Dahl
2008-02-21  9:10   ` Miles Bader
2008-02-21 15:59   ` Stefan Monnier
2008-02-21 20:41     ` Mathias Dahl
2008-02-21 10:01 ` David Kastrup
2008-02-21 10:06 ` joakim
2008-02-21 12:43   ` David O'Toole
2008-02-21 18:43 ` Chong Yidong
2008-02-21 21:49   ` David Kastrup
2008-02-21 22:20     ` Miles Bader
2008-02-22  6:35       ` Jan Djärv
2008-02-22  6:49         ` Miles Bader
2008-02-22  7:26           ` Jan Djärv
2008-02-22 22:57         ` Richard Stallman
2008-02-22  4:57     ` Chong Yidong
2008-02-22  7:48       ` David Kastrup
2008-02-22 20:28         ` Chong Yidong
2008-02-22 21:52           ` David Kastrup
2008-02-22 22:41             ` Chong Yidong
2008-02-22 22:51               ` David Kastrup
2008-02-22 10:23       ` Juanma Barranquero
2008-02-22 10:55         ` Thien-Thi Nguyen
2008-02-22 11:06           ` Juanma Barranquero
2008-02-22 20:38             ` Chong Yidong [this message]
2008-02-22 20:47               ` Juanma Barranquero
2008-02-22 22:21               ` Miles Bader
2008-02-23 19:28               ` Richard Stallman
2008-02-22 22:57       ` Richard Stallman
2008-02-21 22:28 ` Richard Stallman

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=87fxvkk9q4.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    --cc=ttn@gnuvola.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).