Re: [Nautilus-list] Re: Allowing view components to provide editing (UI and architecture issues)
- From: Maciej Stachowiak <mjs noisehavoc org>
- To: nautilus-list lists eazel com
- Subject: Re: [Nautilus-list] Re: Allowing view components to provide editing (UI and architecture issues)
- Date: Fri, 3 Aug 2001 15:10:26 -0700
On 03Aug2001 10:59PM (+0200), Guillermo S. Romero / Familia Romero wrote:
> mjs noisehavoc org (2001-08-03 at 1313.35 -0700):
> > > Or, if you want to be consistent with the more Mac-alike button ordering
> > > that's been proposed for 2.0, rather than with the rest of Nautilus:
> > > [Cancel] [Don't Save] [Save]
> > Thanks for the suggestion, Calum. The problem I see with this proposal
> > is that it's unclear from the text what Cancel does, and in
> > particular, how it is different from Don't Save. Any suggestions for
> > that?
>
> "Save" saves and "do not save" does not save, but both close the doc.
> "Cancel" does nothing, it aborts everything, nothing is changed in
> disk or screen. That is the idea we talked about in the other lists,
> Cancel is a "oops, I did not want this dialog" or "I changed my mind,
> I want to keep doing things".
>
Yes, I know that and you know that, but will it be clear to someone
who did not design the app?
- Maciej
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]