Features/Server Objects Sharing

Summary

Share sugar datastore(Journal) objects on a standalone server.

The main purpose is having one place to share users Journal objects like [1] does for Scratch community (that doesn't exclude possibility of having storages for local community needs) i.e. having something similar to Activity Library but for Journal objects.

Owner

Name:
Email:

Current status

Targeted release: 0.86
Last updated: Thu Jul 9 01:37:37 UTC 2009
Percentage of completion: 0%

Detailed Description

Let users store sugar objects on standalone server. So, users can share theirs objects for broad audience.

The idea is keeping this feature as simple as possible from Shell point of view.

Utilize Browse for browsing/download/upload(?)
Minimal changes in Shell or even nothing(use Browse in all cases)

Benefit to Sugar

Storing objects on a server, user shouldn't be online all time to share objects for other users. Users can treat server as a standalone additional storage as well.

Scope

Shell code
- Fix issues related to name mangling of Journal objects after uploading/downloading
- Keep objects DS metadata while transfering between user-server-user
  - we can package DS object to bundles (it relates to Unified Bundles)
- After user-server-user session, object on target box should be treated in the same way like object on source box
Choosing/coding web engine

How To Test

Create a new TurtleArt activity
Upload the new entry to the SL wiki using Browse
Use Browse to download the entry back to Journal
Resume it from Journal

This should ideally work for all Activities, then folks can actually start creating and distributing content/activities directly using Sugar, for other Sugar users.

User Experience

In progress

Dependencies

In progress..

Contingency Plan

None necessary, revert to previous release behaviour.

Documentation

ml thread

Release Notes