sugarbot's aim is to provide testing and automation facilities for the OLPC Project's Sugar GUI. The project must first identify and evaluate possible implementation options, and then implement the best choice. Although it has a Sugar focus, sugarbot should be easily extensible to other Python-based GUI's.
Subscribe to:
Post Comments (Atom)
Blog Archive
-
▼
2008
(91)
-
▼
June
(30)
- Issues Testing XML Server
- So wait...
- zomg
- sugar-emulator
- Not cooperating...
- Documentation Effort
- Ubuntu is running
- Drive Genius
- New Wiki Pages
- Refactoring
- Not going well today...
- Now Launching
- Parsing Server-side
- Bug Hunting
- Moving
- That's it, really?
- Timout problem
- XML-RPC
- Temporary Diversion
- Brick Wall
- Reorganizing, issues with a few Widgets
- In Maryland
- Multiple-Initialization
- Re-factoring mood?
- Widget Identifier Refactor
- Getting pretty sugar-specific
- Bandwidth
- Damnit, Python
- Evaluating Entries, basic parsing
- Houston
-
▼
June
(30)
2 comments:
Is there something that Sugar could be doing to make your life easier here?
There are a few Widget subclasses that I've run into (in sugar.graphics, IIRC) that do not have accessor methods to retrieve the label or name that they were assigned. Also, the objects do not use those names/labels to call gtk.Widget.set_name() to set the name of the widget in a globally-retrievable manner.
Post a Comment