Summer of Code/2013/Turtle Blocks Python export project - Revision history

Marion Zepf: highlight link to final report

2013-10-07T18:18:06Z

highlight link to final report

← Older revision		Revision as of 14:18, 7 October 2013
Line 3:		Line 3:
	The mentors for this project are [[User:Walter\|Walter Bender]] and [http://wiki.laptop.org/go/User:Claudia_Urrea Claudia Urrea].		The mentors for this project are [[User:Walter\|Walter Bender]] and [http://wiki.laptop.org/go/User:Claudia_Urrea Claudia Urrea].

	The summer is over, so I have written a [[Media:Final_Report_on_Turtle_Blocks_Python_export.pdf\|final report]] on my project. It gives an overview of the task, my ideas and their implementation, as well as the final status of the project.		The summer is over, so I have written a '''[[Media:Final_Report_on_Turtle_Blocks_Python_export.pdf\|final report]]''' on my project. It gives an overview of the task, my ideas and their implementation, as well as the final status of the project.

	== Repositories ==		== Repositories ==

Marion Zepf: fix link to final report

2013-10-07T18:15:33Z

fix link to final report

← Older revision		Revision as of 14:15, 7 October 2013
Line 3:		Line 3:
	The mentors for this project are [[User:Walter\|Walter Bender]] and [http://wiki.laptop.org/go/User:Claudia_Urrea Claudia Urrea].		The mentors for this project are [[User:Walter\|Walter Bender]] and [http://wiki.laptop.org/go/User:Claudia_Urrea Claudia Urrea].

	The summer is over, so I have written a [[~~File~~:Final_Report_on_Turtle_Blocks_Python_export.pdf\|final report]] on my project. It gives an overview of the task, my ideas and their implementation, as well as the final status of the project.		The summer is over, so I have written a [[Media:Final_Report_on_Turtle_Blocks_Python_export.pdf\|final report]] on my project. It gives an overview of the task, my ideas and their implementation, as well as the final status of the project.

	== Repositories ==		== Repositories ==

Marion Zepf: link to final report

2013-10-07T18:14:28Z

link to final report

← Older revision		Revision as of 14:14, 7 October 2013
Line 2:		Line 2:

	The mentors for this project are [[User:Walter\|Walter Bender]] and [http://wiki.laptop.org/go/User:Claudia_Urrea Claudia Urrea].		The mentors for this project are [[User:Walter\|Walter Bender]] and [http://wiki.laptop.org/go/User:Claudia_Urrea Claudia Urrea].

			The summer is over, so I have written a [[File:Final_Report_on_Turtle_Blocks_Python_export.pdf\|final report]] on my project. It gives an overview of the task, my ideas and their implementation, as well as the final status of the project.

	== Repositories ==		== Repositories ==

Marion Zepf: update timeline

2013-09-24T13:15:34Z

update timeline

← Older revision		Revision as of 09:15, 24 September 2013
Line 44:		Line 44:
	*** Introduce strong typing to <code>Primitive</code>s.		*** Introduce strong typing to <code>Primitive</code>s.
	*** Pass argument blocks to the functor as <code>Primitive</code> objects, not as ASTs or return values of a function call.		*** Pass argument blocks to the functor as <code>Primitive</code> objects, not as ASTs or return values of a function call.
			** August 26 – September 1 (1 week)
			*** Introduce disjunctions of <code>Type</code>s, <code>ArgSlot</code>s, argument lists, and <code>Primitive</code>s.
			*** Adjust the export functionality to the type system.
			*** Start re-writing 'old' <code>Primitive</code>s to make use of the new type system.
			*** Write new documentation about how to create a new block, including creating new <code>Primitive</code>s.
			*** Comments from the 'Extra options' palette: This is especially difficult because Python's <code>ast</code> module does not support comments natively.
			** September 2 – September 8 (1 week)
	*** Screen dimensions from the 'Presentation templates' palette		*** Screen dimensions from the 'Presentation templates' palette
	*** Runtime control (e.g., exit, suspension) from the 'Flow operators' palette		*** Runtime control (e.g., exit, suspension) from the 'Flow operators' palette
	** August 26 – September 1 (1 week)
	*** Heaps from the 'Extra options' palette		*** Heaps from the 'Extra options' palette
			** September 9 – September 15 (1 week)
	*** External functions (chr, int, mathematical function, tamyblock.py) from the 'Extra options' palette		*** External functions (chr, int, mathematical function, tamyblock.py) from the 'Extra options' palette
	*** Comments from the 'Extra options' palette: This is especially difficult because Python's <code>ast</code> module does not support comments natively.
	** September 2 – September 8 (1 week)
	*** Events and user input from the 'Sensors' palette		*** Events and user input from the 'Sensors' palette
	*** Sounds and sprites from the 'Media' palette		*** Sounds and sprites from the 'Media' palette
	*** Presentation templates from the 'Presentation templates' palette
	** September 9 – September 15 (1 week)
	*** Multiple turtles and custom turtle shells from the 'Extra options' palette
	*** Display management (hide/ show blocks, toggle full screen) from the 'Presentation templates' palette		*** Display management (hide/ show blocks, toggle full screen) from the 'Presentation templates' palette
	*** Printing and loading blocks and palettes from the 'Extra options' palette
	* September 16 – September 23 (1 week): Test exporting different kinds of blocks in combination. Fix the last bugs. Clean up.		* September 16 – September 23 (1 week): Test exporting different kinds of blocks in combination. Fix the last bugs. Clean up.

Marion Zepf: remove the footnotes in the timeline

2013-08-23T15:15:13Z

remove the footnotes in the timeline

Marion Zepf: describe the type-system branch in the gitorious repo

2013-08-23T15:12:49Z

describe the type-system branch in the gitorious repo

← Older revision		Revision as of 11:12, 23 August 2013
Line 5:		Line 5:
	== Repositories ==		== Repositories ==

	I develop my project in a repository called [https://git.sugarlabs.org/~mzepf/gsoc-python-export gsoc-python-export] in the SugarLabs Gitorious system. If you would like to have a look at my latest progress, check out the <code>primitive-class</code> branch. (The <code>master</code> branch is only used for submitting merge requests to [https://git.sugarlabs.org/turtleart/mainline the main TurtleArt repository].)		=== gsoc-python-export on gitorious ===

			I develop my project in a repository called [https://git.sugarlabs.org/~mzepf/gsoc-python-export gsoc-python-export] in the SugarLabs Gitorious system. If you would like to have a look at my latest progress, check out the <code>primitive-class</code> branch. It contains the latest '''stable''', i.e. working, version of TurtleArt and the export tool.

			The branch <code>type-system</code> contains some work-in-progress on the type system for <code>Primitive</code> objects that I am currently introducing. It's a major change that affects how blocks are executed and exported to ASTs. Therefore, this branch should be considered '''unstable''', i.e. there is no guarantee that things will work or even that you'll get useful error messages. As soon as the type system is fully established and everything works again, this branch will be merged back into <code>primitive-class</code>.

			The <code>master</code> branch is only used for submitting merge requests to [https://git.sugarlabs.org/turtleart/mainline the main TurtleArt repository].

			=== ta-python-export-dev on github ===

	Design documents, sample code, etc. go into [https://github.com/outofthecave/ta-python-export-dev ta-python-export-dev] on GitHub. There, the <code>master</code> branch is the most recent one.		Design documents, sample code, etc. go into [https://github.com/outofthecave/ta-python-export-dev ta-python-export-dev] on GitHub. There, the <code>master</code> branch is the most recent one.

Marion Zepf: explain branches in the two repositories

2013-08-18T11:57:59Z

explain branches in the two repositories

← Older revision		Revision as of 07:57, 18 August 2013
Line 5:		Line 5:
	== Repositories ==		== Repositories ==

	I develop my project in a ~~branch~~ called [https://git.sugarlabs.org/~mzepf/gsoc-python-export gsoc-python-export] on Gitorious. Design documents, sample code, etc. go into [https://github.com/outofthecave/ta-python-export-dev ta-python-export-dev] on GitHub.		I develop my project in a repository called [https://git.sugarlabs.org/~mzepf/gsoc-python-export gsoc-python-export] in the SugarLabs Gitorious system. If you would like to have a look at my latest progress, check out the <code>primitive-class</code> branch. (The <code>master</code> branch is only used for submitting merge requests to [https://git.sugarlabs.org/turtleart/mainline the main TurtleArt repository].)

			Design documents, sample code, etc. go into [https://github.com/outofthecave/ta-python-export-dev ta-python-export-dev] on GitHub. There, the <code>master</code> branch is the most recent one.

	== Timeline ==		== Timeline ==

	The following timeline ~~will be~~ modified as the project evolves.		The following timeline is being modified as the project evolves.

	* June 17 – June 30 (2 weeks): Determine what code needs to be shared by Turtle Blocks and the exported code. Restructure the modules to isolate this part, so it can easily be imported. Only cover the modules that are necessary to run blocks from the 'Turtle', 'Pen', and 'Pen colors' palettes. Deal with the other modules when implementing the corresponding blocks.		* June 17 – June 30 (2 weeks): Determine what code needs to be shared by Turtle Blocks and the exported code. Restructure the modules to isolate this part, so it can easily be imported. Only cover the modules that are necessary to run blocks from the 'Turtle', 'Pen', and 'Pen colors' palettes. Deal with the other modules when implementing the corresponding blocks.

Marion Zepf: timeline: squeeze in two new awesome ideas

2013-08-16T14:46:52Z

timeline: squeeze in two new awesome ideas

← Older revision		Revision as of 10:46, 16 August 2013
Line 31:		Line 31:
	*** Action stacks (functions) from the 'Action stacks' palette		*** Action stacks (functions) from the 'Action stacks' palette
	** August 19 – August 25 (1 week)		** August 19 – August 25 (1 week)
	*** Write a tutorial on how to define a Primitive for a new block, so other TA (plugin) developers can make their blocks exportable.		*** Write a tutorial on how to define a <code>Primitive</code> for a new block, so other TA (plugin) developers can make their blocks exportable.
			*** Introduce strong typing to <code>Primitive</code>s.
			*** Pass argument blocks to the functor as <code>Primitive</code> objects, not as ASTs or return values of a function call.
	*** Screen dimensions from the 'Presentation templates' palette<ref name="requires-add-imports" group="note" />		*** Screen dimensions from the 'Presentation templates' palette<ref name="requires-add-imports" group="note" />
	*** Heaps from the 'Extra options' palette
	*** Runtime control (e.g., exit, suspension) from the 'Flow operators' palette		*** Runtime control (e.g., exit, suspension) from the 'Flow operators' palette
	** August 26 – September 1 (1 week)		** August 26 – September 1 (1 week)
			*** Heaps from the 'Extra options' palette
	*** External functions (chr, int, mathematical function, tamyblock.py) from the 'Extra options' palette<ref name="requires-add-imports" group="note" />		*** External functions (chr, int, mathematical function, tamyblock.py) from the 'Extra options' palette<ref name="requires-add-imports" group="note" />
	*** Comments from the 'Extra options' palette: This is especially difficult because Python's <code>ast</code> module does not support comments natively.		*** Comments from the 'Extra options' palette: This is especially difficult because Python's <code>ast</code> module does not support comments natively.

Marion Zepf: timeline: add tutorial on defining Prims; move external functions down a week

2013-08-16T13:51:32Z

timeline: add tutorial on defining Prims; move external functions down a week

← Older revision		Revision as of 09:51, 16 August 2013
Line 31:		Line 31:
	*** Action stacks (functions) from the 'Action stacks' palette		*** Action stacks (functions) from the 'Action stacks' palette
	** August 19 – August 25 (1 week)		** August 19 – August 25 (1 week)
			*** Write a tutorial on how to define a Primitive for a new block, so other TA (plugin) developers can make their blocks exportable.
	*** Screen dimensions from the 'Presentation templates' palette<ref name="requires-add-imports" group="note" />		*** Screen dimensions from the 'Presentation templates' palette<ref name="requires-add-imports" group="note" />
	*** Heaps from the 'Extra options' palette		*** Heaps from the 'Extra options' palette
	*** Runtime control (e.g., exit, suspension) from the 'Flow operators' palette		*** Runtime control (e.g., exit, suspension) from the 'Flow operators' palette
			** August 26 – September 1 (1 week)
	*** External functions (chr, int, mathematical function, tamyblock.py) from the 'Extra options' palette<ref name="requires-add-imports" group="note" />		*** External functions (chr, int, mathematical function, tamyblock.py) from the 'Extra options' palette<ref name="requires-add-imports" group="note" />
	** August 26 – September 1 (1 week)
	*** Comments from the 'Extra options' palette: This is especially difficult because Python's <code>ast</code> module does not support comments natively.		*** Comments from the 'Extra options' palette: This is especially difficult because Python's <code>ast</code> module does not support comments natively.
	** September 2 – September 8 (1 week)		** September 2 – September 8 (1 week)

Marion Zepf: decision: show status bar when running exported code

2013-08-02T20:26:06Z

decision: show status bar when running exported code

← Older revision		Revision as of 16:26, 2 August 2013
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?

← Older revision		Revision as of 11:15, 23 August 2013
Line 44:		Line 44:
	*** Introduce strong typing to <code>Primitive</code>s.		*** Introduce strong typing to <code>Primitive</code>s.
	*** Pass argument blocks to the functor as <code>Primitive</code> objects, not as ASTs or return values of a function call.		*** Pass argument blocks to the functor as <code>Primitive</code> objects, not as ASTs or return values of a function call.
	*** Screen dimensions from the 'Presentation templates' palette~~<ref name="requires-add-imports" group="note" />~~		*** Screen dimensions from the 'Presentation templates' palette
	*** Runtime control (e.g., exit, suspension) from the 'Flow operators' palette		*** Runtime control (e.g., exit, suspension) from the 'Flow operators' palette
	** August 26 – September 1 (1 week)		** August 26 – September 1 (1 week)
	*** Heaps from the 'Extra options' palette		*** Heaps from the 'Extra options' palette
	*** External functions (chr, int, mathematical function, tamyblock.py) from the 'Extra options' palette~~<ref name="requires-add-imports" group="note" />~~		*** External functions (chr, int, mathematical function, tamyblock.py) from the 'Extra options' palette
	*** Comments from the 'Extra options' palette: This is especially difficult because Python's <code>ast</code> module does not support comments natively.		*** Comments from the 'Extra options' palette: This is especially difficult because Python's <code>ast</code> module does not support comments natively.
	** September 2 – September 8 (1 week)		** September 2 – September 8 (1 week)
	*** Events and user input from the 'Sensors' palette~~<ref name="requires-add-imports" group="note" />~~		*** Events and user input from the 'Sensors' palette
	*** Sounds and sprites from the 'Media' palette		*** Sounds and sprites from the 'Media' palette
	*** Presentation templates from the 'Presentation templates' palette~~<ref name="requires-add-imports" group="note" />~~		*** Presentation templates from the 'Presentation templates' palette
	** September 9 – September 15 (1 week)		** September 9 – September 15 (1 week)
	*** Multiple turtles and custom turtle shells from the 'Extra options' palette~~<ref name="requires-add-imports" group="note" />~~		*** Multiple turtles and custom turtle shells from the 'Extra options' palette
	*** Display management (hide/ show blocks, toggle full screen) from the 'Presentation templates' palette		*** Display management (hide/ show blocks, toggle full screen) from the 'Presentation templates' palette
	*** Printing and loading blocks and palettes from the 'Extra options' palette<ref name="requires-add-imports" group="note" /><!-- These are very specific to Turtle Blocks. We need further discussion how this should look in the output of the exported Python code. --><!-- TODO report results of discussion -->		*** Printing and loading blocks and palettes from the 'Extra options' palette
	* September 16 – September 23 (1 week): Test exporting different kinds of blocks in combination. Fix the last bugs. Clean up.		* September 16 – September 23 (1 week): Test exporting different kinds of blocks in combination. Fix the last bugs. Clean up.

	~~'''Notes'''~~
	~~<references group="note">~~
	~~<ref name="requires-add-imports">This may require importing additional modules from Turtle Blocks.</ref>~~
	~~</references>~~

	== Decisions ==		== Decisions ==