− | Authors of code are always interested in supporting as large an audience of users as possible. And since people can use Sugar in different environments, it is critical to provide an instrument that permits an activity to run on all Sugar platforms. In the case of Python-based activities, the existing practice of just zipping the activity code into .xo files works pretty well. But for arbitrary scripting languages, such as Ruby, that are not part of the [[0.88/Platform_Components|Sugar Platform]], and for activities that have dependencies that are not included in the Sugar Platform, there is the problem of providing the user with the necessary code. | + | Authors of code are always interested in supporting as large an audience of users as possible. And since people can use Sugar in different environments, it is critical to provide an instrument that permits an activity to run on all Sugar platforms. In the case of Python-based activities, the existing practice of just zipping the activity code into .xo files works pretty well. But for arbitrary scripting languages, such as Ruby, that are not part of the [[0.88/Platform_Components|Sugar Platform]], for binary based activities and for activities that have dependencies that are not included in the Sugar Platform, there is the problem of providing the user with the necessary code. |