LOGO: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
Line 3: Line 3:
There are lessons to be learned in all of these systems if OLPC application developers wish to stand on the shoulders of giants rather than reinvent the wheel over and over again.
There are lessons to be learned in all of these systems if OLPC application developers wish to stand on the shoulders of giants rather than reinvent the wheel over and over again.


==variations==
==Variations==
;UCBLogo : http://www.cs.berkeley.edu/~bh/logo.html
;UCBLogo : http://www.cs.berkeley.edu/~bh/logo.html
Needs a better GUI (Brian Harvey is working on one, but he is working on it alone and as a hobby). It can be translated (without recompilation) to languages that have their character sets in 1 byte encodings. It was been translated to Spanish ([http://mondragon.angeltowns.net/logoes/ LogoES])
Needs a better GUI (Brian Harvey is working on one, but he is working on it alone and as a hobby). It can be translated (without recompilation) to languages that have their character sets in 1 byte encodings. It was been translated to Spanish ([http://mondragon.angeltowns.net/logoes/ LogoES])
Line 20: Line 20:
;LogoWiki : http://www.logowiki.net
;LogoWiki : http://www.logowiki.net
Recently developed by Alan Kay and friends. Built on top of JavaScript.
Recently developed by Alan Kay and friends. Built on top of JavaScript.

==Necesary features==
*Multilingual support
*Trigonometric functions, sqrt, exp, power, log, ln (to be able to draw at least [http://mondragon.angeltowns.net/paradiso/Construcciones.html figure 24] accurately)

==Requested Features==
*Optional inputs, like UCBLogo
*ColorUnder (or "Pixel")
*SetPenColor

Revision as of 15:37, 2 June 2006

A powerful programming language built to be easy for children to use. LOGO is essentially a dialect of LISP without the parentheses that traditional LISP requires. It has been implemented in many versions including Brian Harvey's UCBLogo and the multimedia authoring toolkit called Hyperstudio.

There are lessons to be learned in all of these systems if OLPC application developers wish to stand on the shoulders of giants rather than reinvent the wheel over and over again.

Variations

UCBLogo
http://www.cs.berkeley.edu/~bh/logo.html

Needs a better GUI (Brian Harvey is working on one, but he is working on it alone and as a hobby). It can be translated (without recompilation) to languages that have their character sets in 1 byte encodings. It was been translated to Spanish (LogoES)

aUCBLogo
http://www.physik.uni-augsburg.de/~micheler/

Needs testing, packaging and materials (maybe it's still too beta)

MSWLogo
http://www.softronix.com/logo.html

Needs a migration to Linux. Has lots of learning material on the Internet

FMSLogo
http://sourceforge.net/projects/fmslogo

Needs a migration to Linux

PyLogo
http://pylogo.org/PyLogo.html

Works under Python (which, it seems, will be a given in the laptop). Is this enough Logo?

Scratch
http://llk.media.mit.edu/projects/summaries/scratch.shtml

Runs under Squeak (whick is bulky?). Is this enough Logo?

NetLogo
http://ccl.northwestern.edu/netlogo/

Freeware, but not open source. Requires Java. Actively developed; high quality.

LogoWiki
http://www.logowiki.net

Recently developed by Alan Kay and friends. Built on top of JavaScript.

Necesary features

  • Multilingual support
  • Trigonometric functions, sqrt, exp, power, log, ln (to be able to draw at least figure 24 accurately)

Requested Features

  • Optional inputs, like UCBLogo
  • ColorUnder (or "Pixel")
  • SetPenColor