Sugar Labs

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

← Older edit
 
(7 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 ====
 
Sugar Shell related hacks to start activities from Journal's paths
* to start activity Shell should fetch Activity jobjects in RO mode
* Shell should restrict user by using only one Activity jobject(in RW mode) in the same time
 
==== Create Views of Journal ====
 
* Views could be regular activities(installed from Activity Library) and registered in Shell as Views


==Pro==
==Pro==
Retrieved from "https://wiki.sugarlabs.org/go/User:Alsroot/trash/Unified_Objects"