Difference between revisions of "Activities/Library"
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
So, journal objects, activities, activity bundles, content bundles are the same level objects. | So, journal objects, activities, activity bundles, content bundles are the same level objects. | ||
| + | |||
| + | All object versions | ||
| + | * by ''activity_id'' if it exists | ||
| + | * by ''activity'' for activities/bundles | ||
| + | are represented in Library by one collapsed item. | ||
Every Library object could include: | Every Library object could include: | ||
* manually included objects | * manually included objects | ||
| − | * auto included | + | * auto included objects |
| + | ** by MIME type | ||
| + | ** new version of object, if object was already included | ||
* all objects | * all objects | ||
Revision as of 16:14, 4 May 2009
Purposes
Cornerstone ideas:
- implement Unified Objects proposal to have unified method to create, reuse and share all Objects in Sugar
- work with remote Sugar Objects in the same way like with local
- make this activity Sucrose version independent(0.82+)
Objects model
How it looks like from top-level point of view.
Everything is an object
So, journal objects, activities, activity bundles, content bundles are the same level objects.
All object versions
- by activity_id if it exists
- by activity for activities/bundles
are represented in Library by one collapsed item.
Every Library object could include:
- manually included objects
- auto included objects
- by MIME type
- new version of object, if object was already included
- all objects