From Interaction-Patterns.org

Contents 1 Autosave 1.1 Quick Summary 1.2 Visual Examples 1.3 Examples found on the World Wide Web 1.4 Possible Field of Application 1.5 Possible Solution 1.6 Rationale 1.7 This pattern is being used to 1.8 Source

[edit] Autosave

[edit] Quick Summary

This pattern isn't necessarily an interaction pattern in the sense that user are directly interacting with the system. Moreover, this pattern is functionality that the system the user offers. Autosave regularly saves the data the user has been entering before. This decreases the likelihood of data loss.

If there is that to be saved this function makes it possible that the system itself is saving once in a while or the moment new information is been added. Includes a Feeback: System telling the user "Saved". First Process --> then saved.

[edit] Visual Examples

Found at docs.google.com

[edit] Examples found on the World Wide Web

• http://extjs.com/deploy/dev/examples/statusbar/statusbar-demo.html

[edit] Possible Field of Application

• In word processor like Google Docs (http://docs.google.com)

[edit] Possible Solution

It's a programming problem so at this place we would add code, right?

[edit] Rationale

[edit] This pattern is being used to

• Prevent Errors
• Save Data

[edit] Source

• http://friedhold-matz.blogspot.com/2007/09/autocomplete-combobox.html
• http://ajaxpatterns.org/Suggestion
• http://serversideguy.blogspot.com/2004/12/google-suggest-dissected.html
• http://dojotoolkit.org/forum/dijit-dijit-0-9/dijit-development-discussion/combobox-behavior