8,288
edits
Changes
Jump to navigation
Jump to search
Line 58:
Line 58: − + Line 92:
Line 92: − + Line 103:
Line 103: + + + + + + + + + − + + + Line 113:
Line 124: + + + +
Google Code In 2018/background (view source)
Revision as of 19:24, 1 December 2018
, 19:24, 1 December 2018→Setting up a Sugar desktop environment: update SoaS sugar version
|-
|-
! Sugar desktop user experience on startup
! Sugar desktop user experience on startup
| yes, 0.112 || yes, 0.110 || no, must install packages
| yes, 0.112 || yes, 0.112 || no, must install packages
|-
|-
! Good for Sugar activity development
! Good for Sugar activity development
* For both, you will need knowledge of Sugar activity development, see the book [http://www.flossmanuals.net/make-your-own-sugar-activities/ Make Your Own Sugar Activities!]
* For both, you will need knowledge of Sugar activity development, see the book [http://www.flossmanuals.net/make-your-own-sugar-activities/ Make Your Own Sugar Activities!]
Python programmers, you must run [http://legacy.python.org/dev/peps/pep-0008/#introduction pep8] and pyflakes on your code ''before'' submitting your patches.
Python programmers, you should run [http://legacy.python.org/dev/peps/pep-0008/#introduction pep8] and flake8 on your changes ''before'' submitting your patches.
=== Getting started with GIT ===
=== Getting started with GIT ===
Our old bug tracker is https://bugs.sugarlabs.org, but these days, we mostly report bugs using the ''issues'' feature of GitHub. (See https://guides.github.com/features/issues/ for details on GitHub Issues.)
Our old bug tracker is https://bugs.sugarlabs.org, but these days, we mostly report bugs using the ''issues'' feature of GitHub. (See https://guides.github.com/features/issues/ for details on GitHub Issues.)
=== Making a Pull Request ===
We detail the Pull Request process in [https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md here] in our [https://github.com/sugarlabs/sugar-docs docs] on Git Hub.
A few things to keep in mind:
* Do not link commits or pull requests to a GCI task, as these are transient and not public,
* Link commits and pull requests to any relevant GitHub issue, and if there is no such issue, say so,
* Explain the problem and how it was solved in your commit message, not in your pull request.
=== Setting up a Sugarizer environment ===
=== Setting up a Sugarizer environment ===
Use your computer. See also [[#Getting started with Sugarizer]].=== Getting started with Sugarizer ===
Use your computer. See also [[#Getting started with Sugarizer]].
=== Getting started with Sugarizer ===
Sugar Web Framework is the [https://github.com/sugarlabs/sugar-docs/blob/master/web-architecture.md JavaScript Framework for Sugar]. [http://sugarizer.org Sugarizer] is a subset of Sugar that allow running activities developed with Sugar Web Framework on any web browser. Sugarizer is also available as Android, iOS, Firefox OS and Chrome Web App.
Sugar Web Framework is the [https://github.com/sugarlabs/sugar-docs/blob/master/web-architecture.md JavaScript Framework for Sugar]. [http://sugarizer.org Sugarizer] is a subset of Sugar that allow running activities developed with Sugar Web Framework on any web browser. Sugarizer is also available as Android, iOS, Firefox OS and Chrome Web App.
Some tasks require that you make edits to this wiki for which you'll need an account. Please email walter @ sugarlabs . org to request an account.
Some tasks require that you make edits to this wiki for which you'll need an account. Please email walter @ sugarlabs . org to request an account.
=== Editing SVG ===
Some tasks will require that you edit SVG. You are welcome to use any SVG editor you like, but we recommend [https://inkscape.org/en/ Inkscape]. That said, when saving from Inkscape, please be sure to "save as plain SVG." The default "save" puts extra data into the files which is not needed by Sugar and makes the file size quite large.
=== Getting help ===
=== Getting help ===