Planet Sugar is a collection of personal blogs by Sugar Labs contributors. Sugar Labs is a world-wide organization of passionate people working together to solve the same problem: giving everyone an opportunity to learn to learn. Our community members write about what excites them about learning, Sugar, and the Sugar community. In the spirit of free software, we share and criticize—that is how we learn and improve and encourage participation by newcomers. Enjoy and join the conversation.
Hace un mes leí un artículo brillante de Katie Cunningham donde ella describía parte de su estrategia para realizar talleres de Python. Dedicándome últimamente con mucha pasión a esta actividad, pero con grupos objetivo diferentes (yo enseño a niños), tomé nota de sus experiencias y sobretodo me pareció que el uso que daba a la herramienta Git era brillante.
Katie sugiere que gran parte del tiempo en un taller de Python se “pierde” mientras los aprendices copian ejercicios. Git le permitiría empezar la sesión con una versión simple de un programa y luego pasar a la siguiente “en un paso”, sin copiar, de esta manera invirtiendo el tiempo del aprendiz más bien en modificar cada versión subsiguiente y así comprender el funcionamiento del mismo, en vez de en la mecánica de escribir el programa en primer lugar.
Sin embargo para mí, el uso de Git en la terminal es todavía demasiado obtuso para poder enseñarlo efectivamente a niños. Los conceptos en sí son simples, pero la abstracción se me hace demasiada. Por eso es que empecé el desarrollo de una actividad de Sugar que facilite visualizar el historial de un proyecto, y en general trabajar con git. Mi principal inspiración es “Gitg” para gnome, pero me interesa realizar un trabajo de simplificación de los flujos de trabajo que se necesitan en el contexto de un taller de Python, como los que describe Katie.
De momento es solo un prototipo pero ya sirve para navegar el historial usando una barra de tiempo:
Comparto anticipadamente para recibir comentarios e ideas.
Estoy documentando el proyecto en nuestra wiki.
Este es el resumen de actividad para la comunidad Laboratorios Azúcar.
Éste se compone de una agregación de fuentes como nuestro gestor de tareas, Wiki, y blogs.
Puedes publicar un comentario o participar de diferentes formas.
Si tienes una noticia o una fuente que deberíamos incluir (como un blog, etc), avísanos a todos(arroba)somosazucar.org
Hubo 85 eventos esta semana.
Larry Cuban’s post provides a really nice, concise history of Logo and coding efforts. As he notes at the end, the Papert effort can be inspiring and instructional, as it has been for our Sugar Labs effort, but we also hit a wall and have suspended the program, as Cuban would expect . : )
We are getting ready to set up the annual community summit (2014 will be the sixth such summit) and we've made a significant change to the way we organize it. This year, we will be running an online and an in-person event. The summit will be held October 17 to 19, 2014. You can either be here with us in-person, or be online and attend! Let us know what your thinking is at this time, so we can organize accordingly.
Mark your calendar!
This will be a online-and-offline event with opportunities to attend and present both online from the comfort fo your home, or in person in San Francisco. More details coming soon.
This week was spent mostly on writing tests for Read. The major issue we were facing is that, we couldn’t open files in Read activity using the objectchooser. So, Gonzalo sent a novel way of doing the same use case. in a different way and it worked perfectly. Here is the link of the conversation on the mailing list.
I have successfully written tests for Read and also added some helper functions in uitree.py of sugar-toolkit-gtk3 that are required for writing tests for the activities.
Next week, my focus will be work on the writing tests for imageviewer using the same approach as used in Read activity. After, the same is done and time is left then I will also continue on the work where I left off for Browse activity.
Sugar Labs supports a smarter (computing) culture. I think we should see if the innovation lab wants / needs some XOs. Or maybe we can build Rich Rice’s XO kiosk.
Work done this week-
1. Read wasn’t opening correctly and gave an error in readactivity.py which was solved by gonzalo. I helped a little in debugging and testing the patch.
2. The files being displayed in objectchooser were incorrect. So, informed gonzalo and the patch for it was submitted by him. Pinched in for testing and debugging of the error.
3. Next problem was to access the path of the documents folder, which is not generic in sugar. So, again gonzalo pointed me the function of get_documents_path() in jarabe/activity/model.py. That solved the document path issue.
4. While progressing on writing tests for Read, I stumbled across a GError while running the tests, after finding more about them, I found that Read were running on some Dbus settings X and as soon as the objectchooser is loaded, the dbus settings change to something else(They take the dbus settings of the journal). Leading, to the pyatspi(the main library used to testing) to infer that the read activity, process has hung up. I haven’t been able to find anything substantial that could solve the given problem.
6. Worked a little on documentation and the testing guide of the tests.
1. Work on Browse and Chat
2. Complete the testing guide and documentation of individual activities.
Problems in writing tests for some activities
1. TurtleArt (Reason : ta is gtk2 and tests currently run on gtk3.So, the conflict lead to the unsuccessful attempt at writing the tests for them)
2. Read and Imageviewer (Reason : GError : timeout in dbind, leading the pyatspi to assume the activity to be hung) Only, the basic tests for them have been possible.
Happy 6th Birthday Sugar Labs
1. I just got back from Turtle Art Day in Kathmandu, Nepal. OLE Nepal helped organize a 2-day workshop with 70+ children from four schools. Many thanks to Martin Dluhos, Basanta Shrestha, Subir Pradhanang, Rabi Karmacharya, Bernie Innocenti, Nick Dorian, and Adam Holt, all of whom contributed to the event.
It was not a surprise that children in Nepal are like children everywhere else: they take to programming like ducks to water. We began by taking the children in small groups to learn some basics about controlling the turtle: one child plays the role of turtle, one holds the pen (a piece of chalk) and the rest, in a circle, instruct the “turtle” how to draw a square. They need to be very precise with their instructions: if they just say “forward” without saying how far forward, the turtle keeps walking. If they say “right”, without saying how far to turn, the turtle keeps spinning. After they draw a square, I ask them to draw a triangle then they are ready to start with Turtle Art. I’ve posted a few of the chalk drawings in the wiki: simple ones from my session to more elaborate from those working with another one of the mentors.
After working with chalk, we went to the computers. On a laptop connected to a projector, I introduced Turtle Blocks, and again ask for a square. I show them that they can snap together blocks, e.g., forward 100, right 90; showed them the repeat block; and then I show them how to use the start block to run their program with the rabbit or snail (fast or slow). Over time, I introduced the pen and let them explore colors for awhile. Next, I introduce action blocks: make an action for drawing a square and then call that action inside of a repeat block followed by right 45, and you get a pretty cool pattern. This was followed by more open-ended exploration. I introduced a few more ideas, such as using “set color to heading” (the color is determined by the direction the turtle is heading); “set color = color + 1″ to increment the color; and “set color = time” to make the color slowly change over time. I also introduced a few other blocks, such as show, speak, and random. Finally, I introduced boxes. For this, I use a physical box: I ask the children to put a number (written on paper) in the box; then I ask them what number is in the box. I ask them to take the number in the box and add 1 to it. Again I ask them what number is in the box. I repeat this until they get used to it; then I show them the same thing using Turtle. The example program I write with them is to go forward by the amount in the box, turn right, and add 10 to the number in the box. I asked them what they think will happen and then show them that it makes a spiral. When they run it with the “snail”, they can see the number in the box as the program runs. Another block I explicitly introduced was the “show” block. We programmed an animation with “show image”, “wait 1″, “show image”, “wait 1″, … They recorded dance steps using the Sugar Record activity and used those images in their Turtle projects. As often as possible, we tried to have a child show their work to the entire group. At the end of the second day, we had a table set up for an exhibition; we had to keep adding more tables as more and more children wanted to show off their projects.
We originally planned on break-out sessions on Day Two, but we had a technical glitch on Day One, that slowed things down quite a bit. The children were running Sugar 0.82 on XO-1 laptops, which is nearly six-years old. They had them connected to the mesh network, which cannot scale properly to 70+ machines. The result was a lot of frozen machines. It took most of the day to figure out what was wrong. Once we turned off the radios, everything worked great. I also had to spin a stripped down version of Turtle Art, since a number of dependencies I use, such as some Python 2.7 features, were unavailable on 0.82.
We did have one break-out session for robotics. I brought a Butia to Nepal and I wrote the typical program with the kids to have the Butia go forward until it got to the edge of the circle (everyone was sitting in a circle on the floor); whomever the Butia approached had to push a button so that the Butia would spin and then go in another direction. We then added a few embellishments: the Butia would say “ouch” or “that tickles” when the button was pushed; and we had it take a picture of the child who pushed the button. We saved the files so we could use them to make an animation in Turtle Art.
Of note: One child approached me to say he is teaching himself to program Python. I showed him how to export Python from his Turtle Art projects. I’ll be curious how he uses that feature. I am making a new set to Turtle Cards to demonstrate the steps we took in explaining Turtle to the children.
2. While I was in Kathmandu, I had a chance to meet with the Nepali FOSS community, thanks to Shankar Pokharel, Ankur Sharma, and Subir Pradhanang. We had a nice talk about the challenges and opportunities facing FOSS in Nepal.
3. Just before my trip to Nepal, I was in Mexico DF attending Aldea Digital. The central plaza in Centro Historico is turned into the world’s largest free Internet cafe for two weeks. I gave a lecture about Sugar and ran an impromptu Turtle Art session. (We installed Sugar in a VM on twenty Windows 8 machines and ran a session.) I also had a chance to meet Ian, the 9-month old baby of Carla Gomez: a future Turtle Artist.
In the Community
4. Mike Dawson, formally of OLPC Afghanistan, wrote a nice commentary on the Keepod in which he mentions Sugar on a Stick.
5. Google Summer of Code begins on the 19th of May. We’ll be meeting every week in IRC on Fridays at 2PM EST.
6. There is still time to enter the Sugar Background Image Contest.
7. Daniel Narvaez has been building F20 images for XO: The XO-1 image boots into Sugar (latest from git) and wifi works. He has also built XO-4 images.
9. Please help us with testing of Sugar 102.
10. Please visit our planet.
While we are no longer meeting as the OLPC Learning Club (I have a personal and club update nearly ready to post), there are two Scratch Day celebrations coming up in the D.C. area on Saturday May 17, 2014 that were jumpstarted by club members.
Jeff Elkner, who hosted many club meetings at the Arlington (Virginia) Career Center, has engaged with the staff of Hoffman-Boston Elementary School in Arlington to help them stage their first Scratch Day. They are calling it the All Star Computer Programming Party. I’ve enlisted Michael Badger, author of the new book Scratch 2.0: A Beginner’s Guide (Second Edition), to make a guest appearance. The school’s STEM team will showcase a number of other fun coding tools. Dell Computer and George Mason University are also sponsoring. For more information, visit this link:
Hoffman-Boston Elementary School All Star Computer Programming Party
In D.C., our amazing friend Leshell Hatley of Uplift, Inc., is doing her third Scratch Day, moving this year to Howard University’s Computer Learning & Design Center (CLDC). Kevin Cole, who has hosted many, many club meetings at Gallaudet University, helped Leshell get her first event going. Uplift, Inc. is a 501c3 nonprofit immersing students in STEAM and CS education. For more on Uplift’s Scratch Day, visit this link:
Uplift / Howard University Scratch Day
Both events are open to the public, but the Uplift / Howard University Scratch Day asks for an RSVP.
While Scratch 1.4 is still in wide use, many are adopting the new web-based version, Scratch 2.0, which has been completely rebuilt from “scratch” and substantially enhanced. Just in the last few weeks, support for the Lego WeDo robotics kit was added to Scratch 2.0 and a touch tablet version called ScratchJr. was announced. Exciting times lie ahead for Scratchers of all ages!
Tinnitus creates discomfort to people suffering from it so they desperately search for ways to get rid of it. Thomas Coleman, the developer of http://www.prweb.com/releases/TinnitusMiracle/review/prweb11452569.htm is actually a sufferer of chronic disease. This actually means to say that he himself is knows how this cure works. Suffering from this ailment for over 14 years absolutely made him dedicated in finding the solution to his concern. Fortunate for those people who have the same condition Mr. Coleman decided to share his solution to everyone who wants to get rid of it for good. He did and he wants everyone who is suffering from it to be as healthy as he is now.
Tinnitus Miracle is a system developed by Thomas to be followed religiously in order to eliminate the buzzing, hissing and all those noise you hear on your ear. This is an entire system which guarantees effect within 7 days and if you are diligent enough to abide to each word written to change your lifestyle, you will not only say goodbye to your Tinnitus but to your unhealthy way of living for good. If you have this concern, you would know that whatever your doctor gives you is only something to temporary lessen the discomfort but the noise will come back and you are bound by the discomfort until you decide to change everything. The decision is yours to make. You are the only one who can decide whether you tolerate the discomfort or say goodbye to it, permanently.
<iframe allowfullscreen="allowfullscreen" frameborder="0" height="315" src="http://www.youtube.com/embed/vgh6lu6HUfI" width="560"></iframe>