Slightly off-topic, but everyone discussing this (IMHO) should take a look at what scratchpad[1] does. It is a very basic text editor right now, but in particular, it implements instant-apply saving and marking of revisions. IMHO, that's the route gedit should think about going instead of doing lots of complicated stuff to unbreak broken concepts like 'save'.
Luis [1] http://www.gnomefiles.org/app.php?soft_id=760 On Fri, 4 Mar 2005 15:02:22 +0100, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > "Save" means something to everyone who has used a computer: commit > my > > > changes "permanently", don't close the document. "Save a copy" is a > > > variation on that which I thought I knew, but the extra words *add > > > confusion* because now I don't know what aspects of "save" are being > > > performed. "Copy to" tells me exactly what is going to happen, and I > > > find clearer because it isn't corrupted with my preconceived notions > of > > > what "save" does. > > This isn't a very good solution as it clashes with items in the edit > menu. > You need something that clearly states that this generates a file in the > same format as "Save". > What do you copy to? A clipboard? A file? Some magic buffer? > I think I've prefer "Export" to "Copy to", even if this is even more > difficult for the user to interpret. > > John > > _______________________________________________ > Usability mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/usability > _______________________________________________ Usability mailing list [email protected] http://mail.gnome.org/mailman/listinfo/usability
