Summer of Code/2013/Turtle Blocks Python export project: Difference between revisions

delay 'screen dimensions' (has low priority)
decision: show status bar when running exported code
Line 64: Line 64:
* All blocks (including the ones introduced by plugins) reference a <code>Primitive</code> object, which can be called to execute the block in TA, or transformed into a Python AST.
* All blocks (including the ones introduced by plugins) reference a <code>Primitive</code> object, which can be called to execute the block in TA, or transformed into a Python AST.
** Type conversion and other modification of the arguments of a block is done by ''slot wrappers''. A slot wrapper is a <code>Primitive</code> that is attached to the argument of another <code>Primitive</code>. Slot wrappers are called/ transformed before the <code>Primitive</code> itself.
** Type conversion and other modification of the arguments of a block is done by ''slot wrappers''. A slot wrapper is a <code>Primitive</code> that is attached to the argument of another <code>Primitive</code>. Slot wrappers are called/ transformed before the <code>Primitive</code> itself.
* The status bar may be shown when the exported code is run, as is necessary and appropriate during execution.


=== Pending ===
=== Pending ===
Line 75: Line 76:
* Enable the user to control the speed of execution (e.g., by setting a global <code>step_time</code>)?
* Enable the user to control the speed of execution (e.g., by setting a global <code>step_time</code>)?
** How to implement this? E.g., call a <code>wait(step_time)</code> function in between two steps?
** How to implement this? E.g., call a <code>wait(step_time)</code> function in between two steps?
* Should the status bar be shown when the exported code is run?