5,705
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + − (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+ − − + − + − + − + − + − + − + + + + + + + + + + + + + + + + + +
User:Alsroot/trash/Unified Objects (view source)
Revision as of 06:03, 11 April 2009
, 06:03, 11 April 2009→Preamble
<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===
=== 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?
We should encourage people CRS theirs activities as well. Only one but -
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.
current sugar cannot work with many versions installed. At the same time
this multi versioning is cornerstone of CRS activities since we have
This CRS scheme works(more or less at present) for content since we have Journal to store objects, but what about Activities?
(should have) many versions of one particular activity installed on the
same box. And these versions could include "home made" activities not
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.
only "official" ones. User should have possibility to treat all these
versions(of one activity) effectively to CRS them.
===== Journal Objects(in old meaning) is a 1st class Objects as well(in addition to Activities) =====
[[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.
===== Replace Home and Journal Views with more relevant View(s) =====
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.
===== Summarising =====
Instead of having:
* Activity bundles(.xo in Journal or in /usr)
* Content bundles(.xol in Journal)
* Activities(from Home View)
* 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.
===Proposal===
===Proposal===