Another approach would be to replace the "save" metaphor with a "checkpoint" (I'm not wild about that word, but it'll work for now). The system would save continuously, and whenever you wanted to note a significant revision, you'd click "checkpoint". The app would let you add notes (as searchable metadata, of course) to describe the checkpoint and perhaps increment a version number as in Jonathan's version control observation.
The "checkpoint" log could also be used by other elements of the system. I'd like, for example, to have the version of a document that I emailed automatically checkpointed as such, so when I went into the document history I could easily find the version that I had sent to Sam, or that I had uploaded to a file server, etc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=40180 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... disc...@ixda.org Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
