Difference between revisions of "Features/Server Objects Sharing"

From Sugar Labs
Jump to navigation Jump to search
m
 
(33 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{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 objects on standalone server.
+
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: [[User:alsroot| Aleksey Lim]]
+
* Name:  
* Email: [[Special:Emailuser/alsroot|send an email]]
+
* Email:
  
 
== Current status ==
 
== Current status ==
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 them for other users. Users cat treat server as a standalone additional storage.
+
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 ==
  
It affects Journal code in sugar package, adds new activity for <0.86 releases, codding server side(for example hacking AMO).
+
* depends on [[Features/Object Bundles]]
 +
* Choose/adapt web framework
  
 
== How To Test ==
 
== How To Test ==
  
''In progress..'
+
# 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 ==
  
For >=0.86, all functionality will come from sugar package, for <0.86 it will be packaged in activity.
+
''In progress..''
  
 
== Contingency Plan ==
 
== Contingency Plan ==
  
Don't know yet, but I'm sure I'll do something terRrible.
+
None necessary, revert to previous release behaviour.
  
 
== Documentation ==
 
== Documentation ==
  
Nothing to plan, it will ruin all my life.
+
* [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 ==
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the release team and shipped with the release.''
+
 
 +
''In progress''
  
 
== 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 -->
 
==[[Features]] Subpages==
 
{{Special:PrefixIndex/Features/}}
 
 
[[Category:FeaturePageIncomplete]]
 
[[Category:Feature]]
 
[[Category:Feature for 0.86 Journal]]
 

Latest revision as of 02:26, 18 October 2009


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)
  • Server should return object bundle if web client is Browse and plain Journal entries otherwise (for non-sugar users)

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

How To Test

  1. Create a new Turtle Art activity
  2. Upload the new entry to the SL wiki using Browse
  3. Use Browse to download the entry back to Journal
  4. 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

Comments and Discussion