Ethereal-dev: Re: [ethereal-dev] "Save" vs. "Save As"
> Hmmm - I would have gone in the other direction - to make the saved
> filename the current filename, simply because this is how vi & Emacs
> behave.
If I do "vi /etc/motd" and then, from within "vi", do ":w /tmp/motd"
("w" with a file name is the equivalent of "Save As"), the current file
is still "/etc/motd", i.e. if I do ":f", it reports that the file is
"/etc/motd", not "/tmp/motd".
And Network Monitor does the same with its "Save As".
Microsoft Word, however, changes the current file name on a "Save As".
I guess Microsoft is a big company, and not everybody who writes an
application talks to the other people writing applications....
Netscape Composer does the same thing as Word.
The online Macintosh Human Interface Guidelines says, at
http://developer.apple.com/techpubs/mac/HIGuidelines/HIGuidelines-99.html
the following:
The Save As dialog box allows the user to provide a name for the
document and to choose where it will be saved. Leave the
document open and active.
When the user opens a document, makes changes to it, and then
chooses Save As, don't change the original document. Save the
changed version of the document under the new name. The active
document is no longer the one the user opened, but rather the
new one with the new name.
So I'll assume the NetMon guys didn't read that (the copy of *The
Windows Interface: An Application Design Guide* I have doesn't seem to
say what "Save As" should do, so maybe Microsoft doesn't think it needs
to be standardized), and ignore them, and have "Save As" make the new
file name be the current file name.
The Microsoft book, and the Mac HI Guidelines, say that if something
hasn't yet been saved, "Save" should act like "Save As" (or, at least,
should pop up a file selection box), so I'll do that as well - and have
"Save" grayed out, for now, unless the file hasn't been saved (as we
don't currently let you edit the capture, so, once you've saved it,
there's never going to be anything unsaved).
