caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Matt Gushee <matt@gushee.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Weak hashtables & aggressive caching
Date: Mon, 14 Aug 2006 17:25:57 -0600	[thread overview]
Message-ID: <44E10685.8070403@gushee.net> (raw)
In-Reply-To: <20060814181836.GA23782@furbychan.cocan.org>

Richard Jones wrote:
> On Mon, Aug 14, 2006 at 10:28:39AM -0600, Matt Gushee wrote:
>> Wait a minute, though. According to the Gdk reference manual, 
>> <http://developer.gnome.org/doc/API/2.0/gdk/gdk-Pixbufs.html#id2861842>
>>
>>   Pixbufs are client-side images.
> 
> Ah right, pixbufs, pixmaps ...  In that case why bother preloading
> them at all?

Well, maybe I shouldn't. That's why I asked if it was worth the effort.

> eog is flagrant with regards to pixmaps because the
> developers believe it allows them to display images quickly (the
> images are already on the X server, converted from JPEGs into raw
> pixels).  In this age of fast CPUs and slow RAM this is unlikely to be
> the case.

Thanks for your insights.

-- 
Matt Gushee
: Bantam - lightweight file manager : matt.gushee.net/software/bantam/ :
: RASCL's A Simple Configuration Language :     matt.gushee.net/rascl/ :


  reply	other threads:[~2006-08-14 23:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 14:58 Matt Gushee
2006-08-14 15:47 ` [Caml-list] " Richard Jones
2006-08-14 16:28   ` Matt Gushee
     [not found]     ` <44E0A8F1.8060504@janestcapital.com>
2006-08-14 17:35       ` Matt Gushee
2006-08-14 18:18     ` Richard Jones
2006-08-14 23:25       ` Matt Gushee [this message]
2006-08-14 21:23 ` Jacques Garrigue
2006-08-14 23:30   ` Matt Gushee
2006-08-16  0:54     ` Jacques Garrigue
2006-08-16  4:33       ` Matt Gushee
2006-08-15  4:55   ` skaller
2006-08-15 16:17     ` Matt Gushee

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=44E10685.8070403@gushee.net \
    --to=matt@gushee.net \
    --cc=caml-list@inria.fr \
    /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. 
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 NNTP newsgroup(s).