Activities/Library

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/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 Journal objects
• auto included Journal objects
  • by MIME type
  • new version of object, if object was already included
• all Journal objects