| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Add self-restore capability to Backup/Restore sample app | Chris Tate | 2010-11-16 | 1 | -1/+20 |
| | | | | | | | | | | | | The Backup/Restore sample application now provides a "restore my own last-known-good data" button. When it is clicked the app will run the standard public BackupManager.requestRestore() operation. (This was the one aspect of the public API that was not previously exercised by the sample app.) Change-Id: I8abcfbad4b27b35fe9fafbbb97f89bac1d7a668c | ||||
| * | Backup/Restore sample application | Christopher Tate | 2010-04-06 | 4 | -0/+800 |
| A very simple application: one activity, with a few bits of persistent data that are updated live by the activity. To that are added a few alternative agent implementations, to illustrate various approaches and tradeoffs when implementing a backup/restore agent. In particular, there are example agents that do everything "by hand," either record-by-record or by directly backing up the app's entire persistent data file; plus an example agent that illustrates how very easy it is to implement the latter using the OS-provided helpers. Part of bug #2545514 Change-Id: Iaca33a5113406360c23d6e2e59eb012f9f1e9400 | |||||
 |
index : development.git | |
| development |
| summaryrefslogtreecommitdiff |