Difference between revisions of "Features/Peer to Peer Objects Sharing"
< Features
Jump to navigation
Jump to search
m |
|||
| (16 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | <noinclude>{{ GoogleTrans-en | + | <noinclude>{{GoogleTrans-en}}{{TOCright}} |
| + | [[Category:Feature Page Incomplete]] | ||
| + | [[Category:Feature|Peer to Peer Objects Sharing]]</noinclude> | ||
<!-- All fields on this form are required to be accepted. | <!-- All fields on this form are required to be accepted. | ||
| Line 12: | Line 14: | ||
== Owner == | == Owner == | ||
| − | * Name: | + | * Name: |
| − | * Email: | + | * Email: |
== Current status == | == Current status == | ||
| − | * Targeted release: 0. | + | * Targeted release: 0.88 |
* Last updated: Thu Jul 9 01:18:29 UTC 2009 | * Last updated: Thu Jul 9 01:18:29 UTC 2009 | ||
* Percentage of completion: 0% | * Percentage of completion: 0% | ||
| Line 22: | Line 24: | ||
== Detailed Description == | == Detailed Description == | ||
| − | Let users share | + | Let users share their Journal objects with other users. The key difference from the "Send to" feature is that target users can browse shared objects without downloading them. |
| + | |||
| + | There could be several designs: | ||
| + | |||
| + | * One set of shared objects<br>User can mark any object in Journal as a "shared" object, so other users can choose "Browse shared objects" option from buddy context menu in Neighborhood view and browse/download all shared objects (how, in what window?) | ||
| + | |||
| + | * Collections<br>A superset of first option - collections of objects. In fact it relates to [[Activities/Library]]. User creates a collection of objects(they are "stored" in some way in Library object), later user shares this object, opening this object by other user means opening shared Library object (with list of shared objects). | ||
| + | |||
| + | Having collections makes sense in "local" mode as well - user can have several collections for local purposes, e.g., "My favorite books", etc. see [[Features/Object Collections]]. | ||
== Benefit to Sugar == | == Benefit to Sugar == | ||
| Line 30: | Line 40: | ||
== Scope == | == Scope == | ||
| − | It affects Journal code in | + | It affects Journal code in Sugar package, adds new activity for <0.86 releases. |
== How To Test == | == How To Test == | ||
| Line 37: | Line 47: | ||
== User Experience == | == User Experience == | ||
| − | '' | + | |
| + | ''In progress'' | ||
== Dependencies == | == Dependencies == | ||
| − | For >=0.86, all functionality will come from | + | For >=0.86, all functionality will come from Sugar package, for <0.86 it will be packaged in an activity. |
== Contingency Plan == | == Contingency Plan == | ||
| − | + | ||
| + | None necessary, revert to previous release behaviour. | ||
== Documentation == | == Documentation == | ||
| − | + | ||
| + | None other than this page. | ||
== Release Notes == | == Release Notes == | ||
| − | '' | + | |
| + | ''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 --> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 01:18, 18 October 2009
Summary
Share sugar objects in Peer-to-Peer manner.
Owner
- Name:
- Email:
Current status
- Targeted release: 0.88
- Last updated: Thu Jul 9 01:18:29 UTC 2009
- Percentage of completion: 0%
Detailed Description
Let users share their Journal objects with other users. The key difference from the "Send to" feature is that target users can browse shared objects without downloading them.
There could be several designs:
- One set of shared objects
User can mark any object in Journal as a "shared" object, so other users can choose "Browse shared objects" option from buddy context menu in Neighborhood view and browse/download all shared objects (how, in what window?)
- Collections
A superset of first option - collections of objects. In fact it relates to Activities/Library. User creates a collection of objects(they are "stored" in some way in Library object), later user shares this object, opening this object by other user means opening shared Library object (with list of shared objects).
Having collections makes sense in "local" mode as well - user can have several collections for local purposes, e.g., "My favorite books", etc. see Features/Object Collections.
Benefit to Sugar
Make changing of objects between users more friendly.
Scope
It affects Journal code in Sugar package, adds new activity for <0.86 releases.
How To Test
In progress..
User Experience
In progress
Dependencies
For >=0.86, all functionality will come from Sugar package, for <0.86 it will be packaged in an activity.
Contingency Plan
None necessary, revert to previous release behaviour.
Documentation
None other than this page.
Release Notes
In progress..