Category talk:Software ideas: Difference between revisions
No edit summary |
(GIS / Mapping Software) |
||
| Line 1: | Line 1: | ||
Java support really aught to be integrated, so that software can be ported on to the OLPC with NO adaptations. JAVA is also a fairly kid-friendly language, and SUN will be open-sourcing parts of it soon, making it ideal. |
Java support really aught to be integrated, so that software can be ported on to the OLPC with NO adaptations. JAVA is also a fairly kid-friendly language, and SUN will be open-sourcing parts of it soon, making it ideal. |
||
== GIS / Mapping Software == |
|||
I would really hope that mapping software is included in the olpc. Although the popular proprietary GIS applications are very large / memory intensive, there are plenty of open source examples already in existance which show that this is feasible within a 100mb size limit. |
|||
Geographical Information Systems are a cross cirricula learning tool, but most obviously, a GIS would compliment the data logging applications described on this wiki, providing a way for children to analyse results. |
|||
The application should focus on use of vector data (point line and polygon) as these are least memory intensive - although raster images could be used if connected to a usb cd drive. |
|||
Revision as of 10:45, 28 November 2006
Java support really aught to be integrated, so that software can be ported on to the OLPC with NO adaptations. JAVA is also a fairly kid-friendly language, and SUN will be open-sourcing parts of it soon, making it ideal.
GIS / Mapping Software
I would really hope that mapping software is included in the olpc. Although the popular proprietary GIS applications are very large / memory intensive, there are plenty of open source examples already in existance which show that this is feasible within a 100mb size limit. Geographical Information Systems are a cross cirricula learning tool, but most obviously, a GIS would compliment the data logging applications described on this wiki, providing a way for children to analyse results. The application should focus on use of vector data (point line and polygon) as these are least memory intensive - although raster images could be used if connected to a usb cd drive.