123
edits
Changes
Jump to navigation
Jump to search
mLine 23:
Line 23: − + Line 36:
Line 36: − + − ==== Modify Journal ====+ − + − Store Activities' code(not .xo) in Journal and let users modify and and it.+ − + − ==== Modify Shell ====+ − + − − − ==== Create Views of Journal ==== − − ''to be continued'' Line 70:
Line 65: − * Sugar integration with ASLO+ − ** common tags+ − ** common objects(links to ASLO objects in Tags view - not only local)+ − ** easy way to post objects to ASLO+ + + + + + + + + + + − * 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
User:Alsroot/trash/Unified Objects (view source)
Revision as of 14:27, 1 March 2010
, 14:27, 1 March 2010moved Walter is a wanker 6/trash/Unified Objects to User:Alsroot/trash/Unified Objects over redirect: revert
==== 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. One of possible choices is Tag View(see proposal below). More over 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 ====
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 ==
* [[Features/Object Bundles]]
* [[Features/Activity Objects]]
* [[Features/Unified Browser for Objects]]
* [[Features/Object Collections]]
* [[Features/Peer to Peer Objects Sharing]]
* [[Activities/Library]]
to start activities from Journal's paths
==Pro==
==Pro==
==Going further==
==Going further==
==== Sugar integration with http://activities.sugarlabs.org/ ====
* upload to ASLO all kinds of Objects not only Activities
* common Tags
* 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
==== Sets of Objects ====
To support [http://dev.sugarlabs.org/ticket/540 meta bundles]