|
|
| 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 ====
| | See [[Activities/Library]]. |
| | |
| Store all Activity versions(not only .xo) in Journal and let users modify and run it
| |
| * identify the whole activity by jobject_id
| |
| * support life cycle of regular Journal Objects
| |
| * do not rely on external modules like 9p kernel module or FUSE
| |
| | |
| ==== 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
| |
| | |
| ==== Versions of Journal Objects ====
| |
| | |
| We should differentiate at least Activities by versions thus Journal Objects [[Version_support_for_datastore|should have versions]].
| |
| | |
| ==== Create Views of Journal ====
| |
| | |
| * Views could be regular activities(installed from Activity Library) and registered in Shell as Views
| |
|
| |
|
| ==Pro== | | ==Pro== |