Chapter 13: Rethinking Files and Save

Talks about how every file exists in two places at once: in memory and on disk.

Not saving is not as probably as SAVING, so why ask and give it each 50/50. An application must assume a user wants a file saved and constantly save it for them.

Power users see the "SAVE AS" as a way to disregard the changes made in a document to revert back to the original. This should be replaced with a REVERT feature instead.

An interesting observation on transportable disks. They actually show down the system.

Allow users to rename a file by clicking the title bar at the top of the window, as well as re-position the file on their system. File properties (such as jpeg, gif, etc) should not be determined along with the SAVE process.

Archiving should be a function. Presentation of milestones for the user to revert back to.

Designing a Unified File Presentation Model.

Snapshot should be a feature.

All of these changes would lead to a redesign of the FILE menu.