Difference between revisions of "Features/Server Objects Sharing"
< Features
Jump to navigation
Jump to search
(→Scope) |
(→Scope) |
||
Line 38: | Line 38: | ||
** fix issues related to name mangling of Journal objects after uploading/downloading | ** fix issues related to name mangling of Journal objects after uploading/downloading | ||
** keep objects DS metadata while transfering between user-server-user | ** keep objects DS metadata while transfering between user-server-user | ||
− | ** after user-server-user session object on target box should be treated in the same way like object on source box | + | ** 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 | * Choosing/coding web engine | ||
Revision as of 23:38, 16 July 2009
Summary
Share objects on standalone server.
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
- 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
Release Notes
In progress