Summer of Code/2013/Turtle Blocks Python export project: Difference between revisions
Marion Zepf (talk | contribs) design decision on which graphical elements to include in the output |
Marion Zepf (talk | contribs) add decision to convert named and unnamed stacks to functions |
||
| Line 1: | Line 1: | ||
This page tracks the progress of [[User:Marion Zepf|Marion Zepf]]'s GSoC project, "Turtle Blocks Python export." An abstract and a motivational statement can be found on the [[Summer of Code/2013/Turtle Blocks Python export|project proposal]] page, along with other details. | This page tracks the progress of [[User:Marion Zepf|Marion Zepf]]'s GSoC project, "Turtle Blocks Python export." An abstract and a motivational statement can be found on the [[Summer of Code/2013/Turtle Blocks Python export|project proposal]] page, along with other details. | ||
The mentors for this project are [[User:Walter|Walter Bender]] and Claudia Urrea. | The mentors for this project are [[User:Walter|Walter Bender]] and [http://wiki.laptop.org/go/User:Claudia_Urrea Claudia Urrea]. | ||
== Repositories == | == Repositories == | ||
| Line 45: | Line 45: | ||
* The generated Python code will setup a window without menus and palettes. It will only be a plain canvas. Turtles will be visible with their (default or custom) sprites because this is the only way to make sprites move in TA. | * The generated Python code will setup a window without menus and palettes. It will only be a plain canvas. Turtles will be visible with their (default or custom) sprites because this is the only way to make sprites move in TA. | ||
* Code in named stacks will be put into functions with the same name. Blocks appended to the 'start' block will be put into a function called <code>start()</code>. Unnamed stacks will also be put into extra functions with auto-generated names (e.g., <code>unnamed_stack_1()</code>). | |||