51
edits
Changes
Jump to navigation
Jump to search
Line 84:
Line 84: + + + + + + + + + + + + + + + +
Summer of Code/2013/Turtle Blocks Python export (view source)
Revision as of 11:05, 2 May 2013
, 11:05, 2 May 2013+impact on the Sugar labs community
=== Impact on the Sugar Labs community ===
=== Impact on the Sugar Labs community ===
''If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.''
''If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.''
Many Sugar activities allow exporting the user's creations as a sound file, a picture, a video, or a simple text file, which can then be imported into other activities. In the case of this project, the user can export their block program to Python code and view, edit, and run it in the Pippy and Terminal activities. Combining several activities to create a single piece of work inspires users' creativity. Moreover, it makes Sugar a coherent system, rather than just an arbitrary collection of activities. Users will view it as a tool kit that helps them realize their ideas, no matter which forms they take. This unlimitedness is an important aspect of Sugar's quality, and thus it ensures continued interest in Sugar in the future.
[[User:Walter|Walter Bender]], mentor of this project:<br/>
The primary goal of Turtle Blocks is to engage children in programming, specifically the joy of debugging. But also to give them a sense of empowerment over the tools that they use. Hence Turtle Blocks (as opposed to its sister project Turtle Art) exposes the learner to as much of the system as possible, through sensor blocks, Python blocks, etc. At the same time, Turtle Blocks is not an end in of itself. The further goal is to encourage the learners to move beyond block-based projects and get acquainted with the more expressive text-based languages. This project is an experiment to determine if providing a Python version of the block-based programming environment might provide a stepping stone to making this transition. Until we implement Sugar itself as a Turtle Blocks project, this experiment is a worthwhile bet at turning Sugar users into Sugar developers.
[[User:Rgs|Raúl Gutiérrez Segalés]], Turtle Art contributor:<br/>
In my mind, the big take away here is that we'll enable portability of
Turtle Art projects. Being able to translate TA internal
code into external languages (initially Python, eventually Javascript
perhaps, or others) will allow this fundamental learning activity to
reach other platforms and a much broader audience. The question we've
got in front of us is not if Sugar or Turtle Art belong in the Cloud;
it's just how fast can we get there.<br/>
This project is a key step towards our goal of getting Sugar/Turtle
Art onto more hands.
=== Sugar pilot deployment ===
=== Sugar pilot deployment ===