Re: [Gimp-developer] Re: optional scaling in the save dialog?

[Adam D. Moss]

Joao S. O. Bueno Calligaris wrote:
- Initially using X memory
duplicate image - now using x * 2 memory.
That shouldn't be true.  The vast majority of the memory
used by the duplicate is tile data which GIMP simply
copy-on-write shares between the original and the duplicate.
(Unless COW stuff got broken since I last checked, but I
doubt it.)
--Adam
--
Adam D. Moss   -   [EMAIL PROTECTED]
___
Gimp-developer mailing list
Gimp-developer@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

[Gimp-developer] Re: optional scaling in the save dialog?

[GSR - FR]

Hi,
[EMAIL PROTECTED] (2005-02-18 at 2053.55 -0200):
   I am currently working on a poster, and it's huge (from the point
   of view of the amount of memory I have ;) ). Once in a while I
   have to post it to the mailing list for my people to see if they
   like it and tell me what to change. Every time I want to mail it
   I first have to save it (.xcf), then scale it down, save as jpg
   then undo the scaling or just close and load again. So I thought
   it would be great if there was an option in the save dialog to
   choose the size you want to save the image in. It could be hidden
   in the Advanced Options or something so that usually it
   wouldn't bother you.
 Try disabling script-fu previously to scale,
 then save as copy, and reload your image.

I would go with duplicate image, scale the clone, save then close. No
undo problems that way, xcf version stays untouched, both disk and
memory.

GSR
 
___
Gimp-developer mailing list
Gimp-developer@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer

Re: [Gimp-developer] Re: optional scaling in the save dialog?

[Joao S. O. Bueno Calligaris]

On Saturday 19 February 2005 16:06, GSR - FR wrote:
 Hi,

 [EMAIL PROTECTED] (2005-02-18 at 2053.55 -0200):
I am currently working on a poster, and it's huge (from the
point of view of the amount of memory I have ;) ). Once in a
while I have to post it to the mailing list for my people to
see if they like it and tell me what to change. Every time I
want to mail it I first have to save it (.xcf), then scale it
down, save as jpg then undo the scaling or just close and
load again. So I thought it would be great if there was an
option in the save dialog to choose the size you want to save
the image in. It could be hidden in the Advanced Options or
something so that usually it wouldn't bother you.
 
  Try disabling script-fu previously to scale,
  then save as copy, and reload your image.

 I would go with duplicate image, scale the clone, save then close.
 No undo problems that way, xcf version stays untouched, both disk
 and memory.

Let X bre a Huge Amount of Memory (tm) taken by said image, and Y be A 
Couple Kilobytes (tm) used by scaled down version
Your proccess: 
- Initially using X memory
duplicate image - now using x * 2 memory.
scale image down, with UNDO active - using x * 2 + Y memory 
discard copy- back to using X memory.

My proccess:
- Inittially using X memory
- Disable Undo for this image
- Scale down: Using Y memory.
- Save copy
- Revert: Using back X memory.

As you see, they are roughly equivalent, exepct that your method, in 
the intermediate steps, use twice as much memory.  The slowdown 
complained about is probably due to Tile swapping . 

Take your conclusions.




 GSR

 ___
 Gimp-developer mailing list
 Gimp-developer@lists.xcf.berkeley.edu
 http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
___
Gimp-developer mailing list
Gimp-developer@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer