Sugar development: Difference between revisions

From OLPC
Jump to navigation Jump to search
(→‎How to start hacking: add Activity Factory doc link)
m (→‎How to start hacking: rename Activity DBus API page)
Line 33: Line 33:
* Marco wrote a quick tutorial on how to make your [[Sugar Activity Tutorial|own Sugar Activity]].
* Marco wrote a quick tutorial on how to make your [[Sugar Activity Tutorial|own Sugar Activity]].
* Dan has some docs up on the [[Presence Service DBus API]].
* Dan has some docs up on the [[Presence Service DBus API]].
* Bert started to document the [[Activity Factory DBus API]].
* Bert started to document the [[Activity DBus API]].
* There is also a page that describes [[Activity Bundles]].
* There is also a page that describes [[Activity Bundles]].
* See [[Sugar Architecture]] for more specifications/documentation.
* See [[Sugar Architecture]] for more specifications/documentation.

Revision as of 10:02, 22 May 2007

Sugar is currently under heavy development, and is meant to be used by developers. There are no binary packages yet available.

(See also the Sugar category for a broad view on the subject)

Development

The easiest way to build Sugar from sources is to use sugar-jhbuild.

You may also want to see the specific instructions for several Linux distributions, for MS-Windows or MacOS X.

(See the Installing Sugar category for further links)

Repositories

Developer site Trac

Emulation and/or Testing

You don't need a real OLPC laptop in order to see what it's like, how it works and test activities—you can use an emulator. OLPC periodically updates the emulation images for the QEMU emulator that is available for *ix, MS-Windows and MacOS X.

(See the Emulation category for further links)

You can find the latest stable build here.

Note: There are ways to convert the QEMU images for use in other emulation software—ie: VMWare's Player—but OLPC image standard is for QEMU.

How to start hacking