Projects/Edu/KidsPlay - Revision history

Annma: /* Application we need: */

2010-05-01T14:03:02Z

‎Application we need:

Annma: /* Application we need: */

2010-05-01T13:50:06Z

‎Application we need:

Annma: /* The implementation */

2010-05-01T13:47:27Z

‎The implementation

Annma: /* The interface */

2010-05-01T13:44:05Z

‎The interface

Annma: /* The core */

2010-05-01T13:17:25Z

‎The core

Annma: /* The goal of the project */ typos

2010-05-01T13:12:12Z

‎The goal of the project: typos

OpenIDUser6: /* Application we need: */

2010-03-19T13:57:33Z

‎Application we need:

OpenIDUser6: /* The implementation */

2010-03-19T13:55:58Z

‎The implementation

SabineEller at 13:54, 19 March 2010

2010-03-19T13:54:33Z

Simion314 at 13:52, 19 March 2010

2010-03-19T13:52:25Z

@@ Line 31: / Line 31: @@
 Deployment should be easy, maybe a package that can be just extracted, double click and all should work, this can be made for Linux too, downloading dependencies requires Internet access and administrative rights.
-=== Application we need:  ===
+=== Applications we need:  ===
 *application for learning using the mouse (moving, clicking, double clicking, mouse over a picture discovers it,...)

@@ Line 33: / Line 33: @@
 === Application we need:  ===
-*application for learning using the mouse (moving, clicking, double clicking)
+*application for learning using the mouse (moving, clicking, double clicking, mouse over a picture discovers it,...)
 *application for learning using the arrows keys
@@ Line 39: / Line 39: @@
 *application for learning counting (we have some code for this)
-*application for learning the alphabet and learning reading (example: we have a cat picture the kids should chose letter c(cat begins with c) this should be made in such a way to be cross languages
+*application for learning the alphabet and learning reading (example: we have a cat picture the kids should chose letter c (cat begins with c) this should be made in such a way to be cross languages
 *application for drawing and other application for coloring
 *we should write some games with cars, boys love cars

@@ Line 23: / Line 23: @@
 === The implementation  ===
-Should be simple. We should avoid using lots of &nbsp;other libraries. The application should be easy to deploy cross platform(maybe only parts of it). &nbsp;A good feature would be that it could run on other operating systems stand alone. Depending on KDE core should not stop us reach computers that do not have KDE but have kids who need software.
+Should be simple. We should avoid using lots of &nbsp;other libraries. The application should be easy to deploy cross platform (maybe only parts of it). &nbsp;A good feature would be that it could run on other operating systems stand alone. Depending on KDE core should not stop us reach computers that do not have KDE but have kids who need software.
-The application should remain simple as structure, do one thing and do it better and simple, no generalization(so if we have 2 ideas about a game with letters maybe is better to make 2 games) if the code is simple(not containing 100 classes it is easy for new coders to contribute
+The application should remain simple as structure, do one thing and do it better and simple, no generalization (so if we have 2 ideas about a game with letters maybe it is better to make 2 games) if the code is simple (not containing 100 classes) it is easy for new coders to contribute
-It would be nice that the plugins application could run standalone, someone can download only one application or some of them, put them on a USB flash and setup them on different computers.
+It would be nice that the plugin applications could run standalone, someone can download only one application or some of them, put them on a USB flash and setup them on different computers.
 Deployment should be easy, maybe a package that can be just extracted, double click and all should work, this can be made for Linux too, downloading dependencies requires Internet access and administrative rights.

@@ Line 13: / Line 13: @@
 === The interface  ===
-The interface should be simple:<br>
+The interface should be simple:
-*no menus(kids can't read)
+*no menus (kids can't read)
-*no options dialog(or this should be hidden) maybe a separate application can be used to configure the apps.
+*no options dialog (or this should be hidden) maybe a separate application can be used to configure the apps.
-*a way to block losing focus of the application(block clicking on the menus or starting some compiz/kde effect by moving the mouse on corners ,block the moving/dragging of the window<br>
+*a way to block losing focus of the application (block clicking on the menus or starting some compiz/kde effect by moving the mouse on corners, block the moving/dragging of the window
 === The implementation  ===

@@ Line 9: / Line 9: @@
 === The core &nbsp;  ===
-All the application will be writen as plugins. The core will search and load this plugins. This searching and loading should be fast and simple. We want that the application to be easily extended.
+All the application will be written as plugins. The core will search and load this plugin. This searching and loading should be fast and simple. We want the application to be easily extended.
-−
-<br>
 === The interface  ===

@@ Line 3: / Line 3: @@
 === The goal of the project  ===
-This project aims to create free applications for young kids(less then 7 years old)
+This project aims to create free applications for young kids (less then 7 years old).
- <br>
-The application should be easy to grab from the web ,placed on a CD or USB stick and deployed. The application should reach homes with young kids and kindergartens as easy as possible.
+The application should be easy to grab from the web, placed on a CD or a USB stick and deployed. The application should reach homes with young kids and kindergartens as easy as possible.
-−
 === The core &nbsp;  ===

@@ Line 25: / Line 25: @@
 Should be simple. We should avoid using ots of &nbsp;other libraries. The application should be easy to deploy cross platform(maybe only parts of it). &nbsp;A good feature would be that it could run on other operating systems stand alone. Depending on kde core should not stop us reach computers that do not have KDE but have kids who need software.
-<br>
- The application should remain simple as structure, do one thing and do it better and simple, no generalization(so if we have 2 ideas about a game with letters maybe is better to make 2 games) if the code is simple(not containing 100 classes it is easy for new coders to contribute
+The application should remain simple as structure, do one thing and do it better and simple, no generalization(so if we have 2 ideas about a game with letters maybe is better to make 2 games) if the code is simple(not containing 100 classes it is easy for new coders to contribute
- <br>
- It would be nice that the plugins application could run standalone, someone can download only one application or some of them ,put them on a USB flash and setup them on different computers.
+It would be nice that the plugins application could run standalone, someone can download only one application or some of them ,put them on a USB flash and setup them on different computers.
- <br>
 Deployment should be easy, maybe a package that can be just extracted , double click and all should work, this can be made for Linux too, downloading dependencies requires Internet access and administrative rights.
 === Application we need:  ===