Changes

Jump to navigation Jump to search
448 bytes added ,  08:54, 2 April 2009
no edit summary
Line 30: Line 30:  
There are a number of educational applications available on the K Desktop Environment. Sugar, having education in mind, would like to use these applications. The only problem is that these applications  are written for KDE using the Qt toolkit, while Sugar uses the GTK+ toolkit. Therefore for Sugar to have access to these applications they must be rewritten using the GTK+ toolkit.
 
There are a number of educational applications available on the K Desktop Environment. Sugar, having education in mind, would like to use these applications. The only problem is that these applications  are written for KDE using the Qt toolkit, while Sugar uses the GTK+ toolkit. Therefore for Sugar to have access to these applications they must be rewritten using the GTK+ toolkit.
   −
I plan on rewriting an appication using gtkmm instead of GTK+. My reasoning is that gtkmm and Qt are both based on the C++ programming language and should share many of the same development  techniques (object-oriented, etc.). GTK+, on the other hand, is based on the C programming lanuage and techniques (functional, etc.). Using gtkmm should prove to be a smoother transition.
+
Trolltech, the developer of the Qt Toolkit, has included QGtkStyle into Qt 4.5. The QGtkStyle class provides a widget style rendered by GTK+ (http://doc.trolltech.com/4.5/qgtkstyle.html). QGtkStyle will allow programs written in Qt to integrate better into desktop environments that use GTK+. Using QGtkStyle as an alternative to recoding an entire program from Qt to GTK+ will dramatically speed up the process of bringing KDEEdu applications to Sugar.  
   −
One experience that was lacking in my early education was the use of computers to solve math problems. You could always use a word processor to type a report or the internet to find a map for geography but you always needed to solve math problems out my hand. Therefore, I would like to "sugarize" a mathematics application from KDEEdu, probably KAlgebra since it is general purpose and has graphing capabilites. I believe this will help all students, but especially those who may find it hard to visualize some concepts.
+
The only drawback to using QGtkStyle is that the Qt libraries will still be needed to run KDEEdu applications on Sugar. This may pose a problem for hardware with less resources such as the OLPC XO-1. After porting a KDEEdu application to Sugar and finding it stable, I will try to reduce the number of Qt libraries by removing one that are not needed by the application.
 +
 
 +
One experience that was lacking in my early education was the use of computers to solve math problems. You could always use a word processor to type a report or the internet to find a map for geography but you always needed to solve math problems out my hand. Therefore, I would like to "sugarize" a mathematics application from KDEEdu, probably KAlgebra since it is general purpose and has graphing capabilites. I believe this will help all students, but especially those who may find it hard to visualize math concepts.
    
* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.
 
* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.
28

edits

Navigation menu