There are different options to connect your arduino board to Sugar (trough sugar-capable activities)
For example.
==Squeak==
Thanks to the great work found on [http://tecnodacta.com.ar/gira/ Gira]
We can download an squeak project and install it on our Sugar.
This script can help in the process.
#/bin/bash
echo "Downloading.."
echo ""
curl -o Arduino.zip http://tecnodacta.com.ar/gira/Arduino.7.zip
unzip Arduino.zip
echo "Executing.."
echo ""
cd Arduino.7/
./Arduino.sh
''Note that on an XO laptop you have to tweak some your Arduino.sh script in these or similar ways''
#!/bin/sh
APP=`dirname $0`
EXE="$APP/Contents/Linux686"
RES="$APP/Contents/Resources"
exec "/usr/bin/squeak" \
-plugins "$EXE" \
-encoding latin1 \
-vm-display-X11 \
"$RES/Arduino.2.image"
==Turtle Art==
The code needed is located at (Thanks to Sayamindu Dasgupta)
*http://git.sugarlabs.org/projects/turtleart/repos/arduino-support
TODO: Link to an XO bundle.
This uses the same [http://www.firmata.org firmata] protocol that the arduino-squeak connection uses.
===Some use examples and Screenshots===
*[http://people.sugarlabs.org/sayamindu/ta_arduino.png]
*[http://people.sugarlabs.org/rafael/Arduino-turtle1.png]
*[http://people.sugarlabs.org/rafael/Draw-leds.png]
More information:
*http://wiki.sugarlabs.org/go/Development_Team/Arduino
== Spanish Version ==
Please go to
* http://co.sugarlabs.org/go/Arduino
Sunday, December 27, 2009
Friday, September 11, 2009
OLPC and Sugar, Live dreams
I like to publicize here Nicholas Negroponte and Walter Bender's response to one blog, a particularly bad documented one by Alanna Shaikh on a UN Foundation-sponsored site (http://www.undispatch.com/node/8859):
First NN response:
''The dream is not over. When OLPC started there were no low cost laptops. We created the category less than four years ago and it now represents almost one third of the world production of latops. I am not aware of too many technologies that have gone from “impossible” to such wide adoption.
The million laptops, our little green ones, that are in the hands of children, are currently in 19 languages and 31 countries. Another million are on their way. Not bad. But even better, these countries include Afghanistan, Haiti, Ethiopia, as well as places like the West Bank (and next month Gaza). Even better, eh?
I suggest you look more carefully at Uruguay, Peru and Rwanda. In the case of Uruguay, every child has one. That is pretty amazing. Peru is headed there. Rwanda too. In fact, we have moved our learning group (as of early June) to Kigali perminently, to be in the field and get the kind of feedback you claim we ignore.
Anyway. I do not normally answer press and blogs, because we would spend all our time with words, not actions in the field But you are on a UN site and the UN is our partner. Check out Kofi Annan’s words -- they have been fulfilled. Has it been harder than I expected? Yes. But do you know why? It is not due to what I had anticipated, things like corruption and logistics. It has been due to commercial interests and press, stories like yours.
As a small non-profit, humanitarian organization, it is hard to battle giants who view children as a market, not a mission, and have other agendas. In spite of all that, the change is huge. I no longer hear people arguing against “one laptop per child” as a concept. The issue is purely a matter of funding and there are many ways to do that. Wait and see.
Nicholas Negroponte''
And Walter's one:
''I am writing in response to Alanna Shaikh’s 9/9/09 article, “One Laptop Per Child – The Dream is Over”.
Not only is the dream not over, the OLPC project has created an opportunity for the pursuit of more dreams by many more people.
I was Nicholas Negroponte’s partner in founding One Laptop per Child. As Nicholas has elegantly stated in his response to Ms. Shaikh’s blog, we spawned the netbook market, which is bringing the price of computing within reach of millions more people. In addition, we launch a free software initiative, Sugar Labs, that is putting educational software into the hands of children.
Sugar Labs (www.sugarlabs.org) is an independent outgrowth of OLPC. We are a global community of volunteers—teachers and software developers—whose mission is to bring the advantages of the Sugar learning platform to children everywhere, on any computer. Sugar was designed specially for children and offers a better alternative for young learners than traditional “office-desktop” software. Indeed, nothing in our children’s future has anything to do with office work from 30 years ago.
Ms. Shaikh is mistaken in her assertion that OLPC has abandoned “the special child-friendly OS.” More than 99% of the OLPC laptops in the hands of children run Sugar. Governments prefer Sugar because of its superior quality, openness, built-in collaboration, easy internationalization and localization to indigenous languages, and unbeatable price (free).
Sugar on a Stick, our latest initiative, allows children fortunate enough to have access to a computer at school, in the community, at home (or only the occasional access to a computer in an Internet café) to benefit from Sugar with a simple USB stick, which costs less than US $5. Sugar on a Stick runs on netbooks, but it also runs on hand-me-down computers, typical of those found in schools, that can only limp along running Windows.
We invite you to contact as we will be pleased to answer any of your questions about Sugar, the free learning platform used in schools every day in countries around the world.''
There are ideas that change the world, we see that as we apply them, these kinds of ideas never sleep.
First NN response:
''The dream is not over. When OLPC started there were no low cost laptops. We created the category less than four years ago and it now represents almost one third of the world production of latops. I am not aware of too many technologies that have gone from “impossible” to such wide adoption.
The million laptops, our little green ones, that are in the hands of children, are currently in 19 languages and 31 countries. Another million are on their way. Not bad. But even better, these countries include Afghanistan, Haiti, Ethiopia, as well as places like the West Bank (and next month Gaza). Even better, eh?
I suggest you look more carefully at Uruguay, Peru and Rwanda. In the case of Uruguay, every child has one. That is pretty amazing. Peru is headed there. Rwanda too. In fact, we have moved our learning group (as of early June) to Kigali perminently, to be in the field and get the kind of feedback you claim we ignore.
Anyway. I do not normally answer press and blogs, because we would spend all our time with words, not actions in the field But you are on a UN site and the UN is our partner. Check out Kofi Annan’s words -- they have been fulfilled. Has it been harder than I expected? Yes. But do you know why? It is not due to what I had anticipated, things like corruption and logistics. It has been due to commercial interests and press, stories like yours.
As a small non-profit, humanitarian organization, it is hard to battle giants who view children as a market, not a mission, and have other agendas. In spite of all that, the change is huge. I no longer hear people arguing against “one laptop per child” as a concept. The issue is purely a matter of funding and there are many ways to do that. Wait and see.
Nicholas Negroponte''
And Walter's one:
''I am writing in response to Alanna Shaikh’s 9/9/09 article, “One Laptop Per Child – The Dream is Over”.
Not only is the dream not over, the OLPC project has created an opportunity for the pursuit of more dreams by many more people.
I was Nicholas Negroponte’s partner in founding One Laptop per Child. As Nicholas has elegantly stated in his response to Ms. Shaikh’s blog, we spawned the netbook market, which is bringing the price of computing within reach of millions more people. In addition, we launch a free software initiative, Sugar Labs, that is putting educational software into the hands of children.
Sugar Labs (www.sugarlabs.org) is an independent outgrowth of OLPC. We are a global community of volunteers—teachers and software developers—whose mission is to bring the advantages of the Sugar learning platform to children everywhere, on any computer. Sugar was designed specially for children and offers a better alternative for young learners than traditional “office-desktop” software. Indeed, nothing in our children’s future has anything to do with office work from 30 years ago.
Ms. Shaikh is mistaken in her assertion that OLPC has abandoned “the special child-friendly OS.” More than 99% of the OLPC laptops in the hands of children run Sugar. Governments prefer Sugar because of its superior quality, openness, built-in collaboration, easy internationalization and localization to indigenous languages, and unbeatable price (free).
Sugar on a Stick, our latest initiative, allows children fortunate enough to have access to a computer at school, in the community, at home (or only the occasional access to a computer in an Internet café) to benefit from Sugar with a simple USB stick, which costs less than US $5. Sugar on a Stick runs on netbooks, but it also runs on hand-me-down computers, typical of those found in schools, that can only limp along running Windows.
We invite you to contact as we will be pleased to answer any of your questions about Sugar, the free learning platform used in schools every day in countries around the world.''
There are ideas that change the world, we see that as we apply them, these kinds of ideas never sleep.
Tuesday, September 01, 2009
Local Labs organization (II)
Deep inside a local labs, we have to consider a general internal organization.
These are the proposed objectives of a local labs
* Adapt the technology and pedagogy to an area's culture and resources (e.g, developing activities and content specific to a region)
* Help translate Sugar to the local language(s)
* Support Sugar deployments in area schools
* Create a local community devoted to the Sugar Labs principles, making Sugar more open and sustainable
* Provide for communication,between the local communities and the global Sugar Labs community
* Develop Local content and software that can be used not only for local purposes but also for the overall community
* Host, co-host or partner in the organization of conferences, workshops, talks and meetings related to the use or development of Sugar,
And these are the means proposed to accomplish these objectives.
* A university connection as a local human resource
* A local pilot user group from which to learn
* A local passion or sub-goal that provides a rational for the work
* Bi-directional communication with the global Sugar community and other Sugar Labs
* A sustainable and well-defined entrepreneurship model
* A program to reach out to local free-software community and local industry.
* A marketing program or roadmap
Internally each local labs, have to divide responsibilities between the individuals to achieve objectives, implement programs and with that reach sustainability.
But overall the people involved have to be passionate about education and free software, they have to be passionate about cultural and social changes, they have to share their knowledge and construct innovation starting from the joy of collaboration, because after all, love is better master than duty.
now we have three Local Labs starting around the world, we expect that many would start between this and next year.
* http://co.sugarlabs.org/go/Laboratorios_Azúcar_Colombia Colombia Local Labs
* http://cl.sugarlabs.org/go/Página_Principal Chile Local Labs
* http://wiki.sugarlabs.org/go/Sugar_Labs_DC Washington DC Local Labs
These are the proposed objectives of a local labs
* Adapt the technology and pedagogy to an area's culture and resources (e.g, developing activities and content specific to a region)
* Help translate Sugar to the local language(s)
* Support Sugar deployments in area schools
* Create a local community devoted to the Sugar Labs principles, making Sugar more open and sustainable
* Provide for communication,between the local communities and the global Sugar Labs community
* Develop Local content and software that can be used not only for local purposes but also for the overall community
* Host, co-host or partner in the organization of conferences, workshops, talks and meetings related to the use or development of Sugar,
And these are the means proposed to accomplish these objectives.
* A university connection as a local human resource
* A local pilot user group from which to learn
* A local passion or sub-goal that provides a rational for the work
* Bi-directional communication with the global Sugar community and other Sugar Labs
* A sustainable and well-defined entrepreneurship model
* A program to reach out to local free-software community and local industry.
* A marketing program or roadmap
Internally each local labs, have to divide responsibilities between the individuals to achieve objectives, implement programs and with that reach sustainability.
But overall the people involved have to be passionate about education and free software, they have to be passionate about cultural and social changes, they have to share their knowledge and construct innovation starting from the joy of collaboration, because after all, love is better master than duty.
now we have three Local Labs starting around the world, we expect that many would start between this and next year.
* http://co.sugarlabs.org/go/Laboratorios_Azúcar_Colombia Colombia Local Labs
* http://cl.sugarlabs.org/go/Página_Principal Chile Local Labs
* http://wiki.sugarlabs.org/go/Sugar_Labs_DC Washington DC Local Labs
Tuesday, August 18, 2009
Local Labs organization (I)
As intended from the beginning, SugarLabs is a distributed FLOSS organization, anyone can be part of Sugarlabs and also can found organizations that can support or share the same or similar objectives Sugarlabs is supporting.
Local Labs are organized to supply specific needings of countries where sugar is deployed,
some of them are constituted of volunteers that want to have economic support to be able to help,
in other words they need help to help others, but this organizations although motivated by charity are doing entrepreneurship models to be soustanaible and scalable, to include and not to exclude all learners (parents, teachers, students, developers and deployers).
Although the local labs effort is young we have seen a nascent interest on it, because we are looking for a more independent way of thinking and this thinking has to be applied not only to ideas but also to real life procedures; liberty generates empathy and facilitates inclusion of new supporters and cultivates ideas.
But independence doesn't mean ignoring other people's point of view, and local labs have to have a good communication between them and the overall Sugarlabs that is also composed of local labs,
in a way of saying there is not a centralized Sugarlabs, there is a central place of virtual gathering namely mail-lists, wiki's and IRC channels.
Some orgs (not necessarily FLOSS oriented) have chosen the other way around, they impose all in a centralized way.
but this is not sustainable or scalable and then they have been doing some fragmentation of it's own orgs in entities like nemeorg-LA or nameorg-India or nameorg-USA. and each one independent from the central nameorg but without an straight-trough way of communication between them, in other words, they are now adopting some of the federated way of thinking but without having the advantages of it, the future for these centralized organizations is not too bright because they are exercising the same top-down ideas in all it's fragmented partners, when they try to impose
or ''give'' a solution to different countries or third-parties, they are working ''for'' them and not ''with'' them, this generate opossing forces that act against their progress even from the start, so they have to work not only to solve the problems that it's mission implies but also these pre-existent forces, due to the fact that artificial solutions don't solve the real needs of communities because they ''interpret'' communities needs and don't work side-by-side to solve them.
The first part of this blog talks about the need for a distributed FLOSS organization, the second part would discuss it's organization specifics, what we are lacking and what we are doing well.
Local Labs are organized to supply specific needings of countries where sugar is deployed,
some of them are constituted of volunteers that want to have economic support to be able to help,
in other words they need help to help others, but this organizations although motivated by charity are doing entrepreneurship models to be soustanaible and scalable, to include and not to exclude all learners (parents, teachers, students, developers and deployers).
Although the local labs effort is young we have seen a nascent interest on it, because we are looking for a more independent way of thinking and this thinking has to be applied not only to ideas but also to real life procedures; liberty generates empathy and facilitates inclusion of new supporters and cultivates ideas.
But independence doesn't mean ignoring other people's point of view, and local labs have to have a good communication between them and the overall Sugarlabs that is also composed of local labs,
in a way of saying there is not a centralized Sugarlabs, there is a central place of virtual gathering namely mail-lists, wiki's and IRC channels.
Some orgs (not necessarily FLOSS oriented) have chosen the other way around, they impose all in a centralized way.
but this is not sustainable or scalable and then they have been doing some fragmentation of it's own orgs in entities like nemeorg-LA or nameorg-India or nameorg-USA. and each one independent from the central nameorg but without an straight-trough way of communication between them, in other words, they are now adopting some of the federated way of thinking but without having the advantages of it, the future for these centralized organizations is not too bright because they are exercising the same top-down ideas in all it's fragmented partners, when they try to impose
or ''give'' a solution to different countries or third-parties, they are working ''for'' them and not ''with'' them, this generate opossing forces that act against their progress even from the start, so they have to work not only to solve the problems that it's mission implies but also these pre-existent forces, due to the fact that artificial solutions don't solve the real needs of communities because they ''interpret'' communities needs and don't work side-by-side to solve them.
The first part of this blog talks about the need for a distributed FLOSS organization, the second part would discuss it's organization specifics, what we are lacking and what we are doing well.
Monday, December 15, 2008
SugarLabs, Local Labs, World labs.
So we have begun a good way to distribute a FLOSS project, we share ideas with people that have been thinking on it for a while now, including Walter Bender, Sebastian Silva, Edward Cherling David Farning, Tomeu Visozo and others (all sugar labs community ;)), i think in some way the people that is working on SugarLabs (http://sugarlabs.org/), share the same concepts about how to help in breaking status quo.
At the beginning we had questions about how to make Sugar deployments better, how to reach the broad community, because sugar it's not only aimed to developers, it's truth aim are teachers, students and parents, (iirc) David Farning proposed that the development of all SugarLabs should be oriented by teams, and thous we have deployment team.
http://sugarlabs.org/go/DeploymentTeam
But even more we were worried about how to facilitate the distribution and development of Sugar in the world and now we have Local Labs
http://sugarlabs.org/go/Local_Labs
Ok i want to get back to this post in another take..but for me this last link tries to achieve a worldwide, active and distributed community of practice, that being software developers, students, teachers, parents, industry, academics...entire cultures trying to work on resolving local and global issues related to enhance education.
At the beginning we had questions about how to make Sugar deployments better, how to reach the broad community, because sugar it's not only aimed to developers, it's truth aim are teachers, students and parents, (iirc) David Farning proposed that the development of all SugarLabs should be oriented by teams, and thous we have deployment team.
http://sugarlabs.org/go/DeploymentTeam
But even more we were worried about how to facilitate the distribution and development of Sugar in the world and now we have Local Labs
http://sugarlabs.org/go/Local_Labs
Ok i want to get back to this post in another take..but for me this last link tries to achieve a worldwide, active and distributed community of practice, that being software developers, students, teachers, parents, industry, academics...entire cultures trying to work on resolving local and global issues related to enhance education.
Thursday, May 29, 2008
Documents about sugar new procedures
This is only to document myself and try to extend the new procedures of sugar to the debian packaging for example. All this is documented in http://wiki.sugarlabs.org/go/Taxonomy.
(The taxonomy has been proposed proposed by Benjamin M. Schwartz)
What i really like about the naming is the biological and physics resemblances.
Sugar components
1 Sweet (the taste of sugar) : The abstract design of the interface: This is the design of the GUI with mockups in
http://wiki.laptop.org/go/Designs, it's independent of any other Sugar code.
2 Glucose (the fundamental, simple sugar used by all life forms): The base Sugar environment
Glucose doesn't include any of the activities it's just the minimal dependencies or packages that must be added to any standard linux distribution in order to get activities working.for example
xorg-server, xulrunner, squeakvm, rainbow, etc.
3 Fructose (the main sugar in fruit, which is how we're supposed to get our sugar): A set of demonstration activities.
Fructose are the packages for making sugar demonstrations, more exactly a set of activities impressive enough for potential sugar users or clients.
4 Sucrose ("table sugar", the kind you buy in the store. It consists of glucose and fructose, combined): The interface, plus a set of demonstration activities.
Glucose + Fructose = complete example Sugar environment, ready to be installed through a package manager.(yum, apt...).
5 Ribose(the sugar used by all lifeforms to control their hardware, in the form of RNA. It's important, but not sweet):The base Linux distribution being used by Sugar
It includes the XO kernels, OHM, any init-script customizations, etc. In synthesis all components necessary to boot the system, enough to install Glucose if it has not yet been installed.
6 Starch(es)(starch is composed of multiple sugars bonded together): A complete disk image for Sugar
Complete disk images for Sugar, as an example "glycogen" could be a development a starch used to produce Glucose. and "cellulose", an extremely stable starch or stable build.
As a side note please see this..:):
Lead acetate: An implementation of Sweet on Windows
(often called sugar of lead(http://en.wikipedia.org/wiki/Sugar_of_lead), lead acetate tastes better than sugar but isn't good for children)
"Lead acetate" is the proposed implementation of Sweet on Windows XP. Lead acetate may provide better performance than Glucose, but it is obsolete and toxic to young brains(http://www.healthychildrenproject.org/pdf/PPLEAD.pdf). It causes learning disability, behavioral tendencies toward violence, and even brain damage.
(The taxonomy has been proposed proposed by Benjamin M. Schwartz)
What i really like about the naming is the biological and physics resemblances.
Sugar components
1 Sweet (the taste of sugar) : The abstract design of the interface: This is the design of the GUI with mockups in
http://wiki.laptop.org/go/Designs, it's independent of any other Sugar code.
2 Glucose (the fundamental, simple sugar used by all life forms): The base Sugar environment
Glucose doesn't include any of the activities it's just the minimal dependencies or packages that must be added to any standard linux distribution in order to get activities working.for example
xorg-server, xulrunner, squeakvm, rainbow, etc.
3 Fructose (the main sugar in fruit, which is how we're supposed to get our sugar): A set of demonstration activities.
Fructose are the packages for making sugar demonstrations, more exactly a set of activities impressive enough for potential sugar users or clients.
4 Sucrose ("table sugar", the kind you buy in the store. It consists of glucose and fructose, combined): The interface, plus a set of demonstration activities.
Glucose + Fructose = complete example Sugar environment, ready to be installed through a package manager.(yum, apt...).
5 Ribose(the sugar used by all lifeforms to control their hardware, in the form of RNA. It's important, but not sweet):The base Linux distribution being used by Sugar
It includes the XO kernels, OHM, any init-script customizations, etc. In synthesis all components necessary to boot the system, enough to install Glucose if it has not yet been installed.
6 Starch(es)(starch is composed of multiple sugars bonded together): A complete disk image for Sugar
Complete disk images for Sugar, as an example "glycogen" could be a development a starch used to produce Glucose. and "cellulose", an extremely stable starch or stable build.
As a side note please see this..:):
Lead acetate: An implementation of Sweet on Windows
(often called sugar of lead(http://en.wikipedia.org/wiki/Sugar_of_lead), lead acetate tastes better than sugar but isn't good for children)
"Lead acetate" is the proposed implementation of Sweet on Windows XP. Lead acetate may provide better performance than Glucose, but it is obsolete and toxic to young brains(http://www.healthychildrenproject.org/pdf/PPLEAD.pdf). It causes learning disability, behavioral tendencies toward violence, and even brain damage.
Sunday, May 11, 2008
Mon Ange.
At last i know you, the waiting although accepted was biter..
My angel you are
My live you are
Now i look at the stars, you change my firmament, my sun and my planets spin around you.
What about death now, what about sadness now?
these constants dye behind your lips your hearth and your mind.
Don't go complex about things, don't go complex about anything..because the natural course
is like a river that even you can't control.
to GPM
My angel you are
My live you are
Now i look at the stars, you change my firmament, my sun and my planets spin around you.
What about death now, what about sadness now?
these constants dye behind your lips your hearth and your mind.
Don't go complex about things, don't go complex about anything..because the natural course
is like a river that even you can't control.
to GPM
Subscribe to:
Posts (Atom)
