Python Debugger activity for the XO: Difference between revisions

From OLPC
Jump to navigation Jump to search
Line 1: Line 1:
===Objectives And Strategy===
===Objectives And Strategy===
It would be wonderful to have a python sourcecode debugger for the XO, fully integrated with sugar. But at this point it is difficult to use even Ipython and PDB command line tools within the SUGAR environment. It appears that most activity development is done using emulation and cross machine development.
It would be wonderful to have a python sourcecode debugger for the XO, fully integrated with sugar. But at this point it is difficult to use even Ipython and PDB command line tools within the SUGAR environment. It appears that most Activity development is done using emulation and cross machine development.
The purpose of this Activity is to develop as quickly as possible a minimal set of function which will permit stand alone development of Sugar Activities on the XO.
The purpose of this Activity is to develop as quickly as possible the minimal functionality which will permit stand alone development of Sugar Activities on the XO.
*One way it will try to minimize development time is by combining Activities that are already available on the XO -- such as Write, Browse, and Terminal (with ipython).
*One way it will try to minimize development time is by combining Activities that are already available on the XO -- such as Write, Browse, and Terminal (with ipython).
*Another is to tightly control the addition of "nice to have" features.
*Another is to tightly control the addition of "nice to have" features.
It would be nice if this activity could become a springboard for older students as the explore the world of Python, Gtk, and Sugar Activity development. In the service of this objective, PyDebug should provide simple working examples which can be explored and modified. It should provide a set of offline documentation which is appropriate to using Ipython, Pdb, as tools for developing and debugging Activities.

Revision as of 19:46, 10 October 2009

Objectives And Strategy

It would be wonderful to have a python sourcecode debugger for the XO, fully integrated with sugar. But at this point it is difficult to use even Ipython and PDB command line tools within the SUGAR environment. It appears that most Activity development is done using emulation and cross machine development. The purpose of this Activity is to develop as quickly as possible the minimal functionality which will permit stand alone development of Sugar Activities on the XO.

  • One way it will try to minimize development time is by combining Activities that are already available on the XO -- such as Write, Browse, and Terminal (with ipython).
  • Another is to tightly control the addition of "nice to have" features.

It would be nice if this activity could become a springboard for older students as the explore the world of Python, Gtk, and Sugar Activity development. In the service of this objective, PyDebug should provide simple working examples which can be explored and modified. It should provide a set of offline documentation which is appropriate to using Ipython, Pdb, as tools for developing and debugging Activities.