Sugar Labs

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

← Older edit
No edit summary
 
(35 intermediate revisions by 4 users not shown)
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. 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 ====


Instead of having:
Instead of having:
* Activity bundles(.xo in Journal or in /usr)
* Activity bundles(.xo in Journal)
* Content bundles(.xol in Journal)
* Content bundles(.xol in Journal)
* Activities(from Home View)
* Activities(from Home View and placed to /usr or ~/Activities)
* Content(in meaning of [[Unified Bundles]])
* Content(in meaning of [[Unified Bundles]])
* Journal Objects(from old Journal View)
* Journal Objects(from old Journal View)
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 ==


To achieve this target, instead of inventing new versioning scheme in sugar
* [[Features/Object Bundles]]
(in addition to Journal), I propose treat Activities as regular Journal objects.
* [[Features/Activity Objects]]
 
* [[Features/Unified Browser for Objects]]
Home View should mutate from "storage" of activities to Tags View of
* [[Features/Object Collections]]
Journal objects. It could have tags cloud and etc.
* [[Features/Peer to Peer Objects Sharing]]
 
* [[Activities/Library]]
And final, all sugar stuff could be treated as Objects in Journal(Journal as a technical term not Journal View). User could operate them from various View backends: Tags View, "classical" Home and Journal Views.


==Pro==
==Pro==
Line 66: Line 65:
==Going further==
==Going further==


* Sugar integration with ASLO
==== 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
Retrieved from "https://wiki.sugarlabs.org/go/User:Alsroot/trash/Unified_Objects"