Talk:OLPC Human Interface Guidelines/Core Ideas

From OLPC
< Talk:OLPC Human Interface Guidelines
Revision as of 23:13, 16 January 2008 by Walter (talk | contribs) (Reverted edits by 222.235.64.181 (Talk); changed back to last version by Eben)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Representing Limited Memory

How does the idea of Journal work with the idea of no hard drive and limited storage? Is there a metaphor like the application ring that shows how big each kept object is and how much capacity is left for more?

  • We're not exactly sure how this is going to be represented in the journal. There will be some indication of the size of each entry, but whether this is some abstraction or a straight value in MB, we don't know yet. Additionally, we hope to provide some broader view of the capacity of the journal itself, and intend to provide natural ways for old, unused, and unwanted entries to "fall off" the end. Automatic backups to the school servers will prevent permanent loss of data, allowing this type of "cleanup" to happen as needed. Of course, this will require much testing to get right. - Eben 10:48, 13 December 2006 (EST)