Activities: Difference between revisions
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
Sugar user applications are called '''[[DesignTeam/Human Interface Guidelines/Activities | Activities]]'''. They are software packages that when run in Sugar will automatically save your work producing instances of the Activity in the Journal that can be resumed at a later time. The Activity instance becomes a Journal event. | Sugar user applications are called '''[[DesignTeam/Human Interface Guidelines/Activities | Activities]]'''. They are software packages that when run in Sugar will automatically save your work producing instances of the Activity in the Journal that can be resumed at a later time. The Activity instance becomes a Journal event. | ||
Please see the [http://activities.sugarlabs.org | Please see the [http://activities.sugarlabs.org Activity Library] for a 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 11: | Line 11: | ||
{{Special:PrefixIndex/{{PAGENAME}}/}} | {{Special:PrefixIndex/{{PAGENAME}}/}} | ||
=== Running Linux Applications Under Sugar | === Running Linux Applications Under Sugar === | ||
There are two ways to run Linux applications as Activities under Sugar (meaning you don't need to use Terminal to load them): | There are two ways to run Linux applications as Activities under Sugar (meaning you don't need to use Terminal to load them): | ||