Skip to main content


developerWorks  >  Linux | Open source  >

Application development for the OLPC laptop

Program an activity for the XO-1 using Python

developerWorks

Level: Intermediate

M. Tim Jones (mtj@mtjones.com), Consultant Engineer, Emulex Corp.

18 Dec 2007

Register now or sign in using your IBM ID and password.

The XO laptop (of the One-Laptop-Per-Child initiative) is an inexpensive laptop project intended to help educate children around the world. The laptop includes many innovations, such as a novel, inexpensive, and durable hardware design and the use of GNU/Linux® as the underlying operating system. The XO also includes an application environment written in Python with a human interface called Sugar, accessible to everyone (including kids). Explore the Sugar APIs and learn how to develop and debug a graphical activity in Sugar using Python.

In this tutorial

  • Develop Python activities for the XO laptop
  • Learn about Sugar (the XO user interface, or UI) and the details behind activity development
  • Learn about Python programming, Sugar application program interfaces (APIs) for Python, and platform emulation with QEMU


Objectives

In this tutorial, you learn about the XO laptop and how to write a Python activity using the Sugar UI. Along the way, you learn more about the XO laptop, its architecture, internals, and use.

Prerequisites

More on OLPC

This tutorial is written for Linux developers who want to learn more about the XO laptop and the Sugar UI. It assumes a familiarity with the Linux shell and a basic understanding of the Python language.


System requirements

This tutorial provides a hands-on approach to learning about the XO laptop and Sugar activities. It assumes a Linux computer with at least 1.1GB of free space.



Duration

More than 2 hours


Formats

html, pdf


Learn more

Share this....

digg Digg this story del.icio.us del.icio.us Slashdot Slashdot it!


Back to top


Document options

Document options requiring JavaScript are not displayed

Discuss


My developerWorks needs you!

Connect to your technical community