From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: Several suggestions for image support Date: 21 Apr 2004 12:10:08 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1082535909 24294 80.91.224.253 (21 Apr 2004 08:25:09 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 21 Apr 2004 08:25:09 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed Apr 21 10:25:01 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BGD2S-0005ZM-00 for ; Wed, 21 Apr 2004 10:25:00 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BGD2S-0007Gu-00 for ; Wed, 21 Apr 2004 10:25:00 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1BGCyF-000228-00 for emacs-devel@quimby.gnus.org; Wed, 21 Apr 2004 04:20:39 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1BGCy7-00020N-2v for emacs-devel@gnu.org; Wed, 21 Apr 2004 04:20:31 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1BGCxX-0001t2-25 for emacs-devel@gnu.org; Wed, 21 Apr 2004 04:20:26 -0400 Original-Received: from [212.88.64.25] (helo=mail-relay.sonofon.dk) by monty-python.gnu.org with smtp (Exim 4.30) id 1BGCur-0001JG-Fy for emacs-devel@gnu.org; Wed, 21 Apr 2004 04:17:09 -0400 Original-Received: (qmail 22478 invoked from network); 21 Apr 2004 08:10:27 -0000 Original-Received: from unknown (HELO kfs-l.imdomain.dk.cua.dk) (213.83.150.2) by 0 with SMTP; 21 Apr 2004 08:10:27 -0000 Original-To: David Kastrup In-Reply-To: Original-Lines: 61 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:21979 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:21979 David Kastrup writes: > storm@cua.dk (Kim F. Storm) writes: > > > David Kastrup writes: > > > > > PNG images support transparency. Emacs can't make use of it. You can > > > only have Emacs declare a particular color as transparent. This is > > > dissatisfactory. It should tell the PNG decoding routines Emacs' > > > background color for the purpose of transparency. > > > > > > I would find it important if an image specifier could restrict the > > > displayed portion of an image. > > > > I have just implemented image slicing via a new slice property: > > > > display ((slice X Y WIDTH HEIGHT) (image ...)) > > Does that imply that slicing is not only applicable to images? Currently it only applies to images. It can be extended to other objects as well, but I don't plan to do that myself. > Anyway, I have been wondering about how to make slicing an image > property while being able to reuse the image for several slices. > Making this a separate property of course solves that concern. > > The effect would presumably be that only the selected slice of the > image gets displayed, right? Exactly. > And if the current line height exceeds > that of slices in consecutive rows, then there would be white space > between them, right? Unfortunately, yes. However, I have fixed the treatment of newline characters so that non-empty lines are no longer made a minimum height equal to the frame default line height. So you can use very small slices with good results. > Does anybody know offhand whether one can > _reduce_ the linespacing to "tight" for a given interval? We can probably build on the existing "overlapping rows" code, thus allowing a slice to be physically higher than its logical height. But it is a bit complicated, so I postponed that to later -- and to see if something better could be found. > > It probably will not be "crucial" though. Good. -- Kim F. Storm http://www.cua.dk