Line 48: |
Line 48: |
| * Run only the block stack that has a 'start' block at the top. If there is no 'start' block, notify the user, but don't execute unnamed stacks. (TA itself should show the same behavior.) | | * Run only the block stack that has a 'start' block at the top. If there is no 'start' block, notify the user, but don't execute unnamed stacks. (TA itself should show the same behavior.) |
| * Assume the generated code will be run in GNOME, but keep the <code>running_sugar</code> flag, so it can be ported to Sugar later. | | * Assume the generated code will be run in GNOME, but keep the <code>running_sugar</code> flag, so it can be ported to Sugar later. |
| + | * The path to the TA installation must be in the environment variable <code>PYTHONPATH</code>. |
| + | * Boxes and actions are stored in a dictionary in order to allow for arbitrary names (e.g., names that start with a number or names that are read from the content of a box). |
| | | |
| === Pending === | | === Pending === |
Line 55: |
Line 57: |
| * Enable the user to control the speed of execution (e.g., by setting a global <code>step_time</code>)? ''deferred on 2013-06-14'' | | * Enable the user to control the speed of execution (e.g., by setting a global <code>step_time</code>)? ''deferred on 2013-06-14'' |
| ** 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? |
− | * How to automatically determine the path to the TA installation (e.g., for finding the plugins)? ''deferred on 2013-06-14''
| |
− | ** Either: check a list of standard paths.
| |
− | ** Or: expect it to be in the <code>PYTHONPATH</code>.
| |
− | ** Explain to the user what's wrong when the TA installation wasn't found.
| |
| * Should the status bar be shown when the exported code is run? | | * Should the status bar be shown when the exported code is run? |