Python Debugger activity for the XO: Difference between revisions
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. |
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. |
|||
*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. |
|||
Revision as of 19:35, 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 a minimal set of function 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.