Nicolas Robidoux writes:
> > The additional command may be required anyway as a means to reduce file
> > size by dropping some non-destructiveness. See last image in
> > http://gimp-brainstorm.blogspot.com/2009/04/version-control.html
> The way nip2/vips deals with a somewhat related issue is that when
> nip2 is started up, if a lot of disk space is taken up by workspaces,
> it asks you whether you would like to delete them. A less drastic gui
> would ask you whether you would like to go through workspaces and mark
> them for deletion, and then you could pick and choose (and only look
> through some of them, even) based on thumbnails, size, date of last
> mod. and whether the result was "finalized."
To push the "at start-up" idea further:
At start-up, the user could be presented with a list of unfinalized
workspaces, and asked whether to finalize each, or open each.
This way, the possibly time consuming rendering would be started at
the beginning of a session, not at the end, unless the user explicitly
asks to finalize one of the current workspaces.
Alternatively, this could be done automatically at start up, in the
(Just brainstorming here.)
Gimp-developer mailing list