Development Team/Manual: Difference between revisions

Line 16:

== Overview ==

* [[~~Developers~~/Setup]]

* [[DevelopmentTeam/Manual/Setup]]

** Describes how to set up a [[Sugar]] development environment on your PC or workstation. It discusses emulation, running Sugar OS natively or in a virtual machine, cross compiling, and some configuration options. It also includes a discussion of which approach is likely to be the most appropriate for you

** Describes how to set up a Sugar development environment on your PC or workstation. It discusses emulation, running Sugar OS natively or in a virtual machine, cross compiling, and some configuration options. It also includes a discussion of which approach is likely to be the most appropriate for you

* [[Test Config Notes]]

** If you have an XO, this page has many useful configuration tips for testing your application.

* [[Developers/Stack]]

** Describes the choices of programming languages and "software stacks" for developing code on the OLPC. It details the base stack of hardware, firmware, operating system and the [[Sugar]] environment. It then gives options for programming in Python, Squeak, C/C++ and other languages or activities.

** Describes the choices of programming languages and "software stacks" for developing code on the OLPC. It details the base stack of hardware, firmware, operating system and the Sugar environment. It then gives options for programming in Python, Squeak, C/C++ and other languages or activities.

* [[Developers/Issues]]

** Describes the special considerations required for working on the OLPC project, particularly those driven by our target hardware and deployment environments

Line 32:

* [[Developers/FAQ]]

** Collects and attempts to answer common questions that developers have when working on the Sugar platform

~~== Release Schedule ==~~

We expect to be doing updates monthly through the first quarter of 2008. After that, we will likely adopt a three-month update cycle. Eventually we will adopt a six-month update cycle. It should also be noted that we will be—when time permits—moving to a build environment that enables individual activity developers to maintain their own build cycles.

== Related docs and manuals ==

@@ Line 16: / Line 16: @@
 == Overview ==
-* [[Developers/Setup]]
+* [[DevelopmentTeam/Manual/Setup]]
-** Describes how to set up a [[Sugar]] development environment on your PC or workstation.  It discusses emulation, running Sugar OS natively or in a virtual machine, cross compiling, and some configuration options.  It also includes a discussion of which approach is likely to be the most appropriate for you
+** Describes how to set up a Sugar development environment on your PC or workstation.  It discusses emulation, running Sugar OS natively or in a virtual machine, cross compiling, and some configuration options.  It also includes a discussion of which approach is likely to be the most appropriate for you
 * [[Test Config Notes]]
 ** If you have an XO, this page has many useful configuration tips for testing your application.
 * [[Developers/Stack]]
-** Describes the choices of programming languages and "software stacks" for developing code on the OLPC.  It details the base stack of hardware, firmware, operating system and the [[Sugar]] environment.  It then gives options for programming in Python, Squeak, C/C++ and other languages or activities.
+** Describes the choices of programming languages and "software stacks" for developing code on the OLPC.  It details the base stack of hardware, firmware, operating system and the Sugar environment.  It then gives options for programming in Python, Squeak, C/C++ and other languages or activities.
 * [[Developers/Issues]]
 ** Describes the special considerations required for working on the OLPC project, particularly those driven by our target hardware and deployment environments
@@ Line 32: / Line 32: @@
 * [[Developers/FAQ]]
 ** Collects and attempts to answer common questions that developers have when working on the Sugar platform
-== Release Schedule ==
-We expect to be doing updates monthly through the first quarter of 2008. After that, we will likely adopt a three-month update cycle. Eventually we will adopt a six-month update cycle.  It should also be noted that we will be—when time permits—moving to a build environment that enables individual activity developers to maintain their own build cycles.
 == Related docs and manuals ==