Difference between revisions of "Sugar Network/Resources"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
|} | |} | ||
| − | '''Resource. | + | '''Resource.layers''' |
: This is an attempt to generalize the idea of [http://groups.google.com/group/sugar-network/browse_thread/thread/4cad05ec801f364c user/resource levels] with idea that objects should not be removed from the Network immediately (only hidden, and permanently removed by Network administrators). So, every resource is associated with a layer, i.e., it might be visible for observers only if they requested this layer and have permissions to see it. | : This is an attempt to generalize the idea of [http://groups.google.com/group/sugar-network/browse_thread/thread/4cad05ec801f364c user/resource levels] with idea that objects should not be removed from the Network immediately (only hidden, and permanently removed by Network administrators). So, every resource is associated with a layer, i.e., it might be visible for observers only if they requested this layer and have permissions to see it. | ||
| Line 12: | Line 12: | ||
: For now, implemented only the following list of layers, but it might be reused for [http://groups.google.com/group/sugar-network/msg/f5a1b4d78494a5d3 teachers related workflows] later: | : For now, implemented only the following list of layers, but it might be reused for [http://groups.google.com/group/sugar-network/msg/f5a1b4d78494a5d3 teachers related workflows] later: | ||
| − | |||
:* ''deleted'' Network objects' layer will be changed to {{Code|deleted}} after removing objects by users. | :* ''deleted'' Network objects' layer will be changed to {{Code|deleted}} after removing objects by users. | ||
Revision as of 02:26, 19 March 2012
The following diagram shows the full list of objects implemented by the Sugar Network API.
Resource.layers
- This is an attempt to generalize the idea of user/resource levels with idea that objects should not be removed from the Network immediately (only hidden, and permanently removed by Network administrators). So, every resource is associated with a layer, i.e., it might be visible for observers only if they requested this layer and have permissions to see it.
- For now, implemented only the following list of layers, but it might be reused for teachers related workflows later:
- deleted Network objects' layer will be changed to
deletedafter removing objects by users.
- deleted Network objects' layer will be changed to
Context.type
- Context types:
- application, software application;
- library, software library;
- activity, Sugar activity;
- article, arbitrary content in a form of article.
Implementation.license
- Short license names. The licenses should conform with the Activity Library licensing policy.
Implementation.stability
- Stability level of the Implementation. Values conform to 0install stability levels and could be:
- insecure,
- buggy,
- developer,
- testing,
- stable.
Artifact.type
- The type of the Artifact:
- screenshot, screenshot generated within the Context;
- jobject, Journal object generated by Sugar activity.
Notification.type
- create, object was created;
- update, object's properties were modified;
- delete, object was deleted (hidden);
- vote, object was voted/unvoted.