1,285
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + Line 7:
Line 7: − + − + − If you use Linux, your best bet is to install [[Development Team/Jhbuild|sugar-jhbuild]]. You will be able to develop in your native environment, treating Sugar as just another desktop application. − If you run MacOS X or Windows, you will need to set up an emulator. For setup instructions and links to pre-configured virtual machines, see [[VirtualBox]].+ − To develop efficiently using an emulator or a secondary machine (such as an OLPC XO), find an editor which supports editing files over a SFTP connection. [http://www.openkomodo.com/ Komodo Edit] with the Remote Drive Tree extension is a good example.+ + − + + + Line 57:
Line 59: − + Line 98:
Line 100: − + + Line 108:
Line 111: − + + + Line 132:
Line 137: + +
Activity Team/Resources (view source)
Revision as of 22:18, 16 January 2018
, 22:18, 16 January 2018→Sugar Activities
<noinclude>{{GoogleTrans-en}}{{TeamHeader|Activity Team}}</noinclude>{{TOCright}}
<noinclude>{{TeamHeader|Activity Team}}</noinclude>
==Getting started in Activity development==
==Getting started in Activity development==
{|
{|
|-
|-
|[[File:Sugarlabs_mainpage_07.png|link=http://en.flossmanuals.net/ActivitiesGuideSugar]]
|<span class="plainlinks">[[File:Sugarlabs_mainpage_07.png|link=http://en.flossmanuals.net/make-your-own-sugar-activities]]</span>
|valign="center"|The official introduction to writing Sugar activities is the Flossmanuals book [http://en.flossmanuals.net/ActivitiesGuideSugar Writing Sugar Activities], by James Simmons.
|valign="center"|The official introduction to writing Sugar activities is the Flossmanuals book [http://en.flossmanuals.net/make-your-own-sugar-activities/ Make Your Own Sugar Activities!] by James Simmons.
|}
|}
====Setting up a Sugar environment====
====Setting up a Sugar environment====
Please see [[Downloads | Get Sugar]] for details on how to best get Sugar running.
If you decide to use a Virtual Machine (VM) or a secondary machine (such as an OLPC XO) for testing your activities, an editor with support for editing files over an SSH or SFTP connection can come in handy. [http://www.activestate.com/komodo-edit/downloads Komodo Edit] with the Remote Drive Tree extension, emacs with tramp and magit, and [http://www.eclipse.org Eclipse] with the [http://www.jcraft.com/eclipse-sftp/ SFTP Plugin] are examples.
====Python Reference & Tutorials====
====Python Reference & Tutorials====
* [http://greenteapress.com/thinkpython/thinkpython.html Think Python: How to Think Like a Computer Scientist]
* http://docs.python.org/
* http://docs.python.org/
* http://diveintopython.org/
* http://diveintopython.org/
* [http://pleac.sourceforge.net/pleac_python/index.html PLEAC - Programming Language Examples Alike Cookbook]
* [http://pleac.sourceforge.net/pleac_python/index.html PLEAC - Programming Language Examples Alike Cookbook]
* http://code.google.com/edu/languages/google-python-class/
* http://code.google.com/edu/languages/google-python-class/
* [http://people.csail.mit.edu/pgbovine/python/ Online Python Tutor] - Online stepping & visualization of Python code
* [http://ocw.mit.edu/courses/electrical-engineering-and-computer-science/6-00sc-introduction-to-computer-science-and-programming-spring-2011/ 6.00SC Introduction to Computer Science and Programming]
*http://www.babarehner.com/ewrench1011/Python/index.html
Python is the language Sugar is written in and is also used by most activities. If you don't already know Python well, you should familiarize yourself with it before continuing.
Python is the language Sugar is written in and is also used by most activities. If you don't already know Python well, you should familiarize yourself with it before continuing.
The Sugar Almanac contains all the information you need to start writing Sugar activities, ranging from directory structure to bundle format to API reference. It also contains answers to common questions and examples of common tasks.
The Sugar Almanac contains all the information you need to start writing Sugar activities, ranging from directory structure to bundle format to API reference. It also contains answers to common questions and examples of common tasks.
* http://api.sugarlabs.org/
* https://developer.sugarlabs.org/sugar3
This automatically updated site contains the official API documentation for Sugar. Though it is currently quite sparse, the source code is included with the documentation and it's useful to have that at your fingertips.
This automatically updated site contains the official API documentation for Sugar. Though it is currently quite sparse, the source code is included with the documentation and it's useful to have that at your fingertips.
====Git introduction====
====Git introduction====
Git is the version control software used by Sugar Labs. It is a distributed version control system and is quite powerful, but requires a lot of command line use.
Git is the version control software used by Sugar Labs. It is a distributed version control system and is quite powerful, but may require a lot of command line use.
* [[Activity Team/Git|Git]]
* [[Activity Team/Git|Git]]
* [https://github.com/ GitHub]
====XML routines====
====XML routines====
====Speech synthesizing====
====Speech synthesizing====
If you want to add a speech synthesizer for English and other languages, try the [[Activity_Team/gst-plugins-espeak|gst-plugins-espeak]] plugin for gstreamer.
If you want to add a speech synthesizer for English and other languages, use the sugar3.speech module, or try the [[Activity_Team/gst-plugins-espeak|gst-plugins-espeak]] plugin for gstreamer.
==Activity Development Resources==
==Activity Development Resources==
This is an open area for posting links related to activity development.
This is an open area for posting links related to activity development.
===Hosting===
https://github.com/sugarlabs may host your Sugar related code.
===Sample code===
===Sample code===
profiler.disable()
profiler.disable()
profiler.dump_stats('/tmp/profile')
profiler.dump_stats('/tmp/profile')
Use kcachegrind to view the results.
===References===
===References===