Mono: Difference between revisions

From OLPC
Jump to navigation Jump to search
(New page: To use Mono to write an OLPC activity need to prepare a xo bundle with all library inside it. This is necessary because this environment is not supported by XO device. You can find [http...)
 
No edit summary
Line 1: Line 1:
{{Developers}}

Sugar activities are usually written in Python using the [[API_Reference|Python Activity API]]. This page documents how is possible to use Mono to write a sugar activity. Using Mono you can use any underlying language like C# or Boo.

This page is on an early stage of writing so can be modify often.


=Overview=

=XO Bundle and Mono Bundle=
To use Mono to write an OLPC activity need to prepare a xo bundle with all library inside it.
To use Mono to write an OLPC activity need to prepare a xo bundle with all library inside it.


This is necessary because this environment is not supported by XO device.
This is necessary because this environment is not supported by XO device.


=How to run a Mono activity=
You can find [http://mk8.codewiz.org/wiki/MonkeysMemory-3.xo here] a sample of an activity written using Mono.
You can find [http://mk8.codewiz.org/wiki/MonkeysMemory-3.xo here] a sample of an activity written using Mono.


=Interface with the native subsystem=
More documentation will be present as soon as possible.
More documentation will be present as soon as possible.

Revision as of 16:40, 27 December 2007

Sugar activities are usually written in Python using the Python Activity API. This page documents how is possible to use Mono to write a sugar activity. Using Mono you can use any underlying language like C# or Boo.

This page is on an early stage of writing so can be modify often.


Overview

XO Bundle and Mono Bundle

To use Mono to write an OLPC activity need to prepare a xo bundle with all library inside it.

This is necessary because this environment is not supported by XO device.

How to run a Mono activity

You can find here a sample of an activity written using Mono.

Interface with the native subsystem

More documentation will be present as soon as possible.