Changes

and happens automatically), but rather add a new version to the entry. Enhance the UI to allow easy (and simple to understand)  

and happens automatically), but rather add a new version to the entry. Enhance the UI to allow easy (and simple to understand)  

access to "old" versions, including modification (which means automatically saving in a new branch).

access to "old" versions, including modification (which means automatically saving in a new branch).

As "easy and simple to understand" isn't actually easy to implement, I'll concentrate on enhancing (by listing

As "easy and simple to understand" isn't actually easy to implement, I'll concentrate on enhancing the current Journal view

each version separately) the linear, time-based view of the current

by adding previous/next buttons to the details view of each entry for the primary part of the project.  

[[Design_Team/Designs/Journal|Journal design]] for the primary part of the project. Adding a version tree details view

Adding a version tree details view and possibly other ways of presenting versions are planned for the optional  

and possibly other ways of presenting versions are planned for the optional (based on remaining time) "bonus part".

(based on remaining time) "bonus part". Metadata is going to be part of each version (and mutable without creating

a new version) at first.

Version support for data store / Journal already  

Version support for data store / Journal already  

[http://wiki.laptop.org/go/OLPC_Human_Interface_Guidelines/The_Laptop_Experience#Implicit_Versioning_System was part of] the  

[http://wiki.laptop.org/go/OLPC_Human_Interface_Guidelines/The_Laptop_Experience#Implicit_Versioning_System was part of] the