Development Team/Project Ideas: Difference between revisions

Line 151:

* Accessibility Support: Sugar currently doesn't have anything available for the visually impaired.

==== Research projects: code exists, but more-or-less unpolished, and it would be awesome to get one of these really working well ==

==== Research projects: code exists, but more-or-less unpolished, and it would be awesome to get one of these really working well ====

* [[DevelopmentTeam/DatastoreRewrite#Versioned_entries_.28not_fulfilled_yet.29|Version support]] for [[Journal]] / [[DevelopmentTeam/Almanac/sugar.datastore.datastore|DataStore]]: create a new version for each (automatic or manual) Keep with the same name / tags, create a branch if metadata was changed. Allow the user to access "older" versions (Keeping and "old" version will create a branch) and view ancestry (tree of branches). See also (old) [http://wiki.laptop.org/go/Olpcfs Olpcfs] and (newer; less-documented; based on an RCS backend and a relatively small amount of fuse magic) [http://dev.laptop.org/git/users/cscott/olpcfs2/ olpcfs2].

* There is also [http://wiki.laptop.org/go/Journal%2C_reloaded Journal, reloaded]], another research project with real code behind it that is promising but languishing. In this case, the idea is to make the journal "tagging" view transparently compatible with a traditional hierarchical directory structure.

@@ Line 151: / Line 151: @@
 * Accessibility Support: Sugar currently doesn't have anything available for the visually impaired.
-==== Research projects: code exists, but more-or-less unpolished, and it would be awesome to get one of these really working well ==
+==== Research projects: code exists, but more-or-less unpolished, and it would be awesome to get one of these really working well ====
 * [[DevelopmentTeam/DatastoreRewrite#Versioned_entries_.28not_fulfilled_yet.29|Version support]] for [[Journal]] / [[DevelopmentTeam/Almanac/sugar.datastore.datastore|DataStore]]: create a new version for each (automatic or manual) Keep with the same name / tags, create a branch if metadata was changed. Allow the user to access "older" versions (Keeping and "old" version will create a branch) and view ancestry (tree of branches). See also (old) [http://wiki.laptop.org/go/Olpcfs Olpcfs] and (newer; less-documented; based on an RCS backend and a relatively small amount of fuse magic) [http://dev.laptop.org/git/users/cscott/olpcfs2/ olpcfs2].
 * There is also [http://wiki.laptop.org/go/Journal%2C_reloaded Journal, reloaded]], another research project with real code behind it that is promising but languishing. In this case, the idea is to make the journal "tagging" view transparently compatible with a traditional hierarchical directory structure.