Activities: Difference between revisions
m →Midnight Commander: Space |
No edit summary |
||
| Line 1: | Line 1: | ||
<noinclude>{{ GoogleTrans-en | <noinclude>{{GoogleTrans-en}}</noinclude>{{Translations}}{{TOCright}}</noinclude> | ||
{{TOCright}} | |||
== Users == | == Users == | ||
Sugar user applications are called '''[[ | Sugar user applications are called '''[[Human Interface Guidelines/Activities | Activities]]'''. They are software packages that automatically save your work producing instances of the Activity that can be resumed at a later time. An Activity instance is a [[Human_Interface_Guidelines/The_Laptop_Experience/The_Journal| Journal]] event. Many Activities support user [[Collaboration|collaboration]] where multiple users may be invited to join a collective Activity session. | ||
Please see the [http://activities.sugarlabs.org Activity Library] for a complete list of activities which are available for Sugar. | Please see the [http://activities.sugarlabs.org Sugar Activity Library] for a nearly complete list of activities which are available for Sugar. | ||
== Developers == | == Developers == | ||
Please see the [[Activity Team]] for developer information. | Please see the [[Activity Team]] for developer information. | ||
| Line 19: | Line 18: | ||
==== Sugar Coating Activities ==== | ==== Sugar Coating Activities ==== | ||
To run Linux apps under Sugar (i.e. making them to run in the Sugar interface, without the collaboration and other Sugar integration programmed into them), read these instructions on [[Running Linux Applications Under Sugar]]. | To run Linux apps under Sugar (''i.e.'', making them to run in the Sugar interface, without the collaboration and other Sugar integration programmed into them), read these instructions on [[Running Linux Applications Under Sugar]]. | ||
In the future, we hope that Sugar will be able to run Linux applications natively without these steps. | In the future, we hope that Sugar will be able to run Linux applications natively without these steps. | ||