Platform Team/Package Management System: Difference between revisions

Line 20:

=== Doers ===

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 (~~but only with Python,  since Python is~~ a part of the [[0.88/Platform_Components|Sugar Platform]]), the existing practice of just zipping the activity code into .xo files works pretty well. But it is a problem with non-Python activities or activities that have dependencies that are not included in the Sugar Platform.

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 (not for arbitrary scripting language e.g. Ruby is not a part of the [[0.88/Platform_Components|Sugar Platform]]), the existing practice of just zipping the activity code into .xo files works pretty well. But it is a problem with non-Python activities or activities that have dependencies that are not included in the Sugar Platform.

Zero Sugar tries to solve all the possible issues that prevent activity launching in an heterogeneous Sugar environment.

@@ Line 20: / Line 20: @@
 === Doers ===
-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 (but only with Python, <!-- not even arbitrary scripting language ? meaning not even Bash for example? --> since Python is a part of the [[0.88/Platform_Components|Sugar Platform]]), the existing practice of just zipping the activity code into .xo files works pretty well. But it is a problem with non-Python activities or activities that have dependencies that are not included in the Sugar Platform.
+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 (not for arbitrary scripting language e.g. Ruby is not a part of the [[0.88/Platform_Components|Sugar Platform]]), the existing practice of just zipping the activity code into .xo files works pretty well. But it is a problem with non-Python activities or activities that have dependencies that are not included in the Sugar Platform.
 Zero Sugar tries to solve all the possible issues that prevent activity launching in an heterogeneous Sugar environment.