Difference between revisions of "Features/Server Objects Sharing"
< Features
Jump to navigation
Jump to search
(→Scope) |
|||
Line 41: | Line 41: | ||
== How To Test == | == 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 == | == User Experience == |
Revision as of 21:30, 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
- Journal code in sugar package
- at least fix issues related to name mangling of Journal objects while uploading/downloading/running-in-sugar.
- 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