On Mon, Jul 07, 2008 at 08:45:04AM +0200, Sven Neumann wrote:
> But as soon as you perform an operation on the image, the
> full-scale image data needs to be touched.
Agreed. This is much easier to program. However, when I'm zoomed in to
say a 4 megapixel part of the image, and the selection is in view,
then if I do something a max of 4 Mpixels, of 4 bytes * 2 need to be
touched. I have plenty of RAM for that.
> It's non-trivial to avoid this. But it is on the long-term plan to
> implement working on the scaled-down version. We hope to be able to
> address this when GIMP makes full use of GEGL. If you want to help,
> I suggest that you contribute to the GEGL development.
So, when on my original image, I select part, and use the "fill with
gradient" tool, I first get a progress bar that moves in about 30
seconds from 0 to 100%. Then I have to wait about 30 seconds for the
swapping to stop. The fill could be done on the small scale cache,
allowing the GUI to be updated and then a background process can
update the actual image, without me having to wait for it to
complete. Is that similar to what GEGL intends to do?
** [EMAIL PROTECTED] ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ
Gimp-developer mailing list