GTK for OLPC: Difference between revisions

From OLPC
Jump to navigation Jump to search
Line 2: Line 2:


== GTK theme/engine torturer and crash tester ==
== GTK theme/engine torturer and crash tester ==

[[Image:torture_screenshot.png|left|220px|thumb|Theme torturer tab]]
[[Image:Torture_screenshot2.png|left|220px|thumb|Crash tester tab]]


This "gtk-theme-torturer" is an application to detect performance issues in GTK themes/engines. It does two things:
This "gtk-theme-torturer" is an application to detect performance issues in GTK themes/engines. It does two things:
Line 14: Line 17:


* Plans are to merge this app with Federico Mena Quintero's Widget Profiler in order to get a detailed analysis of the time that was necessary to allocate/map/redraw/etc. widgets.
* Plans are to merge this app with Federico Mena Quintero's Widget Profiler in order to get a detailed analysis of the time that was necessary to allocate/map/redraw/etc. widgets.

Screenshots :

[[Image:torture_screenshot.png|left|220px|thumb|Theme torturer tab]]
[[Image:Torture_screenshot2.png|left|220px|thumb|Crash tester tab]]


== Various enhancements ==
== Various enhancements ==

Revision as of 12:09, 9 July 2006

This is the wiki page for the "GTK+ for OLPC" project, as a "Summer of Code" project. The student is Manu Cornet, mentor is Federico Mena-Quintero. You can find the initial goals of the project on the OLPC Google Summer of Code page.

GTK theme/engine torturer and crash tester

Theme torturer tab
Crash tester tab

This "gtk-theme-torturer" is an application to detect performance issues in GTK themes/engines. It does two things:

  • For each of the most common widget types (very easy to add some more), it packs an instance of it in a container, and resizes/redraws it many, many times. You can set a "pain level" to determine the number of times widgets will get redrawn while scaling.
  • It takes each one of the gtk_paint_* functions (implemented by the engines themselves) and tries all possible parameters configurations, including unusual values to see if the engine crashes.

The current version of gtk-theme-torturer is [here http://www.manucornet.net/pub/olpc/gtk-theme-torturer/] (current tarball in the parent directory). The torturer is fully functionnal and mainly finished. Future enhancements :

  • Currently, the detailed log is sent to stdout. It would be more convenient to let the use choose (GtkFileChooser) a log file.
  • Plans are to merge this app with Federico Mena Quintero's Widget Profiler in order to get a detailed analysis of the time that was necessary to allocate/map/redraw/etc. widgets.

Various enhancements

Cursor blinking

I began with this (probably quite simple to do). The purpose is to let the cursor blink for a few seconds, then just stay on and stop blinking (affects GtkEntry and GtkTextView).

This is done by :

  • Adding an XSetting called "gtk-cursor-blink-lifetime", which defaults to 5 seconds.
  • Adding a timeout with the corresponding lifetime each time the code asks the cursor to begin blinking. When the timeout is over, the cursor stays on.

A (nearly final) version of the patch (both for GtkEntry and GtkTreeView) is available [here http://www.manucornet.net/pub/olpc/enhancements/cursor_blink_lifetime.diff].

Simulation Tools

Right now : making tests with "Xephyr" to simulate the laptop's display.

GTK+ theme engine

Right now: learning how to write a GTK engine/theme. I'll probably begin by searching whether there's an existing theme close to what we want, and I can start from there. It seems that some people at RedHat are already working on a special theme for OLPC, I'll need to coordinate with them as soon as the "torturer" part is finished.