Line 23: |
Line 23: |
| ==== More relevant View(s) of Journal ==== | | ==== More relevant View(s) of Journal ==== |
| | | |
− | Having all these Objects user should have more powerful View to threat them. See [http://wiki.laptop.org/go/Journal%2C_reloaded Journal reloaded] and [[Design_Team/Designs/Jou rnal#01|Journal mockups]] for proposals. Moreover we could emulate "classical" Home and Journal Views. | + | Having all these Objects user should have more powerful View to threat them. See [http://wiki.laptop.org/go/Journal%2C_reloaded Journal reloaded] and [[Design_Team/Designs/Journal#01|Journal mockups]] for proposals. Moreover we could emulate "classical" Home and Journal Views. |
| | | |
| ==== Summarising ==== | | ==== Summarising ==== |
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 Journal ====
| + | * [[Features/Object Bundles]] |
− | | + | * [[Features/Activity Objects]] |
− | * Store all Activity versions(not .xo) in Journal and let users modify and run it. | + | * [[Features/Unified Browser for Objects]] |
− | | + | * [[Features/Object Collections]] |
− | ==== Modify Shell ====
| + | * [[Features/Peer to Peer Objects Sharing]] |
− | | + | * [[Activities/Library]] |
− | 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 70: |
Line 65: |
| ==Going further== | | ==Going further== |
| | | |
− | * 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 |
− | ** easy way to post objects to ASLO
| + | * common Objects(links to ASLO objects in Tags View) |
| + | * 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 ==== |
| + | * 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) |
| + | * basic system activities could be installed by default while first creating of .sugar instance |
| + | |
| + | ==== Sugar Infection ==== |
| + | Auto migration of activities before joining to session which uses another version of activity |
| | | |
− | * System activities could be stored in Journal as well
| + | ==== Sets of Objects ==== |
− | ** main purpose - we should encourage user to change all activities(including system ones)
| + | To support [http://dev.sugarlabs.org/ticket/540 meta bundles] |
− | ** 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
| |