Features/Launch Limits: Difference between revisions
No edit summary |
|||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<noinclude> | <noinclude> | ||
[[Category: | [[Category:FeatureLanded|Launch Limits]] | ||
[[Category:Features requested by OLPC AU]]</noinclude> | [[Category:Features requested by OLPC AU]]</noinclude> | ||
| Line 23: | Line 22: | ||
See [https://github.com/walterbender/sugar/commit/3fea62baf20a30e11015a014aeb94a16fba58554] and [https://github.com/walterbender/sugar-toolkit-gtk3/commit/1d550b33e9c083140e453cc19389d7966e888a14] | See [https://github.com/walterbender/sugar/commit/3fea62baf20a30e11015a014aeb94a16fba58554] and [https://github.com/walterbender/sugar-toolkit-gtk3/commit/1d550b33e9c083140e453cc19389d7966e888a14] | ||
== Detailed Description == | == Detailed Description == | ||
| Line 42: | Line 37: | ||
is open (e.g., SL #4554). This patch sets a limit on the number open | is open (e.g., SL #4554). This patch sets a limit on the number open | ||
instances of an activity based on a new field in activity.info: | instances of an activity based on a new field in activity.info: | ||
single_instance. | |||
If and only if the | If and only if the single_instance field is present in | ||
activity.info, is it used to set the limit of open instances. | activity.info, is it used to set the limit of open instances. | ||
single_instance = yes | |||
== Benefit to Sugar == | == Benefit to Sugar == | ||
| Line 59: | Line 56: | ||
Also impacts the activity.info file of any activity that wishes to set a limit to the number of open instances: | Also impacts the activity.info file of any activity that wishes to set a limit to the number of open instances: | ||
single_instance = yes | |||
== How To Test == | == How To Test == | ||
Maximum instances: | Maximum instances: | ||
# Add a | # Add a single_instance = yes field to the activity.info file of an activity | ||
# Launch repeatedly and see if a limit is set | # Launch repeatedly and see if a limit is set | ||
Maximum launches: | Maximum launches: | ||
# From terminal gconftool-2 -t int -s /desktop/sugar/maximum_number_of_open_activities 4 | # From terminal gconftool-2 -t int -s /desktop/sugar/maximum_number_of_open_activities 4 | ||
# reboot | |||
# See if more than 4 activities can be launched | # See if more than 4 activities can be launched | ||
# From terminal gconftool-2 -u /desktop/sugar/maximum_number_of_open_activities | # From terminal gconftool-2 -u /desktop/sugar/maximum_number_of_open_activities | ||
# reboot | |||
# See if there is any limit to the number of activities that can be launched | # See if there is any limit to the number of activities that can be launched | ||
===Notes on using Gconf=== | |||
The previous "how to test" section assumes familiarity with Gconf. Gconf is the Gnome preferences configuration system. It is being used to store Sugar preferences in this case. You can start the tool from the command line in Terminal. The -2 in gconftool-2 means that you are using version 2 of Gconf. Typical switches are | |||
-s set a value | |||
-u unset a value | |||
-g get (print) a value | |||
-t set the type (eg int) of a value | |||
== User Experience == | == User Experience == | ||
| Line 93: | Line 99: | ||
The new (optional) field in the activity.info file is: | The new (optional) field in the activity.info file is: | ||
single_instance | |||
== Release Notes == | == Release Notes == | ||
== Comments and Discussion == | == Comments and Discussion == | ||
* http://lists.sugarlabs.org/archive/sugar-devel/2013-November/045585.html | |||
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] | * See [[{{TALKPAGENAME}}|discussion tab for this feature]] | ||
---- | ---- | ||