On Mon, Jun 18, 2007 at 10:59:29PM +0200, Jean-Marc Lasgouttes wrote:
> >>>>> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
> 
> Andre> We get the same information with any other file format.
> 
> Andre> And as most of the PNGs are tiny storing full diffs would not
> Andre> even be expensive either.
> 
> Probably.
> 
> >> However, in these days of a PNG-aware frontend, it does seem
> >> strange that we still ship these XPM files to our consumers. Here's
> >> a thought: why don't we make the XPM -> PNG transformation part of
> >> the build process and ship the resulting PNGs?
> 
> Andre> Because that is not needed either. We can just the frontend's
> Andre> resource system and would not need to ship individual files at
> Andre> all.
> 
> I do not think this gains anything.

Slightly quicker loading of individual pixmaps at the price of slightly
larger startup times (with a total gain) and less messy user side code.
Compare

  QPixmap pixmap = QPixmap(toqstr(libFileSearch("images", fname,
"xpm").absFilename()));

with

  QPixmap pixmap = QPixmap("images/" + fname + ".png");

or even

  QPixmap pixmap("images/" + fname + ".png");

Faster installation.

Not much gain, but a bit...

Andre'

Reply via email to