Sugar Labs

User:Alsroot/trash/Unified Objects: Difference between revisions

← Older edit
 
(16 intermediate revisions by 4 users not shown)
Line 36: Line 36:
We could have only Objects in Journal(in terms of "storage" not Journal View). And operate these Objects in one unified way - Create(or copy existed) in Journal, Reuse(Change) them in Journal and Share Journal Objects.
We could have only Objects in Journal(in terms of "storage" not Journal View). And operate these Objects in one unified way - Create(or copy existed) in Journal, Reuse(Change) them in Journal and Share Journal Objects.


== Proposal ==
== Implementation ==


==== Modify sugar-datastore ====
* [[Features/Object Bundles]]
 
* [[Features/Activity Objects]]
* Store all Activity versions(not only .xo) in Journal and let users modify and run it
* [[Features/Unified Browser for Objects]]
** identify the whole activity by jobject_id
* [[Features/Object Collections]]
** support life cycle of regular Journal Objects
* [[Features/Peer to Peer Objects Sharing]]
** do not rely on external modules like 9p kernel module or FUSE
* [[Activities/Library]]
 
==== Modify Shell ====
 
to start activities from Journal's paths
 
==== Create Views of Journal ====
 
* Views could be regular activities(installed from Activity Library) and registered in Shell as Views


==Pro==
==Pro==
Line 74: Line 66:


==== Sugar integration with http://activities.sugarlabs.org/ ====
==== Sugar integration with http://activities.sugarlabs.org/ ====
* common tags
* upload to ASLO all kinds of Objects not only Activities
* common objects(links to ASLO objects in Tags view - not only local)
* common Tags
* common Objects(links to ASLO objects in Tags View)
* easy way to post objects to ASLO
* easy way to post objects to ASLO
* Objects updater which uses Activity Library as a source of updates


==== System activities could be stored in Journal as well ====
==== System activities could be stored in Journal as well ====
** main purpose - we should encourage user to change all activities(including system ones)
* main purpose - we should encourage user to change all activities(including system ones)
** physically these .xo could be stored in /usr/share but user should have access to them from the Journal(Tags View)
* physically these .xo could be stored in /usr/share but user should have access to them from the Journal(Tags View)
** basic system activities could be installed by default while first creating of .sugar instance
* basic system activities could be installed by default while first creating of .sugar instance


==== Sugar Infection ====
==== Sugar Infection ====
Migrate activities between friends
Auto migration of activities before joining to session which uses another version of activity


==== Sets of Objects ====
==== Sets of Objects ====
To support [http://dev.sugarlabs.org/ticket/540 meta bundles]
To support [http://dev.sugarlabs.org/ticket/540 meta bundles]
Retrieved from "https://wiki.sugarlabs.org/go/User:Alsroot/trash/Unified_Objects"