Hello Serge,
Also we may want:
- provide VM based on COG, the XO-1 are pretty slow, although XO 1.5 are
better.
- propose a sugar theme for Pharo (it is about 70% complete with some
issues depending on Gary help)
- When Pharo is used to deploy application, what we should think about
is how to load fast Smalltalk code in an existing Pharo installation in
the XO notebook.
I am pretty sure we can have quite visible and important impact!
Nonetheless, an important argument we want to sell with such a set up:
"Develop there, deploy anywhere"
Geert, yes browser may not the easiest. We should iterate on how to
improve the IDE if we want kids to write in some way Smalltalk code. May
be the Workspace is more importante at the first place.
Hilaire
Le 07/07/2010 05:54, Serge Stinckwich a écrit :
What should be done:
- build a specific VM (reuse EToys work),
- port D-BUS to Pharo : http://wiki.laptop.org/go/D-BUS This is mostly
used to communicate with OLPC-services. There is already an EToys
version: http://www.squeaksource.com/dbus.html
- package Pharo as an xo package,
- adapt PBE to have a PBE-Sugar edition.
PS: I have a couple of XO machines for testing purpose.
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
