10,505
edits
Changes
Jump to navigation
Jump to search
Line 5:
Line 5: − + − + − + − + − Another quote from Alan in the interview is: “people love change except for the change part.” Case in point, there has been grumbling on the sur list that Sugar keeps changing and as a consequence things break. While undoubted there are still plenty of bugs in Sugar (and even more in the older versions of the software deployed in, for example, Uruguay), the grass is not greener in the commercial software world. One need not look farther than the evolution of Android or iOS over the past 4 years to see vast amounts of change. As the Greek philosopher Heraclides said approximately 2300 years ago, "Change is the only constant." Get used to it.+ − I end with another quote from Alan: "Modern science was only invented 400 years ago, and it is a good example of what social thinking can do with a high threshold. Science requires a society because even people who are trying to be good thinkers love their own thoughts and theories — much of the debugging has to be done by others. But the whole system has to rise above our genetic approaches to being social to much more principled methods in order to make social thinking work."+ − + − === In the community ===+ + + − 5. Michael Perscheid from the University of Potsdam has been using Etoys as a game development platform with his students. [http://www.hpi.uni-potsdam.de/hirschfeld/projects/olpc/index.html Check out their work].+ − 6. The "github" experiment has been going well. Daniel Narvaez has been leading a team of reviewers through the reasonably efficient process of using [http://help.github.com/articles/using-pull-requests pull requests] and we have been able to clear up at least some of the backlog of features. But we still need more reviewers!+ − The basics for submitting a patch for review are:+ − # Fork the repo on the web UI − # Clone your fork − # Push the patches to your fork − # Make a pull request from the web UI − 7. Daniel has also been leading a discussion of how to move forward on both the integration of Javascript and HTML5 into Sugar and the migration of Sugar onto a more web-centric platform, e.g., chrome. Follow along on the [http://lists.sugarlabs.org/archive/sugar-devel/ devel list] (numerous threads).+ + + + + + + + + + +
→Sugar Digest
== Sugar Digest ==
== Sugar Digest ==
1. I have been on the road the past two weeks and consequently a bit behind in my communication. I don't recall if I announced beyond the sugar-devel list that Sugar Labs was selected to participate in Google Summer of Code. We have a great collection of project ideas and students are starting to engage in discussions. Please, if you are interested in being a mentor, sign up at [http://www.google-melange.com/gsoc/homepage/google/gsoc2013].
1. Sugar Labs has been given 8 slots for student interns for [http://www.google-melange.com/gsoc/homepage/google/gsoc2013 Google Summer of Code]. This means we'll be able to cover a lot ground this summer: we have some very strong proposals and a great mentoring team. The next step is for the mentors and the sugar-devel team to narrow the applicants down to a short list. Many thanks to everyone who has lent a hand so far and to Google for giving us this opportunity.
2. One of my trips was to Sydney, Australia, where I spent a few days with the team from OLPC AU. I really appreciate their approach: a tight coupling of educators, technology, documentation, marketing and business. They are in the process of expanding their program with a systematic, sustainable approach. A seriously good website [http://www.laptop.org.au/] and [http://www.one-education.org/] is part of their strategy for supporting teachers. More on that theme in the coming weeks.
2. The sugar-devel team has been really busy pushing new features for the next release and doing a general clean up of the code base. It is remarkable the current pace of activity, especially around the efforts to make HTML5/Javascript a first-class approach to Sugar activity development. You can follow the work on the [http://lists.sugarlabs.org/archive/sugar-devel/ devel list] or by reviewing (and submitting) patches on [http://github.com/sugarlabs github].
3. My other trip was to Finland, where I gave the keynote at the Finnish [http://www.itk.fi/2013/info/english Interactive Technology for Education (ITK) conference]. Jarmo Viteli was my host. There is the potential of intimidation, going to Finland, with its reputation for great schools, to talk about learning. But I found a receptive audience, appreciative of the fact that technology means more than fun and games. I began my talk with a reference to the former CEO of Nokia, who once described his role in his company not as a conductor in front of an orchestra, but as a member of a Jazz ensemble. I suggested that teachers are not conductors either. There was a real appreciation of the Sugar platform approach to reflection and collaboration. Also the FOSS culture in Finland seems alive and well -- the idea of children and teachers taking responsibility for their tools resonated with the audience. That responsibility and risk-taking are two complementary goals for learners. My talk should be posted on line soon.
3. I've been trying to contribute to the overall Sugar effort, but I tend to get distracted by Turtle Blocks (AKA Turtle Art). When I was visiting RIT a few weeks back, I was inspired to enhance the debugging features Turtle Blocks. I came up with a simple way to introduce the concept of break-points to the code. I had already introduced blocks to "hide" and "show" the program as it executes. And through the "rabbit" and "snail" buttons, the user can control the speed of program execution. What I did was to combine these two concepts. By introducing a "hide" block into your code, the code executes at full speed. Introducing a "show" block causes the program to run slowly and display the status of all of its "variables" as it runs. A subtle change, but what it allows one to do is to surround code you want to debug with a "show" and "hide" blocks. Small blocks of code can be examined while the larger program runs at full speed. Really helpful for debugging complex projects.
4. Right before I left for my two weeks of airplanes and hotel rooms, there was [http://techland.time.com/2013/04/02/an-interview-with-computing-pioneer-alan-kay an interview with Alan Kay] in ''Time Magazine''. A favorite quote he dusted off in the interview was “the music is not in the piano”. Nor is the music in the teacher. For a number of different reasons, Alan's interview is timely. As we see the proliferation of low-cost Android tablets into schools, it is important to ask if we are giving children toys or tools; and are we letting them play music or make music?
4. I am also working on another new feature, this one at the request of the teachers who have been using Butia in Uruguay. The idea is to be able to save a stack of blocks for reuse in multiple projects (instances). The way to do that currently is to open a project, copy the stack to the clipboard, and then paste it into a new project -- too clumsy to be used on a regular basis. The new feature allows users to save a stack to a custom palette. This palette is loaded with each instance of Turtle, so it means the stacks are available as if they were extensions of Turtle itself. It makes it even easier for end-user customization.
=== In the community ===
5. We'll be celebrating International Turtle Art Day (Día Mundial de TortugArte) in October. Our objectives are to:
* Promote the use of Turtle Art
* Share and promote best practices
* Celebrate projects for children and teachers
Details on how you can participate will be made available soon.
6. [http://www.youtube.com/watch?v=cxIDEuYyplc&feature=em-share_video_user How embarrassing].
=== Tech Talk ===
=== Tech Talk ===
7. Laura Vargas reports that [http://pe.sugarlabs.org/go/Proyecto_Piloto_Hexoquinasa/Instalar Hexoquinasa v0.9] (BETA2) has been released and is in the hands of the Ministry of Education of Perú, where it will undergo testing.
8. Daniel Narveaz reports that "the initial bits of the HTML activities work has landed. It should now be relatively easy to start writing an activity."
:(1) You will need the latest [http://sugarlabs.org/~buildbot/docs/build.html Sugar development environment].
:(2) Then open a shell and move to the source directory:
make shell
cd source
:(3) Create an activity based on a template:
volo create my-activity ./sugar-html-template
:(4) Install the activity for development as usual:
cd my-activity
python setup.py dev
:(5) To interact with the platform you will need to add the sugar-core-html library to your activity:
volo add -f ./sugar-html-core
=== Sugar Labs ===
=== Sugar Labs ===