Application Developers: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (cutting double redirects) |
||
| (15 intermediate revisions by 10 users not shown) | |||
| Line 1: | Line 1: | ||
#Redirect [[Developers manual]] |
|||
==Introduction== |
|||
The OLPC needs a wide array of educational applications developed according to [[constructionist]] educational principles. Technically, these applications could be developed in any language supported by Linux, however the OLPC simply does not support the storage required to support all the possible runtime environments. |
|||
Therefore, application developers should restrict themselves to using C or the [[OLPC Python Environment]]. In addition, application developers need to be careful about using any add-on libraries, even those which may be standard issue with Python. The OLPC team may decide to remove any component which is deemed to be redundant. This leads to the following principles: |
|||
*Check to see what libraries are included before you begin development |
|||
*Carefully choose support modules to minimize your storage footprint, for instance if you need a database, choose Sqlite rather than MySQL. Or better yet, use dbm. |
|||
*Test your application in a minimal environment such as one of the [[Minimal Linux distros]] or [[Development Systems]]. |
|||
*If you are unsure what is supported, ask. |
|||
*Use [[Python]] rather than C whenever possible to minimize storage footprint. A few kilobytes of Python source can accomplish the same job as many kilobytes of C object code because it leverages the Python runtime. |
|||
*Test you application with .pyc files only since the .py source will not normally be included in an installation. |
|||
*Distribute your source code under an Open Source license. |
|||
[[Category:Developers]] |
|||
Latest revision as of 08:45, 16 January 2008
Redirect to: