123
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: − ===Preamble===+ − (expanding of [[Unified Bundles]] idea)+ − Separation all objects on verbs and nouns can be failed in some cases -+ − + − sugar was designed for - Create, Reuse, Share.+ − This CRS scheme works(more or less at present) for content since we have+ − − We should encourage people CRS theirs activities as well. Only one but -+ − current sugar cannot work with many versions installed. At the same time − this multi versioning is cornerstone of CRS activities since we have − (should have) many versions of one particular activity installed on the − same box. And these versions could include "home made" activities not − only "official" ones. User should have possibility to treat all these − versions(of one activity) effectively to CRS them. − ===Proposal===+ − To achieve this target, instead of inventing new versioning scheme in sugar+ − − Home View should mutate from "storage" of activities to Tags View of+ − − + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 39:
Line 56: − ===Contra===+ Line 46:
Line 63: − ===Going further===+ + + + + + + + + + + + + + + + − * 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
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
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TOCright}}
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TOCright}}
== Preamble ==
Major ideas of this proposal.
''NOTE''
and moreover it will be failed when sugar will be used for purposes that
# This sections talks not about bundles(activity or content) but about Activities and Content themselves.
# Proposal differentiate Journal(as "storage") and Journal View(as view on "storage")
==== Activities as Journal Objects ====
Journal to store objects, but what about Activities?
Separation all objects to verbs and nouns can be failed in some cases - and moreover its failed when sugar is used for purposes that it was designed for - Create, Reuse, Share.
This CRS scheme works(more or less at present) for content since we have Journal to store objects, but what about Activities?
We should encourage people CRS theirs activities as well. Only one but - current sugar cannot work with many versions installed. At the same time this multi versioning is cornerstone of CRS activities since we have(should have) many versions of one particular activity installed on the same box. And these versions could include "home made" activities not only "official" ones. User should have possibility to treat all these versions(of one activity) effectively to CRS them.
(in addition to Journal), I propose treat Activities as regular Journal objects.
==== Journal Objects is a 1st class Objects as well ====
Journal objects. It could have tags cloud and etc.
===Pro===
[[Unified Bundles]] shows that Content(.xol) are the same level Objects as Activities. We could also extrapolate this idea to regular Journal Objects - it should mean user could have access to Activities, Content and Journal Objects from the same place.
==== 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/Journal#01|Journal mockups]] for proposals. Moreover we could emulate "classical" Home and Journal Views.
==== Summarising ====
Instead of having:
* Activity bundles(.xo in Journal)
* Content bundles(.xol in Journal)
* Activities(from Home View and placed to /usr or ~/Activities)
* Content(in meaning of [[Unified Bundles]])
* Journal Objects(from old Journal View)
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.
== Implementation ==
* [[Features/Object Bundles]]
* [[Features/Activity Objects]]
* [[Features/Unified Browser for Objects]]
* [[Features/Object Collections]]
* [[Features/Peer to Peer Objects Sharing]]
* [[Activities/Library]]
==Pro==
With this scheme accepted user will have unified interface to all
With this scheme accepted user will have unified interface to all
activities.sugarlabs.org(objects.sugarlabs.org? or library.sugarlabs.org?)
activities.sugarlabs.org(objects.sugarlabs.org? or library.sugarlabs.org?)
==Contra==
Well, it couldn't solve multi versions issue for activities out of the box,
Well, it couldn't solve multi versions issue for activities out of the box,
to produce new activity).
to produce new activity).
==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]