Re: gtk+ and gtk-engines slow

[Miguel de Icaza <miguel nuclecu unam mx>]

> That is not the point raster was making.  The point is that imlib has its
> own configuration file (~/.imrc), and gnome was overriding options from
> the user's configuration file.  Maybe a better solution would have been
> for gnome_init to check for the presence of ~/.imrc, and if it doesn't
> exist create one with the settings Miguel thinks are best.  

James,  the problem is that in GNOME, with the exception of the Pixmap 
engine, we barely use all of Imlib's potential.  GNOME applications
are not graphic hungry nor do they keep loading files from the disk
nor scale pixmaps constantly.

The Imlib settings are not useful at all for GNOME applications and
they just waste memory under normal conditions (ie, non-pixmap
theme).  

Under those conditions, it is equivalent to do:

	memset (malloc (512*1024), 0, 512*1024);

Because the information is *NEVER* used under regular operation.

With the current fix (the one I have detailed in the post to
gnome-list and gnome-hackers) I have addressed all of the problems.

Miguel.