Summer of Code/2015/Pointy - Revision history

Andrej T: resized image

2015-03-27T11:56:02Z

resized image

← Older revision		Revision as of 07:56, 27 March 2015
Line 18:		Line 18:
	===About your project===		===About your project===

	[[File:Pointy-with-face.png\|framed]]		[[File:Pointy-with-face.png\|framed\|422x422px]]

	* '''What is the name of your project?'''		* '''What is the name of your project?'''

Andrej T: added project picture

2015-03-27T11:55:23Z

added project picture

← Older revision		Revision as of 07:55, 27 March 2015
Line 17:		Line 17:

	===About your project===		===About your project===

			[[File:Pointy-with-face.png\|framed]]

	* '''What is the name of your project?'''		* '''What is the name of your project?'''

Andrej T: more info about me and the community

2015-03-27T11:51:14Z

more info about me and the community

← Older revision		Revision as of 07:51, 27 March 2015
Line 128:		Line 128:

	* '''What will you do if you get stuck on your project and your mentor isn't around?'''		* '''What will you do if you get stuck on your project and your mentor isn't around?'''

			I'm familiar with web development and googling for solutions; I've been freelancing for 2 years so I'm used to not having someone to ping IRL or them not being around at the moment.

	* '''How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?'''		* '''How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?'''

			Other than informing my mentor regarding the progress of the project every week, over email, I'll try to summarize what's been done in a monthly mailing list post. I'll be online on IRC most of the time, too.

	===Miscellaneous===		===Miscellaneous===

Andrej T: added project impact

2015-03-27T11:45:54Z

added project impact

@@ Line 112: / Line 112: @@
 * '''If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.'''
 * '''What will you do if you get stuck on your project and your mentor isn't around?'''
 * '''How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?'''

Andrej T at 11:34, 27 March 2015

2015-03-27T11:34:43Z

← Older revision		Revision as of 07:34, 27 March 2015
Line 98:		Line 98:

	* '''Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''		* '''Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''

			I made a demo of the game: http://whoeverest.github.io/pointy-demo/ (or alternatively a [https://www.youtube.com/watch?v=j8JfiFtfkP4 video])

	For the past year I've been developing games for [https://www.gambit.com/ gambit.com] as a part of a small team. I worked on several major features, including writing Dominoes and Rock-Paper-Scissors from scratch (both backend and frontend) and writing a physics engine for billiards (based on computational pool papers, not live yet).		For the past year I've been developing games for [https://www.gambit.com/ gambit.com] as a part of a small team. I worked on several major features, including writing Dominoes and Rock-Paper-Scissors from scratch (both backend and frontend) and writing a physics engine for billiards (based on computational pool papers, not live yet).

	~~I made a demo of the game: http://whoeverest.github.io/pointy-demo/ (or alternatively a [https://www.youtube.com/watch?v=j8JfiFtfkP4 video])~~

	3 years ago I successfully completed my first GSOC project for Orange, a data-mining software. I wrote widgets that read images, then processed them and made their pixel data available for further statistical analysis by the rest of the software.		3 years ago I successfully completed my first GSOC project for Orange, a data-mining software. I wrote widgets that read images, then processed them and made their pixel data available for further statistical analysis by the rest of the software.

Andrej T: changed the format of the second semester to table

2015-03-27T11:33:22Z

changed the format of the second semester to table

← Older revision		Revision as of 07:33, 27 March 2015
Line 76:		Line 76:
	Midterm		Midterm

	June 28 - July 5: Finishing up the level editor		{\| class="wikitable"
	July 6 - July 12: Web service for sharing levels (node.js)		\|-
	July 13 - July 19: Polishing the game and level editor		! Start !! End !! Description
	July 20 - July 26: Polishing the game and level editor		\|-
	July 27 - August 2: Integrating with Sugar, making the game an activity		\| June 28 \|\| July 5 \|\| Finishing up the level editor
	August 3 - August 9: Writing documentation, "How to play", "How to install", "How to deploy"		\|-
	August 10 - August 16: Setting up a server to host the web service, writing deploy scripts, infrastructure.		\| July 6 \|\| July 12 \|\| Web service for sharing levels (node.js)
	August 17 - August 22: <extra week for unplanned things>		\|-
			\| July 13 \|\| July 19 \|\| Polishing the game and level editor
			\|-
			\| July 20 \|\| July 26 \|\| Polishing the game and level editor
			\|-
			\| July 27 \|\| August 2 \|\| Integrating with Sugar, making the game an activity
			\|-
			\| August 3 \|\| August 9 \|\| Writing documentation, "How to play", "How to install", "How to deploy"
			\|-
			\| August 10 \|\| August 16 \|\| Setting up a server to host the web service, writing deploy scripts, infrastructure.
			\|-
			\| August 17 \|\| August 22 \|\| <extra week for unplanned things>
			\|}

	* '''Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''		* '''Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''

Andrej T: changed timeline format to table

2015-03-27T11:29:22Z

changed timeline format to table

← Older revision		Revision as of 07:29, 27 March 2015
Line 57:		Line 57:
	''Timeline:''		''Timeline:''

	May 19 - May 24: Basic game logic, and validation, state transitions		{\| class="wikitable"
	May 25 - May 31: Basic rendering and GUI, drag-and-drop, delete, rearrange commands		\|-
	June 1 - June 7: Adding Pointy animations		! Start !! End !! Description
	June 8 - June 14: Level editor tab, GUI controls (add/remove cell or button, rotate grid left/right, add/remove functions, change number of slots)		\|-
	June 15 - June 21: Level editor, implementing click (object) detection		\| May 19 \|\| May 24 \|\| Basic game logic, and validation, state transitions
	June 22 - June 27: Level editor, implementing click (object) detection		\|-
			\| May 25 \|\| May 31 \|\| Basic rendering and GUI, drag-and-drop, delete, rearrange commands
			\|-
			\| June 1 \|\| June 7 \|\| Adding Pointy animations
			\|-
			\| June 8 \|\| June 14 \|\| Level editor tab, GUI controls (add/remove cell or button, rotate grid left/right, add/remove functions, change number of slots)
			\|-
			\| June 15 \|\| June 21 \|\| Level editor, implementing click (object) detection
			\|-
			\| June 22 \|\| June 27 \|\| Level editor, implementing click (object) detection
			\|}

	Midterm		Midterm

Andrej T: added detailed timeline

2015-03-27T11:20:53Z

added detailed timeline

← Older revision		Revision as of 07:20, 27 March 2015
Line 54:		Line 54:

	* If there's enough time at the end, I'd like to create and host a promo single-page website that explains the game. Or maybe after GSOC.		* If there's enough time at the end, I'd like to create and host a promo single-page website that explains the game. Or maybe after GSOC.

			''Timeline:''

			May 19 - May 24: Basic game logic, and validation, state transitions
			May 25 - May 31: Basic rendering and GUI, drag-and-drop, delete, rearrange commands
			June 1 - June 7: Adding Pointy animations
			June 8 - June 14: Level editor tab, GUI controls (add/remove cell or button, rotate grid left/right, add/remove functions, change number of slots)
			June 15 - June 21: Level editor, implementing click (object) detection
			June 22 - June 27: Level editor, implementing click (object) detection

			Midterm

			June 28 - July 5: Finishing up the level editor
			July 6 - July 12: Web service for sharing levels (node.js)
			July 13 - July 19: Polishing the game and level editor
			July 20 - July 26: Polishing the game and level editor
			July 27 - August 2: Integrating with Sugar, making the game an activity
			August 3 - August 9: Writing documentation, "How to play", "How to install", "How to deploy"
			August 10 - August 16: Setting up a server to host the web service, writing deploy scripts, infrastructure.
			August 17 - August 22: <extra week for unplanned things>

	* '''Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''		* '''Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''

Andrej T: made stuff bold

2015-03-26T19:27:20Z

made stuff bold

← Older revision		Revision as of 15:27, 26 March 2015
Line 1:		Line 1:
	===About You===		===About You===

	* What is your name?		* '''What is your name?''' Andrej Trajchevski
	Andrej Trajchevski		* '''What is your email address?''' andrejtrajchevski@gmail.com
			* '''What is your Sugar Labs wiki username?''' Andrej_T
			* '''What is your IRC nickname on irc.freenode.net?''' Andrej_T
			* '''What is your first language?''' Macedonian
			* '''Where are you located, and what hours (UTC) do you tend to work?''' Located in Macedonia, UTC+01; Ideally, from 10:00 to 18:00 local time

	* ~~What is your email address?~~		* '''Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?'''
	~~andrejtrajchevski@gmail.com~~

	* What is your Sugar Labs wiki username?
	~~Andrej_T~~

	* What is your IRC nickname on irc.freenode.net?
	~~Andrej_T~~

	* What is your first language?
	~~Macedonian~~

	* Where are you located, and what hours (UTC) do you tend to work?
	~~Located in Macedonia, UTC+01; Ideally, from 10:00 to 18:00 local time~~

	* Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?

	A good part of my open-source contributions can be found on my Github page: https://github.com/whoeverest		A good part of my open-source contributions can be found on my Github page: https://github.com/whoeverest
Line 29:		Line 18:
	===About your project===		===About your project===

	* What is the name of your project?		* '''What is the name of your project?'''
	~~TurtleBot~~ (~~codename~~, ~~change it~~? ~~maybe it~~'~~s not about turtles)~~		Pointy, a programming game

			* '''Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?'''

	* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
	I would like to create a game that's inspired by [http://en.wikipedia.org/wiki/Lightbot LightBot], a really popular game that teaches you basic programming concepts. Basically, you're a robot (or a turtle) on a grid, and the objective is to "activate" a number of cells on the grid. You do that by dragging and dropping commands in slots: forward, turn left, jump etc. As the game progresses, writing linear procedures is no longer enough, so you're expected to extract common commands to a function or call a function recursively in order to create a loop.		I would like to create a game that's inspired by [http://en.wikipedia.org/wiki/Lightbot LightBot], a really popular game that teaches you basic programming concepts. Basically, you're a robot (or a turtle) on a grid, and the objective is to "activate" a number of cells on the grid. You do that by dragging and dropping commands in slots: forward, turn left, jump etc. As the game progresses, writing linear procedures is no longer enough, so you're expected to extract common commands to a function or call a function recursively in order to create a loop.

Line 41:		Line 31:
	It will be written in JavaScript and rendered using HTML canvas. I'll probably use some lightweight library for isometric drawing.		It will be written in JavaScript and rendered using HTML canvas. I'll probably use some lightweight library for isometric drawing.

	* What is the timeline for development of your project? The Summer of Code work period is from May 19 - August 22; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (27 June); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.		* '''What is the timeline for development of your project? The Summer of Code work period is from May 19 - August 22; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (27 June); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.'''

	First part: develop the game itself		First part: develop the game itself
Line 65:		Line 55:
	* If there's enough time at the end, I'd like to create and host a promo single-page website that explains the game. Or maybe after GSOC.		* If there's enough time at the end, I'd like to create and host a promo single-page website that explains the game. Or maybe after GSOC.

	* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.		* '''Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.'''

	For the past year I've been developing games for [https://www.gambit.com/ gambit.com] as a part of a small team. I worked on several major features, including writing Dominoes and Rock-Paper-Scissors from scratch (both backend and frontend) and writing a physics engine for billiards (based on computational pool papers, not live yet).		For the past year I've been developing games for [https://www.gambit.com/ gambit.com] as a part of a small team. I worked on several major features, including writing Dominoes and Rock-Paper-Scissors from scratch (both backend and frontend) and writing a physics engine for billiards (based on computational pool papers, not live yet).

Line 77:		Line 68:

	===You and the community===		===You and the community===
	* If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
	* What will you do if you get stuck on your project and your mentor isn't around?		* '''If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.'''
	* How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?		* '''What will you do if you get stuck on your project and your mentor isn't around?'''
			* '''How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?'''

	===Miscellaneous===		===Miscellaneous===
	* We want to make sure that you can set up a [http://developer.sugarlabs.org development environment] before the summer starts. Please do ''one'' of the following:
	** Send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "logout".		* '''We want to make sure that you can set up a [http://developer.sugarlabs.org development environment] before the summer starts. Please do ''one'' of the following:
	** Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug.		** Send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "logout".'''
	~~:: It~~'~~s normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.~~

	[[File:Sugar-dev-proof-andrejt.png\|center\|Setting up dev. env]]		[[File:Sugar-dev-proof-andrejt.png\|center\|Setting up dev. env]]

Andrej T at 19:19, 26 March 2015

2015-03-26T19:19:58Z

← Older revision		Revision as of 15:19, 26 March 2015
Line 52:		Line 52:
	Second part: develop the level editor		Second part: develop the level editor

	Scene perspective changes: rotating, scaling		* Scene perspective changes: rotating, scaling

	* Adding / removing objects: click to stack cells on the grid, right click to remove (note: this might involve patching Isomer.js because it currently doesn't support click detection. I patch the library or work around it by making the level editor simpler in some way.)		* Adding / removing objects: click to stack cells on the grid, right click to remove (note: this might involve patching Isomer.js because it currently doesn't support click detection. I patch the library or work around it by making the level editor simpler in some way.)
	* Positioning Pointy: starting position and rotation		* Positioning Pointy: starting position and rotation