[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-look
Subject: Re: KDE Standards - Menus - Options
From: Boris Povazay <boris () jouh ! at>
Date: 1999-09-24 11:38:38
[Download RAW message or body]
Stefan Taferner wrote:
>
> > I am not sure if options should be saved manually or not.
> >
> > _IF_ they are to be saved manually, the application should ask the user whether he wants
> > to save his/her settings (if he/she hasn't done so) when he/she quits.
>
> I have problems with applications that ask strange questions when they are
> supposed to quit. The only situation when this is IMO appropriate is when the
> changes in the document would be lost.
>
> Unsaved settings should open such a dialog.
>
> > It would be nice if some detection could be added which checks whether another
> > application has changed the settings in the mean-time.
>
> Possible behaviour is:
> a) merge the settings or
> b) simply replace the settings or
> b) just not save them or
> d) ask the user?
It often happens that users want to leave the workplace within a second (say: shut down
desktop and with it all applications)
So it would be useful to ask this question:
a) in advance (when the settings are changed the first time: Save settings on exit?)
b) save both configurations and allow to distinguish at the next start. (This woud mean to
allow multiple settings to be saved)
This also applies to the save? option:
When the program is quit and the data has not been saved there the requester should pop up
AND dissapear after a certain time. The data would be saved automatically with an internal
name. (At best the first two words and the creation date)
I guess it would even be better if the document name would be specified at the creation - a
requester should pop up!
In my opinion the system should save all data also when a complete novice uses it.
ciao BoP
--
http://kde.jouh.at - bp@jouh.at
Boris Povazay
[Attachment #3 (text/html)]
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Stefan Taferner wrote:
<blockquote TYPE=CITE>
<br>> I am not sure if options should be saved manually or not.
<br>>
<br>> _IF_ they are to be saved manually, the application should ask the
user whether he wants
<br>> to save his/her settings (if he/she hasn't done so) when he/she quits.
<p>I have problems with applications that ask strange questions when they
are
<br>supposed to quit. The only situation when this is IMO appropriate is
when the
<br>changes in the document would be lost.
<p>Unsaved settings should open such a dialog.
<p>> It would be nice if some detection could be added which checks whether
another
<br>> application has changed the settings in the mean-time.
<p>Possible behaviour is:
<br>a) merge the settings or
<br>b) simply replace the settings or
<br>b) just not save them or
<br>d) ask the user?</blockquote>
It often happens that users want to leave the workplace within a second
(say: shut down desktop and with it all applications)
<br>So it would be useful to ask this question:
<br>a) in advance (when the settings are changed the first time: Save
settings on exit?)
<br>b) save both configurations and allow to distinguish at the next start.
(This woud mean to allow multiple settings to be saved)
<p>This also applies to the save? option:
<br>When the program is quit and the data has not been saved there the
requester should pop up AND dissapear after a certain time. The data would
be saved automatically with an internal name. (At best the first two words
and the creation date)
<p>I guess it would even be better if the document name would be specified
at the creation - a requester should pop up!
<p>In my opinion the system should save all data also when a complete novice
uses it.
<p>ciao BoP
<pre>--
<A HREF="http://kde.jouh.at">http://kde.jouh.at</A> - bp@jouh.at
Boris Povazay</pre>
</html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic