Re: RGSG

[sun <as387 yfn ysu edu>]

Dan Kaminsky wrote:

> >no, you don't exit game files. you exit game applications. it's possible
> >to close a file without closing an application, and this is an entirely
> >separate operation and must be kept distinctly different.
> 
> Kinda hard to keep files open after exiting the application, also kind hard
> to open up new files or save files or do anything.

ambiguity between the "file->close" command and the "application->quit"
command is a terrible thing to invite. i've given you my reasons why
file->quit is bad, can you give me reasons why application->quit is bad?
i'm firmly convinced we're doing the right thing by creating a new menu
for application-wide command choices.

> It's not the place of the app programmer to decide if copying is going to be
> used.  "Oh, this is just a small app, who is going to want to copy text out
> of it?"  OK, so here I am, dealing with the text output of a window that's
> showing me all the files on my system that fulfill some kind of random
> category, and look, I can't copy.

okay, you and i agree on this. edit is a wonderful, terrific thing, and
if the mac os hadn't made it a standard in gui's, the evolution of
computers as user-centric simply would not have taken place.

even mac apps which aren't aimed at content creation often don't have
edit menus, though. imo we can do one better than require an "edit" menu
of an application whose only choice in that menu would be "copy." simply
acknowledge that not all programs require textual or graphical input and
help me figure out a better place to put the "copy" command to avoid the
edit menu with one choice.
--
"They that can give up essential liberty to obtain a little temporary
safety
deserve neither liberty nor safety." --Benjamin Franklin