28
edits
Changes
no edit summary
====About your project====
====About your project====
* What is the name of your project?
KDEEdu
KDEEdu
* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
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.
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.
* 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.
* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.
====You and the community====
====You and the community====