Changes

Version support for datastore/Proposal (view source)

Revision as of 13:52, 8 April 2009

3 bytes added , 13:52, 8 April 2009

m

fix camelcase links

Line 17: Line 17:

==About my project==

−

* Name of project: Version support for [[Development Team/~~DatastoreRewrite~~|data store]] / [[Design_Team/Designs/Journal|Journal]]

+

* Name of project: Version support for [[Development Team/Datastore Rewrite|data store]] / [[Design_Team/Designs/Journal|Journal]]

* Technologies used: The ones currently in use by the data store / journal. The bonus part might introduce additional ones (e.g. sqlite) for indexing.

Line 34: Line 34:

[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#The_Journal original design concept]

−

for the Journal, but [[Development Team/~~DatastoreRewrite~~#Versioned_entries_.28not_fulfilled_yet.29|hasn't been finished yet]].

+

for the Journal, but [[Development Team/Datastore Rewrite#Versioned_entries_.28not_fulfilled_yet.29|hasn't been finished yet]].

There are several prototypes ([http://wiki.laptop.org/go/Olpcfs Olpcfs], [http://dev.laptop.org/git/users/cscott/olpcfs2/ olpcfs2])

Line 46: Line 46:

For this reason, I don't believe that any of these prototypes will mature enough to get integrated

in Sugar even mid-term. My project focusses on the version support instead, enhancing the

−

[[Development Team/~~DatastoreRewrite~~|current data store]] instead of replacing it, with the Journal as the only

+

[[Development Team/Datastore Rewrite|current data store]] instead of replacing it, with the Journal as the only

intended user of the versioning API (though, at least in theory, regular activities could access it as well).

Dfarning

2,751

edits