Being that I think I spent more time than is necessary at this point, I'm shifting just dealing with buttons for the time being. By just working with buttons, I can ignore a lot of the crap flying around inside GTK, and lay a framework for extended functionality. I just feel the need to get something up-and-running that is automated. I keep getting sidetracked by attempting to implement more than is necessary right now (like handling Gtk.Journal's). Need to stay focused.
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.
Monday, May 26, 2008
Being too cautious
I've been dissecting the various layers of the Calculate.activity for the past few hours, trying to find out how little bits of it work, and how to be able to identify different parts of it by label/name/title/whatever, and being able to run a Widget through a method and have it hand me back a useful name (e.g. "9" for a button labelled "9"). However, this is proving to be difficult for some of the non-elementary types (for example, Widgets inside the tabs of a Gtk.Journal; and Gtk.Alignment containers).
Subscribe to:
Post Comments (Atom)
Blog Archive
-
▼
2008
(91)
-
▼
May
(23)
- Automation, GO!
- Simple Button Click
- Health Testing
- Being too cautious
- Scheduling Bloodwork
- Enumerating Widgets
- WOOOOOO
- Which came first, the snake or the egg?
- Migrating to an Activity
- What is our scope?
- Roadblocks
- Workin' It Out
- It's hard to overstate my satisfaction
- More kiwi.ui.test
- kiwi.ui.test
- Dissecting guitest
- GUITAR will have to wait
- Underwhelmed
- Working calculator.py
- Playing with peekaboo
- Contacts and Krstić
- How to Install VMware Tools on Ubuntu Hardy 8.04 u...
- First Post
-
▼
May
(23)
No comments:
Post a Comment