Patrol: moved Walter is a wanker 12/Issues to Development Team/Issues over redirect: revert

2010-02-24T01:33:06Z

moved Walter is a wanker 12/Issues to Development Team/Issues over redirect: revert

← Older revision	Revision as of 21:33, 23 February 2010
(No difference)

Page move vandal: moved Development Team/Issues to Walter is a wanker 12/Issues: Walter is a wanker

2010-02-24T00:21:21Z

moved Development Team/Issues to Walter is a wanker 12/Issues: Walter is a wanker

← Older revision	Revision as of 20:21, 23 February 2010
(No difference)

Patrol: moved Anal bleaching 15/Issues to Development Team/Issues over redirect: revert

2010-02-21T22:41:59Z

moved Anal bleaching 15/Issues to Development Team/Issues over redirect: revert

← Older revision	Revision as of 18:41, 21 February 2010
(No difference)

Anal bleaching: moved Development Team/Issues to Anal bleaching 15/Issues: Anal bleaching

2010-02-21T22:22:31Z

moved Development Team/Issues to Anal bleaching 15/Issues: Anal bleaching

← Older revision	Revision as of 18:22, 21 February 2010
(No difference)

FGrose at 21:10, 22 October 2009

2009-10-22T21:10:51Z

FGrose: DevelopmentTeam/Issues moved to Development Team/Issues: deCamel casing

2009-03-17T20:45:05Z

DevelopmentTeam/Issues moved to Development Team/Issues: deCamel casing

← Older revision	Revision as of 16:45, 17 March 2009
(No difference)

Dfarning: Development issues moved to DevelopmentTeam/Issues: Contents fit best under the DevelopmentTeam

2008-06-25T02:32:13Z

Development issues moved to DevelopmentTeam/Issues: Contents fit best under the DevelopmentTeam

← Older revision	Revision as of 22:32, 24 June 2008
(No difference)

Cjl at 05:37, 12 June 2008

2008-06-12T05:37:46Z

← Older revision		Revision as of 01:37, 12 June 2008
Line 1:		Line 1:
	{{~~OLPC~~}}		<noinclude>{{ GoogleTrans-en \| es =show \| bg =show \| zh-CN =show \| zh-TW =show \| hr =show \| cs =show \| da =show \| nl =show \| fi =show \| fr =show \| de =show \| el =show \| hi =show \| it =show \| ja =show \| ko =show \| no =show \| pl =show \| pt =show \| ro =show \| ru =show \| sv =show }}</noinclude>

	'''Note''': The [[Developers\|Developer's Manual]] provides more comprehensive and up-to-date introductions to the issues described here.		'''Note''': The [[Developers\|Developer's Manual]] provides more comprehensive and up-to-date introductions to the issues described here.

Dfarning-bot: Robot: Removing from Category:Developers

2008-06-07T18:17:10Z

Robot: Removing from Category:Developers

← Older revision		Revision as of 14:17, 7 June 2008
Line 51:		Line 51:
	* '''What kind of applications are needed?'''		* '''What kind of applications are needed?'''
	:have a look at [[Sample Applications]] for some ideas. Or, release an early prototype of your own app as a sample application to help others learn the ropes of developping for this innovative, i.e. non-standard laptop.		:have a look at [[Sample Applications]] for some ideas. Or, release an early prototype of your own app as a sample application to help others learn the ropes of developping for this innovative, i.e. non-standard laptop.

	~~[[Category:Developers]]~~

Dfarning: 47 revisions

2008-06-06T20:49:13Z

47 revisions

← Older revision	Revision as of 16:49, 6 June 2008
(No difference)

← Older revision		Revision as of 17:10, 22 October 2009
Line 1:		Line 1:
	<noinclude>{{ GoogleTrans-en \| es =show \| bg =show \| zh-CN =show \| zh-TW =show \| hr =show \| cs =show \| da =show \| nl =show \| fi =show \| fr =show \| de =show \| el =show \| hi =show \| it =show \| ja =show \| ko =show \| no =show \| pl =show \| pt =show \| ro =show \| ru =show \| sv =show }}</noinclude>		<noinclude></noinclude>
	'''Note''': The [[Developers~~\|Developer's Manual~~]] provides more comprehensive and up-to-date introductions to the issues described here.		'''Note''': The [[olpc:Developers manual]] provides more comprehensive and up-to-date introductions to the issues described here.

	Here are a few of the most obvious development issues/questions/comments:		Here are a few of the most obvious development issues/questions/comments:
	* '''What language should be used to develop applications?'''		* '''What language should be used to develop applications?'''
	:You can use C, C++, [[Python]], JavaScript, [[Flash]], or [[Smalltalk]]. Other languages are possible of course, but will require that any libraries and/or interpreter be included as part of your activity. Notably absent are Java, C#, Perl, Tcl, and Ruby. GTK is the primary GUI widget library in use on the laptop; it supports the theme.		:You can use C, C++, [[olpc:Python]], JavaScript, [[olpc:Flash]], or [[olpc:Smalltalk]]. Other languages are possible of course, but will require that any libraries and/or interpreter be included as part of your activity. Notably absent are Java, C#, Perl, Tcl, and Ruby. GTK is the primary GUI widget library in use on the laptop; it supports the theme.
	* '''What is the API?'''		* '''What is the API?'''
	:The [[Low-level Activity API]] page attempts to cover this, but is frequently incomplete. Documentation help would be very useful.		:The [[olpc:Low-level Activity API]] page attempts to cover this, but is frequently incomplete. Documentation help would be very useful.
	* '''Will the laptops and/or an emulator be available to developers interested in direct contibutions to OLPC?'''		* '''Will the laptops and/or an emulator be available to developers interested in direct contibutions to OLPC?'''
	:'''Yes!!!''' See the [[Developers Program]] for details. Also read the [[Development Systems]] page for ideas of using other minimal systems to do your application testing.		:'''Yes!!!''' See the [[olpc:Developers Program]] for details. Also read the [[olpc:Development Systems]] page for ideas of using other minimal systems to do your application testing.
	*'''What if I don't qualify for one of the development systems?'''		*'''What if I don't qualify for one of the development systems?'''
	:You can still build something as long as you are careful to isolate the GUI portions of your code and not do anything overly complex. Or, if you use [[PyGTK]], then you come very close to the real development environment in [[Sugar]]. If you will be programming in a compiled language or in assembly, make sure that you are aware (and respect) the [[Geode instruction set]]. It is about the same as the original Athlon instruction set. See the Geode data book linked in the [[Geode instruction set]] page.		:You can still build something as long as you are careful to isolate the GUI portions of your code and not do anything overly complex. Or, if you use [[olpc:PyGTK]], then you come very close to the real development environment in [[olpc:Sugar]]. If you will be programming in a compiled language or in assembly, make sure that you are aware (and respect) the [[olpc:Geode instruction set]]. It is about the same as the original Athlon instruction set. See the Geode data book linked in the [[olpc:Geode instruction set]] page.
	* '''Where can I find the sources?'''		* '''Where can I find the sources?'''
	:If you are a skilled *IX user then the [[Sugar]] page should help. But most developers who will be working on OLPC will be using Python to develop educational applications.		:If you are a skilled *IX user then the [[olpc:Sugar]] page should help. But most developers who will be working on OLPC will be using Python to develop educational applications.
	* '''Memory footprint of applications'''		* '''Memory footprint of applications'''
	:It must be as small as you can make it. These are memory-constrained devices.		:It must be as small as you can make it. These are memory-constrained devices.
Line 19:		Line 19:
	: You need to measure the memory usage repeatedly while thoroughly exercising your program. Sample the memory size every minute and graph it. If there is a slowly increasing size, then you have a leak. A normal program will increase rapidly at the beginning and then remain perfectly flat or shrink and grow repeatedly. Remember that every leak, however small, counts!		: You need to measure the memory usage repeatedly while thoroughly exercising your program. Sample the memory size every minute and graph it. If there is a slowly increasing size, then you have a leak. A normal program will increase rapidly at the beginning and then remain perfectly flat or shrink and grow repeatedly. Remember that every leak, however small, counts!
	* '''Required flash footprint of the application'''		* '''Required flash footprint of the application'''
	:if it is big, there may not be space. However, [[JFFS2]] does data compression, so don't presume that the size of a file in a conventional file system corresponds to the actual amount of flash used. As a rule of thumb, expect a factor of 2 compression for text and typical data, expect no compression on already compressed content, but take actual measurements to understand what your actual flash usage will be.		:if it is big, there may not be space. However, [[olpc:JFFS2]] does data compression, so don't presume that the size of a file in a conventional file system corresponds to the actual amount of flash used. As a rule of thumb, expect a factor of 2 compression for text and typical data, expect no compression on already compressed content, but take actual measurements to understand what your actual flash usage will be.
	: If you test on a Unix system you can install [[JFFS2]] and test directly. Since [[JFFS2]] does block compression you can affect the amount of compression by reorganizing your code.		: If you test on a Unix system you can install [[olpc:JFFS2]] and test directly. Since [[olpc:JFFS2]] does block compression you can affect the amount of compression by reorganizing your code.
	* '''Your application should be engineered and packaged to make it easy to strip unneeded functionality.'''		* '''Your application should be engineered and packaged to make it easy to strip unneeded functionality.'''
	:For example, GAIM supports just about every IM protocol in existance, but we can only anticipate 3 being common. So the fact it uses plugins that we can choose to not package saves greatly on its footprint, whereas if everything were built in, both the memory and flash footprint would be much larger.		:For example, GAIM supports just about every IM protocol in existance, but we can only anticipate 3 being common. So the fact it uses plugins that we can choose to not package saves greatly on its footprint, whereas if everything were built in, both the memory and flash footprint would be much larger.
Line 29:		Line 29:
	* '''No 3D hardware:''' we don't have shaded triangles or a geometry pipe; so any OpenGL used will be based on Mesa, and without hardware, will be very slow		* '''No 3D hardware:''' we don't have shaded triangles or a geometry pipe; so any OpenGL used will be based on Mesa, and without hardware, will be very slow
	:Ideally, don't use OpenGL at all except for specialty applications which absolutely must and which can accept the slow rendering. For instance a design program could use OpenGL to provide a rendered view because most of the time the user will not be using OpenGL.		:Ideally, don't use OpenGL at all except for specialty applications which absolutely must and which can accept the slow rendering. For instance a design program could use OpenGL to provide a rendered view because most of the time the user will not be using OpenGL.
	:Remember that the [[Geode]] supports MMX and Enhanced 3DNow!, which can speed up some applications, such as 3D rendering, and should be appropriately used.		:Remember that the [[olpc:Geode]] supports MMX and Enhanced 3DNow!, which can speed up some applications, such as 3D rendering, and should be appropriately used.
	* '''Choice of libraries and required applications:''' you may not have the dependencies you might need, or those dependencies might come at too high a memory cost. We will inventory what you can "count on" in the basic system as it becomes clear.		* '''Choice of libraries and required applications:''' you may not have the dependencies you might need, or those dependencies might come at too high a memory cost. We will inventory what you can "count on" in the basic system as it becomes clear.
	: In the meantime, make sure you know your application's dependencies. For compiled code, run it with "ldd" to get a list of all the libraries being loaded. For Python code, run it with "python -v" to get a list of all modules imported.		: In the meantime, make sure you know your application's dependencies. For compiled code, run it with "ldd" to get a list of all the libraries being loaded. For Python code, run it with "python -v" to get a list of all modules imported.
Line 39:		Line 39:
	:Python is an interpreted language, similar in operation to perl. It lacks a JIT, though it does use an intermediate code form rather than strictly interpreting the raw text as a shell script or makefile would. It is thus inherently slower than C# or Java, but not as bad as it could be. A more serious problem for Python is often memory consumption.		:Python is an interpreted language, similar in operation to perl. It lacks a JIT, though it does use an intermediate code form rather than strictly interpreting the raw text as a shell script or makefile would. It is thus inherently slower than C# or Java, but not as bad as it could be. A more serious problem for Python is often memory consumption.
	* Remember that your '''slow code''' has a direct impact on power consumption (far more than on a desktop), and its usability. Applications that run slowly or don't let the processor idle will be very, very unpopular on battery powered machines that may be powered by children having to run a generator.		* Remember that your '''slow code''' has a direct impact on power consumption (far more than on a desktop), and its usability. Applications that run slowly or don't let the processor idle will be very, very unpopular on battery powered machines that may be powered by children having to run a generator.
	* '''The file system''' is a flash file system, so its write performance is slow, while random access is actually very good. The performance is glacial if the file system is low on space and has to continually erase freed blocks before writing ([[JFFS2]] attempts to do this in the background, but if it can't....). Programs that continually write to the file system without need are anti-social; wear leveling helps flash longevity, but it certainly doesn't help, and burns power. Writable file mappings (via the mmap system call) may not be supported.		* '''The file system''' is a flash file system, so its write performance is slow, while random access is actually very good. The performance is glacial if the file system is low on space and has to continually erase freed blocks before writing ([[olpc:JFFS2]] attempts to do this in the background, but if it can't....). Programs that continually write to the file system without need are anti-social; wear leveling helps flash longevity, but it certainly doesn't help, and burns power. Writable file mappings (via the mmap system call) may not be supported.
	* '''Looping waiting for events (or other busy-waiting) eats power;''' don't do it. Poll and select with timeouts are your friends. Don't gratuitously wake up at frequent intervals just to test if something has happened; design your hardware and software to be completely idle between events they have to respond to.		* '''Looping waiting for events (or other busy-waiting) eats power;''' don't do it. Poll and select with timeouts are your friends. Don't gratuitously wake up at frequent intervals just to test if something has happened; design your hardware and software to be completely idle between events they have to respond to.
	:Right now this is a nice summary page. But items like this deserve some more explanation along with some sample code that uses select/poll/inotify/signals instead of busy-waiting.		:Right now this is a nice summary page. But items like this deserve some more explanation along with some sample code that uses select/poll/inotify/signals instead of busy-waiting.
Line 45:		Line 45:
	* '''Applications should be localizable.'''		* '''Applications should be localizable.'''
	: If you will be using Python, start by reading these 31 slides about how to use Unicode in Python: http://downloads.egenix.com/python/LSM2005-Developing-Unicode-aware-applications-in-Python.pdf		: If you will be using Python, start by reading these 31 slides about how to use Unicode in Python: http://downloads.egenix.com/python/LSM2005-Developing-Unicode-aware-applications-in-Python.pdf
	: Next, read the [[Gettext\|page on gettext]] and it's [http://www.gnu.org/software/gettext documentation]. Become familiar with GTK+ and Pango features for I18N and L10N.		: Next, read the [[olpc:Gettext\|page on gettext]] and it's [http://www.gnu.org/software/gettext documentation]. Become familiar with GTK+ and Pango features for I18N and L10N.
	: You can create a fake translation with lengthy text containing non-ASCII characters. It is common to do this with Cyrillic (Russian) and Greek characters that are shaped similar to English characters. Does the text get rendered? Are any graphical elements too small? East-Asian characters may need extra height, along with some of the double-accented characters used in Eastern Europe. Right-to-left scripts like Arabic should also be considered.		: You can create a fake translation with lengthy text containing non-ASCII characters. It is common to do this with Cyrillic (Russian) and Greek characters that are shaped similar to English characters. Does the text get rendered? Are any graphical elements too small? East-Asian characters may need extra height, along with some of the double-accented characters used in Eastern Europe. Right-to-left scripts like Arabic should also be considered.
	* '''Read and comprehend Dave Jones' paper on "Why Userspace Sucks";''' a summary and pointers to the paper can be found at [http://lwn.net/Articles/192214/ LWN]. Note that most of those problems are now being worked on; please do not make similar mistakes!		* '''Read and comprehend Dave Jones' paper on "Why Userspace Sucks";''' a summary and pointers to the paper can be found at [http://lwn.net/Articles/192214/ LWN]. Note that most of those problems are now being worked on; please do not make similar mistakes!
	* '''What kind of applications are needed?'''		* '''What kind of applications are needed?'''
	:have a look at [[Sample Applications]] for some ideas. Or, release an early prototype of your own app as a sample application to help others learn the ropes of developping for this innovative, i.e. non-standard laptop.		:have a look at [[olpc:Sample Applications]] for some ideas. Or, release an early prototype of your own app as a sample application to help others learn the ropes of developping for this innovative, i.e. non-standard laptop.

Development Team/Issues - Revision history