Erwin-K wrote:
Some of the article seems confusing. Are all your applications running at once if there are no 'Quit' buttons?
They quit automatically when you close your document window. Anyhow, that's what happens with Internet Explorer.
I also have misgivings about the idea of no application "quit" menu item (and the other side of the coin: auto-quit when the file is closed). This is also the way BeOS works. If you're writing something in the text editor, when you finish your document and close it, the text editor also closes. This can be a real drag in a program like a graphics editor, where you are constantly opening, saving and closing image files. You definitely don't want to have to restart your program every time you close and open a file when you're working on a set of files. I cope with that default behavior by opening a new "doorstop" file for the sole purpose of keeping the program running while I open, work on, and close my "real" files. Not exactly an elegant solution.
Maybe it's true that the quit button exposes an implementation detail, but it's a detail that I don't mind having access to. Yes, it's nifty that the program goes away when you're through using it, but often you're
not through with the program even though you were through with the first document you used it for. Then the metaphor is a power saw that you have to get out of the tool box for every new board you want to cut -- lots of wasted time and effort here. At the very least this should be a user configuration option.
-- gary_c
