Re: Next release of GUI and backends?

[Nicola Pero]

> > the other thing I'm not sure is the save panel showing the panel when you
> > select a file which already exists - the problem I see is that the
> > user/application looses control of this thing - the panel can't be
> > disabled...
> 
> What do you mean exactly ? The application can't stop the modal loop ?

Hm - I mean in general that enforcing too much these kinds of things in
the library makes it difficult to work around them in special cases in
applications which need to work around them.

For example imagine that an application is letting the user choose to
which file it wants to redirect some logs.  The logs will be _appended_ to
the file.

Should it use the open panel or the save panel ?

The log file might not exist yet, so I would say the open panel is not
appropriate, because the open panel is meant for opening existing files
(does the open panel allow you at all to select a non-existing file ?).

On the other side, if you use the save panel, then if the user chooses an
existing file, the application does not want to display the popup panel
saying `the file already exists, do you want to replace it' - because it's
not going to replace it, but only to append to it.  Or perhaps it might
want to replace this popup panel with something saying `the file already
exists, do you want to append to it or to replace it ?'.


> > the message in the panel can't be modified... (will the
> > message be appropriate for all usages of the save panel ?)
> 
> I don't know if you can modify the message, apart for language/localization
> stuff.

 
> > Does openstep/apple stuff have this panel ? 
> 
> OS has it.

Ok - I suppose then there could be a reasonable way to work around it.  
Perhaps using the open panel in that case might work ?