Ethereal-dev: Re: Re: Re: Re: [Ethereal-dev] "usability extensions"

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Ulf Lamping <ulf.lamping@xxxxxx>
Date: Tue, 3 Sep 2002 01:36:59 +0200
Guy Harris <gharris@xxxxxxxxx> schrieb am 03.09.02 00:50:28:
> On Tue, Sep 03, 2002 at 12:44:21AM +0200, Ulf Lamping wrote:
> > I think seperate menu items would be even more confusing for a the user.
> 
> Perhaps, but one problem with the existing scheme is that it cannot
> distinguish between permanent changes (i.e., changes the user would want
> saved to their preference file) and temporary changes, so if they've
> made some temporary preference changes, and then make a permanent change
> and click "Save", they've just saved the permanent change *and*
> temporary changes they might even have forgotten that they've made.
> 
> Explicitly distinguishing between your initial/default/permanent
> settings and your current settings, although it introduces a New Concept
> that users have to think about, might, overall, be easier to understand.

I currently have no good idea, how the dialogs and the implementation itself could look like :-(
But I think I have understand what you mean.

> 
> > What do you think of comparing, at program quit, the current with the saved 
> > settings and popup a dialogbox if they are different,
> > asking to save or ignore the changes made.
> > This should be done for every setting file seperately.
> 
> That strikes me as rather clumsy.
> 
> For one thing, I don't know whether this is a problem for settings other
> than the preference settings, so, for the other settings, it might be
> worth just having them just save by default.

No problem with that.

> 
> Furthermore, it would ask you whether you want to save the current
> preference settings, but you might not know whether the current settings
> are the ones you want saved (you might've *forgotten* that you tweaked
> some protocol preference), so you might not know what the right answer
> is - and the answer you *want* might be to have some changes saved and
> others not saved.

Another approach would be to ask the user at program exit: "Do you really want to quit, some preferences are not saved?" or something that way. With three buttons:

"Save": Save and exit program
"Quit": Quit program without saving
"Cancel": return to program and change nothing


To summarize the setting files (as currently on my windows machine), with the actions made, if I get you right:

cfilters (saved at program exit)
colorfilters (saved at program exit)
dfilters (saved at program exit)
preferences (dialog box, described above)

And in future:
recent (saved at program exit)
protocols (saved at program exit)

Maybe the protocols settings could also be put inside the preferences file! As the protocol specific settings are also there.

Regards, ULFL
______________________________________________________________________________
Die clevere Geldreserve: der DiBa-Privatkredit. Funktioniert wie ein Dispo, 
ist aber viel gunstiger! Alle Infos: http://diba.web.de/?mc=021104