Features/Server Objects Sharing: Difference between revisions
No edit summary |
mNo edit summary |
||
(25 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude> | <noinclude>{{GoogleTrans-en}}{{TOCright}} | ||
[[Category:Feature Page Incomplete]] | |||
[[Category:Feature|Server Objects Sharing]]</noinclude> | |||
<!-- All fields on this form are required to be accepted. | <!-- All fields on this form are required to be accepted. | ||
Line 8: | Line 10: | ||
== Summary == | == Summary == | ||
Share sugar datastore (Journal) objects on a standalone server. | |||
The main purpose is having one place to share users Journal objects like [http://scratch.mit.edu/] 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 == | == Owner == | ||
* Name: | * Name: | ||
* Email: | * Email: | ||
== Current status == | == Current status == | ||
* Targeted release: 0. | * Targeted release: 0.86 | ||
* Last updated: Thu Jul 9 01:37:37 UTC 2009 | * Last updated: Thu Jul 9 01:37:37 UTC 2009 | ||
* Percentage of completion: 0% | * Percentage of completion: 0% | ||
Line 24: | Line 28: | ||
Let users store sugar objects on standalone server. So, users can share theirs objects for broad audience. | 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) | |||
* Server should return [[Features/Object_Bundles|object bundle]] if web client is Browse and plain Journal entries otherwise (for non-sugar users) | |||
== Benefit to Sugar == | == Benefit to Sugar == | ||
Storing objects on a server, user shouldn't be online all time to share | 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 == | == Scope == | ||
* depends on [[Features/Object Bundles]] | |||
* Choose/adapt web framework | |||
== How To Test == | == How To Test == | ||
# Create a new Turtle Art 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 == | ||
Line 43: | Line 60: | ||
== Dependencies == | == Dependencies == | ||
''In progress..'' | |||
== Contingency Plan == | == Contingency Plan == | ||
Line 51: | Line 68: | ||
== Documentation == | == Documentation == | ||
* [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg06520.html ml thread] | |||
* [http://joshstechjournal.blogspot.com/2009/07/july-23-2009-xo-web-sharing-scratch.html blog post] | |||
== Release Notes == | == Release Notes == | ||
Line 59: | Line 77: | ||
== Comments and Discussion == | == Comments and Discussion == | ||
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page --> | * See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page --> | ||