Sugar Network/API: Difference between revisions

Line 201:

=== Offline activities ===

To get access to {{Code|/}} mountpoint activities even if there is no server connection, activities need to be accessible from {{Code|~}} mountpoint. There are special ''Context'' properties, on all mountpoints, that ~~control what~~ activities ~~exist on {{Code|~}} mountpoint~~:

To get access to {{Code|/}} mountpoint activities even if there is no server connection, activities need to be accessible from {{Code|~}} mountpoint. There are special ''Context'' properties (on all mountpoints) that relate only to offline activities:

* {{Code|keep}}<br>Bookmarked context which metadata is accessible from {{Code|~}} mountpoint;

* {{Code|keep_impl}}<br>Most recent version of the corresponding ''Context'' is accessible from {{Code|~}} mountpoint being placed to {{Code|~/Activities}} directory.

* {{Code|keep_impl}}<br>Most recent version of the corresponding ''Context'' is accessible from {{Code|~}} mountpoint being placed to {{Code|~/Activities}} directory;

* {{Code|position}}<br>A tuple of integer values with X and Y coordinates of activity icon position in Sugar Shell's Home view.

~~Both~~ properties are writable, so, it is possible to set {{Code|keep_impl}} property to {{Code|True}} for a ''Context'' on {{Code|/}} mountpoint to make sure that after going offline, this ''Context'' will remain runnable. The same true for clearing {{Code|keep_impl}} as well.

All properties are writable, so, it is possible to set {{Code|keep_impl}} property to {{Code|True}} for a ''Context'' on {{Code|/}} mountpoint to make sure that after going offline, this ''Context'' will remain runnable. The same true for clearing {{Code|keep_impl}} as well.

=== Launch activities ===

@@ Line 201: / Line 201: @@
 === Offline activities ===
-To get access to {{Code|/}} mountpoint activities even if there is no server connection, activities need to be accessible from {{Code|~}} mountpoint. There are special ''Context'' properties, on all mountpoints, that control what activities exist on {{Code|~}} mountpoint:
+To get access to {{Code|/}} mountpoint activities even if there is no server connection, activities need to be accessible from {{Code|~}} mountpoint. There are special ''Context'' properties (on all mountpoints) that relate only to offline activities:
 * {{Code|keep}}<br>Bookmarked context which metadata is accessible from {{Code|~}} mountpoint;
-* {{Code|keep_impl}}<br>Most recent version of the corresponding ''Context'' is accessible from {{Code|~}} mountpoint being placed to {{Code|~/Activities}} directory.
+* {{Code|keep_impl}}<br>Most recent version of the corresponding ''Context'' is accessible from {{Code|~}} mountpoint being placed to {{Code|~/Activities}} directory;
+* {{Code|position}}<br>A tuple of integer values with X and Y coordinates of activity icon position in Sugar Shell's Home view.
-Both properties are writable, so, it is possible to set {{Code|keep_impl}} property to {{Code|True}} for a ''Context'' on {{Code|/}} mountpoint to make sure that after going offline, this ''Context'' will remain runnable. The same true for clearing {{Code|keep_impl}} as well.
+All properties are writable, so, it is possible to set {{Code|keep_impl}} property to {{Code|True}} for a ''Context'' on {{Code|/}} mountpoint to make sure that after going offline, this ''Context'' will remain runnable. The same true for clearing {{Code|keep_impl}} as well.
 === Launch activities ===