studio/static/doc/myosa/ch023_where-to-go-from-here.xhtml


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
    "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><body><h1>Where To Go From Here?
</h1>
<p>This book attempts to give a beginning programmer the information she needs to develop and publish her own Sugar Activities.&#160; It already contains many URL's of websites containing information not covered in the book.&#160; This chapter will contain URL's and pointers to still more resources that will be useful to any Sugar developer.
</p>
<h2>PyGTK Book by Peter Gill
  <br/></h2>
<p>Much of the work you will do writing Activities involves PyGTK.&#160; Peter Gill is working on a PyGTK book that covers the subject in great detail.&#160; You can download the book here:
</p>
<p><a href="http://www.majorsilence.com/PyGTK_Book">http://www.majorsilence.com/PyGTK_Book</a>&#160;
  <br/></p>
<h2>OLPC Austria Activity Handbook
</h2>
<p>This is the first attempt to write a manual on creating Sugar Activities.&#160; It is aimed at experienced programmers and covers topics that this book does not, like how to write Activities using languages other than Python.&#160; The book was written in 2008 and as a result some of the advice is a bit dated.&#160; It's still an excellent source of information.&#160; The authors are Christoph Derndorfer and Daniel Jahre.
</p>
<p><a href="http://wiki.sugarlabs.org/images/5/51/Activity_Handbook_200805_online.pdf">http://wiki.sugarlabs.org/images/5/51/Activity_Handbook_200805_online.pdf</a>
  <br/></p>
<p><a href="http://www.olpcaustria.org">http://www.olpcaustria.org</a>
  <br/></p>
<h2>The Sugar Almanac
</h2>
<p>This is a series of Wiki articles covering the Sugar <strong>API</strong> (<strong>Application Programming Interface</strong>).&#160; It's a good source of information that I have referred to many times.
</p>
<p> <a href="http://wiki.sugarlabs.org/go/Development_Team/Almanac">http://wiki.sugarlabs.org/go/Development_Team/Almanac</a>&#160;
</p>
<div class="objavi-forcebreak">
</div>
<h2> Sugar Labs Mailing Lists
</h2>
<p>Sugar Labs has several email mailing lists that might be worth subscribing to.&#160; The ones I follow most are the <strong>IAEP</strong> (<strong>It's An Education Proiject</strong>) list and <strong>Sugar-Devel</strong>.&#160; Sugar-Devel is a good place to ask questions about developing Sugar Activities and learn about the latest work being done on Sugar itself.&#160; IAEP is a good place to get ideas on what kinds of Activities teachers and students want and to get feedback on your own Activities.&#160; Anyone can sign up to these mailing lists here:
</p>
<p><a href="http://lists.sugarlabs.org">http://lists.sugarlabs.org/</a>&#160;
</p>
<h2>PyDoc
</h2>
<p><strong>PyDoc</strong> is a utility for viewing documentation generated from the Python libraries on your computer, including the Sugar libraries.&#160; To run it use this command from a terminal:
</p>
<pre>pydoc -p <em>1234</em></pre>
<p>This command will not finish.&#160; It runs a kind of web server on your system where <em>1234</em> is a port number.&#160; You can access the website it serves at <strong>http://localhost:1234</strong>.&#160; There is nothing magic about the number 1234.&#160; You can use any number you like.
</p>
<p>The website lets you follow links to documentation on all the Python libraries you have installed.&#160; When you are done browsing the documentation you can stop the pydoc command bt returning to the terminal and hitting Ctrl-C (hold down the Ctrl key and hit the "c" key).
</p>
<p>
  <br/></p></body></html>