Summer of Code/2013/Turtle Blocks Python export project: Difference between revisions
Marion Zepf (talk | contribs) add decision to convert named and unnamed stacks to functions |
Marion Zepf (talk | contribs) add section on pending design decisions; add a pending decision |
||
| Line 46: | Line 46: | ||
* 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>). | * 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>). | ||
=== Pending === | |||
The following design issues have yet to be decided: | |||
* When do we determine which block stacks are to be run? When we convert the code to Python or when the Python code is executed? | |||