Re: [Gimp-developer] Annoying behavior of shared settings for file save plug-ins

2007-08-31 Thread Raphaël Quinet
On Fri, 31 Aug 2007 12:24:47 -0400, Robert L Krawitz <[EMAIL PROTECTED]> wrote: > It sounds like what's happening is something like this: > > 1) Current JPEG quality setting is 85 > 2) User selects "Use quality settings from original image if >original image is better" > 3) Ori

Re: [Gimp-developer] Annoying behavior of shared settings for file save plug-ins

2007-08-31 Thread Robert L Krawitz
Date: Fri, 31 Aug 2007 17:39:45 +0200 From: =?UTF-8?B?UmFwaGHDq2w=?= Quinet <[EMAIL PROTECTED]> If you want to save several images with the same settings, you can use the buttons "Save defaults" and "Load defaults". We also have an enhancement request (bug #120829) about providing

Re: [Gimp-developer] Annoying behavior of shared settings for file save plug-ins

2007-08-31 Thread Alexander Rabtchevich
Rather strange conclusion from my POV - if something very convenient cannot be provided for each and every case, it shouldn't be provided at all. I can prove my opinion with a case with healing brush. It saves me a lot of time and efforts during photo retouching despite the fact it doesn't sup

Re: [Gimp-developer] Annoying behavior of shared settings for file save plug-ins

2007-08-31 Thread Raphaël Quinet
On Thu, 30 Aug 2007 15:56:16 -0600, Scott <[EMAIL PROTECTED]> wrote: > On Thu, Aug 30, 2007 at 08:56:33AM +0200, Jakub Friedl wrote: > > I think that "use image file quality unless defaults are 'better'" is not > > thee problem. Problem is inheriting image quality between different images > > in on

[Gimp-developer] Annoying behavior of shared settings for file save plug-ins

2007-08-31 Thread Могучий Сергей
> On Thu, 30 Aug 2007 11:07:40 +0200, Raphaël Quinet > wrote: > On Thu, 30 Aug 2007 00:57:44 +0200, gg at catking.net wrote: >> Gimp should not decide what is "better" because it cannot know what is >> required so cannot make that choice. >> >> This sort of "surprise" behaviour is precisely the

Re: [Gimp-developer] Annoying behavior of shared settings for file save plug-ins

2007-08-30 Thread Scott
On Fri, Aug 31, 2007 at 12:19:23AM +0200, [EMAIL PROTECTED] wrote: > > I think what you describe could be put under Save as. It is not Save > though. > > Probably misusing the "defaults". You're right, of course. Doh. I always use "save as". And it works fine for my purposes (other than the sa

Re: [Gimp-developer] Annoying behavior of shared settings for file save plug-ins

2007-08-30 Thread gg
On Thu, 30 Aug 2007 23:56:16 +0200, Scott <[EMAIL PROTECTED]> wrote: > On Thu, Aug 30, 2007 at 08:56:33AM +0200, Jakub Friedl wrote: >> I think that "use image file quality unless defaults are 'better'" is >> not >> thee problem. Problem is inheriting image quality between different >> images

Re: [Gimp-developer] Annoying behavior of shared settings for file save plug-ins

2007-08-30 Thread Scott
On Thu, Aug 30, 2007 at 08:56:33AM +0200, Jakub Friedl wrote: > I think that "use image file quality unless defaults are 'better'" is not > thee problem. Problem is inheriting image quality between different images > in one GIMP session. I have a default quality of 85. Then I open DSLR image > with

Re: [Gimp-developer] Annoying behavior of shared settings for file save plug-ins

2007-08-30 Thread gg
On Thu, 30 Aug 2007 11:07:40 +0200, Raphaël Quinet <[EMAIL PROTECTED]> wrote: > On Thu, 30 Aug 2007 00:57:44 +0200, [EMAIL PROTECTED] wrote: >> Gimp should not decide what is "better" because it cannot know what is >> required so cannot make that choice. >> >> This sort of "surprise" behaviour i

Re: [Gimp-developer] Annoying behavior of shared settings for file save plug-ins

2007-08-30 Thread Raphaël Quinet
On Thu, 30 Aug 2007 00:57:44 +0200, [EMAIL PROTECTED] wrote: > Gimp should not decide what is "better" because it cannot know what is > required so cannot make that choice. > > This sort of "surprise" behaviour is precisely the kind of thing I was > warning against in making covert changes to

Re: [Gimp-developer] Annoying behavior of shared settings for file save plug-ins

2007-08-30 Thread Alexander Rabtchevich
These are the best words I've heard on UI. A program cannot decide what is better for me because _I_have_not_told_it what _I_need_. This is a principle - it should be up to user, not a program. In a most common case of saving jpeg files I would like to be able to do via advanced mode: 1. See o

Re: [Gimp-developer] Annoying behavior of shared settings for file save plug-ins

2007-08-30 Thread Jakub Friedl
> I said when the new changes were being discussed that the "use image file > quality unless defaults are 'better'" was a bad way to go. I think that "use image file quality unless defaults are 'better'" is not thee problem. Problem is inheriting image quality between different images in one GIMP

Re: [Gimp-developer] Annoying behavior of shared settings for file save plug-ins

2007-08-29 Thread gg
On Thu, 30 Aug 2007 00:27:06 +0200, Raphaël Quinet <[EMAIL PROTECTED]> wrote: > Today, Jakub Friedl reported in #gimp that this behavior can lead to > surprising results, especially after the changes in the JPEG plug-in > that ensure that the initial quality level for the JPEG save dialog is > a

[Gimp-developer] Annoying behavior of shared settings for file save plug-ins

2007-08-29 Thread Raphaël Quinet
Most file-save plug-ins share a behavior inherited from other plug-ins: they save and retrieve their last values so that invoking them again will use the same parameters. As discussed previously, this behavior is fine for image filters but leads to annoying consequences for file plug-ins: if you s