Re: [Gimp-developer] [FEATURE] Some plug-in settings should be persistent accross sessions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Aug 05, 2003 at 02:03:09PM +0200, RaphaÃl Quinet <quinet@xxxxxxxxxx> wrote:
> Look at the comment that I recently added in:
>   http://bugzilla.gnome.org/show_bug.cgi?id=119032
> IMHO, global parasites and immediate changes to the settings could
> make sense for the plug-ins that are used as filters, but not for the
> file plug-ins.  For the file plug-ins, the settings should be a
> per-image property that is not affected by the changes made to the
> other images.

As I said (or wanted to say, but didn't :): the perl plug-ins do exactly
that, as tehy attach themselves as global and per-image parasite.

> It is unfortunate that the file plug-ins and the other filters are all
> called "plug-ins", because they behave differently.  What may make

the problem in pelr is the UI. When I added buttons for the various
options to recall defaults it became a bit complicated for the user to
understand.

Your proposal to have two difefrent default strategies (not reflected in
the UI of the plug-in), i.e. file == per-image and global, filters ==
global only (the latter is not gimp-perl's behaviour, though) might make a
lot of sense without cluttering the UI.

> be a property of the filter itself: it is reasonable to expect that
> applying the same filter to a different image will use the same
> settings as last time.

Personally, I think it's equally reasonable to have the same settings as
used on the same image earlier, though. Both are equally useful to me.

For file-plug-ins, a fallback to the global default is also useful,
although not as useful as with filters.

> This confusion between what is the "right" behavior for a filter and
> for a file plug-in has caused some problems before.  See for example:

What would be good would be a clever way to enable the user to chose, and
have sensible defaults so the user need not to in most cases.

> > For the plug-in writer this is fully transparent (if she uses Gimp::Fu).
> 
> Yes, this is nice.  However, I am not sure that modifying the defaults
> every time (without user confirmation) is a really good idea.

It as, at best, a good guess of what should be done. gimp-perl was mostly
modelled after what other plug-ins do in the case of LAST_RUN_VALS.

> different results because of what they did previously.  This would be
> fine if they knew why (e.g., they had explicitely saved a default set
> of options) but this is not so obvious now.

There is always the button to reset to defaults (and another button to
use the previous values). Adding more buttons was not possible (clutter),
while a menu with various choices is not quick to use.

-- 
      -----==-                                             |
      ----==-- _                                           |
      ---==---(_)__  __ ____  __       Marc Lehmann      +--
      --==---/ / _ \/ // /\ \/ /       pcg@xxxxxxxx      |e|
      -=====/_/_//_/\_,_/ /_/\_\       XX11-RIPE         --+
    The choice of a GNU generation                       |
                                                         |

[Index of Archives]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [GIMP for Windows]     [KDE]     [GEGL]     [Gimp's Home]     [Gimp on GUI]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux