Talk:OLPC Human Interface Guidelines/Core Ideas: Difference between revisions

From OLPC
Jump to navigation Jump to search
(racalri)
m (Reverted edits by 222.235.64.181 (Talk); changed back to last version by Eben)
 
Line 1: Line 1:
racacdrono
====Representing Limited Memory====
====Representing Limited Memory====
How does the idea of Journal work with the idea of no hard drive and limited storage?
How does the idea of Journal work with the idea of no hard drive and limited storage?

Latest revision as of 03:13, 17 January 2008

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)