[squeak-dev] Survey: Cmd-s to close a dialog? (was: 5.3, focus follows mouse, image "save as...")
Tim Johnson
digit at sonic.net
Mon Aug 3 17:27:16 UTC 2020
The Orange Book specifically lists 'accept' in the Menu Command Index,
page 510 in my edition. It separates out its instances in the book by
'to compile' and 'to store'. The second paragraph on page 37
describes what happens if a user tries to dismiss a dialog with
changes, without the user clicking 'accept' or 'cancel'.
I realize this is all MVC and ancient history by now (?), but I first
started learning & understanding Squeak by using the Orange Book &
Blue Book in Squeak's early MVC and Morphic environments. Squeak
hadn't diverged much, in MVC or in Morphic, by 3.8/3.9/3.10 or so.
Nowadays, I'm not sure how helpful it is that I am mentioning a 36-
year-old book. :)
The definition of 'undo' on page 58 is also interesting: it seems
like it was never meant to replace 'accept'/'cancel', but was meant to
exist beside these and remain a tool of its own. Thus the MVC
environment could be said to have given the user two levels of 'undo'.
On Aug 1, 2020, at 4:22 PM, Chris Muller wrote:
> It used to be that Cmd+s would remember the contents of text fields
> in windows, so that if I then made further modifications to it which
> I *then* change my mind about, I could press Cmd+l (lowercase L), to
> restore it to the last-accepted state. I really miss that in
> Workspaces and inspectors.
>
> But it should never close a multifield dialog, IMO. Maybe it
> shouldn't even for FillInTheBlank either, for consistency.
>
> - Chris
>
> On Sat, Aug 1, 2020 at 7:28 AM Jakob Reschke
> <forums.jakob at resfarm.de> wrote:
> Hi Chris,
>
> Chris Muller <asqueaker at gmail.com> schrieb am Fr., 31. Juli 2020,
> 22:47:
>
> *but*
>
> It would be a problem in dialogues with several input fields though;
> see for example the SqueakMap edit tool.
>
> That's different. Not modal. Just like the code browser, where you
> don't want Cmd+s to close the code browser. But for modal dialogs,
> yes, ...
>
> What do you think about windows that are input requesting dialogs,
> but not modal, as in: prevents other interactions while it is open?
> The commit dialog of the Git Browser falls into this category. But
> even though the Monticello save dialog will claim to be modal if its
> process is interrupted, it isn't really since you can do other
> things while it is open. So you could also answer with the
> Monticello save window in mind. Or the Monticello merge tool, which
> does not have text input for a change.
>
> Kind regards,
> Jakob
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20200803/bc20d93a/attachment.html>
More information about the Squeak-dev
mailing list
|