WebFund 2014W: Assignment 3 - Revision history

Soma at 19:23, 22 April 2014

2014-04-22T19:23:56Z

← Older revision		Revision as of 19:23, 22 April 2014
Line 1:		Line 1:
			'''The solutions for this assignment are available [http://homeostasis.scs.carleton.ca/~soma/webfund-2014w/adventure-editor-sol.zip here].'''

	In this assignment you are to examine, modify, and answer questions regarding the [http://homeostasis.scs.carleton.ca/~soma/webfund-2014w/T7/adventure-editor.zip adventure-editor] sample node application. The files of this application are also listed below. Note that to run this application you'll first need to run <tt>node storeRooms.js</tt> to setup the rooms collection in MongoDB.		In this assignment you are to examine, modify, and answer questions regarding the [http://homeostasis.scs.carleton.ca/~soma/webfund-2014w/T7/adventure-editor.zip adventure-editor] sample node application. The files of this application are also listed below. Note that to run this application you'll first need to run <tt>node storeRooms.js</tt> to setup the rooms collection in MongoDB.

Soma at 01:33, 10 March 2014

2014-03-10T01:33:40Z

← Older revision		Revision as of 01:33, 10 March 2014
Line 1:		Line 1:
	~~'''This assignment is not yet finalized'''~~

	In this assignment you are to examine, modify, and answer questions regarding the [http://homeostasis.scs.carleton.ca/~soma/webfund-2014w/T7/adventure-editor.zip adventure-editor] sample node application. The files of this application are also listed below. Note that to run this application you'll first need to run <tt>node storeRooms.js</tt> to setup the rooms collection in MongoDB.		In this assignment you are to examine, modify, and answer questions regarding the [http://homeostasis.scs.carleton.ca/~soma/webfund-2014w/T7/adventure-editor.zip adventure-editor] sample node application. The files of this application are also listed below. Note that to run this application you'll first need to run <tt>node storeRooms.js</tt> to setup the rooms collection in MongoDB.

Soma: /* Questions */

2014-03-10T01:29:02Z

Questions

← Older revision		Revision as of 01:29, 10 March 2014
Line 11:		Line 11:
	==Questions==		==Questions==

	Part A and B are mandatory and together contain 30 points. Part C is optional and contains an additional 10 points.		Part A and B are mandatory and together contain 30 points. Part C is optional and contains an additional 10 points. Note that in cuLearn grades will be out of 40; full credit, however, is still 30 points.

	===Part A===		===Part A===

Soma: /* Part B */

2014-03-10T01:27:01Z

Part B

← Older revision		Revision as of 01:27, 10 March 2014
Line 25:		Line 25:
	# (4) In the editor, get the "Load" button to work. You should put the necessary client-side code in public/javascripts/editor.js. On the server this code should access /getContents; note, though, that you will have to make it so that the room can be selected when being requested from the editor.		# (4) In the editor, get the "Load" button to work. You should put the necessary client-side code in public/javascripts/editor.js. On the server this code should access /getContents; note, though, that you will have to make it so that the room can be selected when being requested from the editor.
	# (4) In the editor, get the "Save" button to work by implementing the appropriate server-side code.		# (4) In the editor, get the "Save" button to work by implementing the appropriate server-side code.
	# (6) ~~Add~~ a room selector to the top that lists the names of all of the rooms in the rooms collection. This should be a drop-down menu or other control of equivalent functionality.		# (4) In the editor, add a room selector to the top that lists the names of all of the rooms in the rooms collection. This should be a drop-down menu or other control of equivalent functionality.
	# (6) In the game, make it so that the game lists all of the players that are in the current room by saying in the last line of text (before the buttons), "Anil, Player7, Foo are here" (for example). You should omit the current player from this list. Keep track of the currently logged in players by adding and updating appropriately an "online" property to documents in the players collection. The query to the players collection should occur in getContents().		# (6) In the game, make it so that the game lists all of the players that are in the current room by saying in the last line of text (before the buttons), "Anil, Player7, Foo are here" (for example). You should omit the current player from this list. Keep track of the currently logged in players by adding and updating appropriately an "online" property to documents in the players collection. The query to the players collection should occur in getContents().

	===Part C (bonus)===		===Part C (bonus)===

Soma: /* Part A */

2014-03-10T01:26:29Z

Part A

← Older revision		Revision as of 01:26, 10 March 2014
Line 18:		Line 18:
	# (2) How can a player end up in the Void after starting a valid game session? Assume that the server is correctly configured and has a valid rooms collection. Also assume that the player has no access to the server other than accessing the adventure-editor web application.		# (2) How can a player end up in the Void after starting a valid game session? Assume that the server is correctly configured and has a valid rooms collection. Also assume that the player has no access to the server other than accessing the adventure-editor web application.
	# (2) What are the client-side AJAX calls in this application (before you have made any changes)?		# (2) What are the client-side AJAX calls in this application (before you have made any changes)?
	# (2)		# (4) When is the code in adventure.js called? If different functions are run at different times, explain.
	~~# (2~~)

	===Part B===		===Part B===

Soma: /* Part C (bonus) */

2014-03-10T01:24:39Z

Part C (bonus)

← Older revision		Revision as of 01:24, 10 March 2014
Line 31:		Line 31:
	===Part C (bonus)===		===Part C (bonus)===

	# (bonus 6) In the game, add buttons above the exits that say "Actions:" followed by a set of actions.		# (bonus 5) In the game, add buttons above the exits that say "Actions:" followed by a set of actions.
	#* These actions should change the activity description of the room.		#* These actions should change the activity description of the room.
	#* Make a new actions property of rooms that is an array of objects, where each object has two properties: an action and a description. The action is used to label the action buttons. The description is the text that is used to replace the current activity when the button is pressed.		#* Make a new actions property of rooms that is an array of objects, where each object has two properties: an action and a description. The action is used to label the action buttons. The description is the text that is used to replace the current activity when the button is pressed.
Line 37:		Line 37:
	#* Note the room state will be the same for all of the current players of the game!		#* Note the room state will be the same for all of the current players of the game!
	#* Using this new functionality, make it possible to ring the bell in engineering (and also stop the bell ringing).		#* Using this new functionality, make it possible to ring the bell in engineering (and also stop the bell ringing).
	# (bonus 4) Extend the editor to work with the "Actions".		# (bonus 5) Extend the editor to work with the "Actions". To get full marks make sure you provide a reasonable interface.

Soma: /* Questions */

2014-03-10T01:24:02Z

Questions

← Older revision		Revision as of 01:24, 10 March 2014
Line 11:		Line 11:
	==Questions==		==Questions==

	~~There~~ are ~~???~~ points ~~below in two parts~~. ~~Answer all questions~~.		Part A and B are mandatory and together contain 30 points. Part C is optional and contains an additional 10 points.

	===Part A===		===Part A===
Line 28:		Line 28:
	# (6) Add a room selector to the top that lists the names of all of the rooms in the rooms collection. This should be a drop-down menu or other control of equivalent functionality.		# (6) Add a room selector to the top that lists the names of all of the rooms in the rooms collection. This should be a drop-down menu or other control of equivalent functionality.
	# (6) In the game, make it so that the game lists all of the players that are in the current room by saying in the last line of text (before the buttons), "Anil, Player7, Foo are here" (for example). You should omit the current player from this list. Keep track of the currently logged in players by adding and updating appropriately an "online" property to documents in the players collection. The query to the players collection should occur in getContents().		# (6) In the game, make it so that the game lists all of the players that are in the current room by saying in the last line of text (before the buttons), "Anil, Player7, Foo are here" (for example). You should omit the current player from this list. Keep track of the currently logged in players by adding and updating appropriately an "online" property to documents in the players collection. The query to the players collection should occur in getContents().


	===Part C (bonus)===		===Part C (bonus)===

	~~'''The following questions are all extra credit.'''~~

	# (bonus 6) In the game, add buttons above the exits that say "Actions:" followed by a set of actions.		# (bonus 6) In the game, add buttons above the exits that say "Actions:" followed by a set of actions.

Soma: /* Part B */

2014-03-10T01:22:13Z

Part B

← Older revision		Revision as of 01:22, 10 March 2014
Line 23:		Line 23:
	===Part B===		===Part B===

	# ~~Make~~ it so that the game lists all of the players that are in the current room by saying in the last line of text (before the buttons), "Anil, Player7, Foo are here". You should omit the current player from this list.		# (2) In the editor, add a "quit" button to the bottom that takes you back to the initial screen.
	# ~~Add~~ buttons above the exits that say "Actions:" followed by a set of actions.		# (4) In the editor, get the "Load" button to work. You should put the necessary client-side code in public/javascripts/editor.js. On the server this code should access /getContents; note, though, that you will have to make it so that the room can be selected when being requested from the editor.
			# (4) In the editor, get the "Save" button to work by implementing the appropriate server-side code.
			# (6) Add a room selector to the top that lists the names of all of the rooms in the rooms collection. This should be a drop-down menu or other control of equivalent functionality.
			# (6) In the game, make it so that the game lists all of the players that are in the current room by saying in the last line of text (before the buttons), "Anil, Player7, Foo are here" (for example). You should omit the current player from this list. Keep track of the currently logged in players by adding and updating appropriately an "online" property to documents in the players collection. The query to the players collection should occur in getContents().


			===Part C (bonus)===

			'''The following questions are all extra credit.'''

			# (bonus 6) In the game, add buttons above the exits that say "Actions:" followed by a set of actions.
	#* These actions should change the activity description of the room.		#* These actions should change the activity description of the room.
	#* Make a new actions property of rooms that is an array of objects, where each object has two properties: an action and a description. The action is used to label the action buttons. The description is the text that is used to replace the current activity when the button is pressed.		#* Make a new actions property of rooms that is an array of objects, where each object has two properties: an action and a description. The action is used to label the action buttons. The description is the text that is used to replace the current activity when the button is pressed.
Line 30:		Line 40:
	#* Note the room state will be the same for all of the current players of the game!		#* Note the room state will be the same for all of the current players of the game!
	#* Using this new functionality, make it possible to ring the bell in engineering (and also stop the bell ringing).		#* Using this new functionality, make it possible to ring the bell in engineering (and also stop the bell ringing).
			# (bonus 4) Extend the editor to work with the "Actions".
	~~# Add a "quit" button to the bottom that takes you back to the initial screen.~~
	~~# Get the "Load" button to work by creating editor.js so that it makes the load button gets the requested room using "/getContents" and updates the form to contain the values for the loaded room.~~
	~~# Get the "Save" button by implementing the appropriate server-side code.~~
	~~# Add a room selector to the top that lists the names of all of the rooms in the rooms collection. This should be a drop-down menu or other control of equivalent functionality.~~
	# Extend the editor to work with the "Actions" ~~from the last tutorial~~.

Soma: /* Part A */

2014-03-10T01:02:01Z

Part A

← Older revision		Revision as of 01:02, 10 March 2014
Line 15:		Line 15:
	===Part A===		===Part A===

	# ~~What is~~ the raw HTML of ~~the /game~~ page before any client-side JavaScript runs?		# (2) How do you get the raw HTML of a page before any client-side JavaScript runs without modifying the configuration of any browser? Note you want to be sure to see '''exactly''' the HTML as it is received by the browser.
	# How ~~do you get to~~ the Void?		# (2) How can a player end up in the Void after starting a valid game session? Assume that the server is correctly configured and has a valid rooms collection. Also assume that the player has no access to the server other than accessing the adventure-editor web application.
	~~# How~~ is the ~~page updated when~~ the ~~player moves between rooms?~~		# (2) What are the client-side AJAX calls in this application (before you have made any changes)?
	# What is the client ~~and and server~~-side ~~code for the two~~ AJAX calls in this application?		# (2)
			# (2)

	===Part B===		===Part B===

Soma at 00:54, 10 March 2014

2014-03-10T00:54:56Z

← Older revision		Revision as of 00:54, 10 March 2014
Line 15:		Line 15:
	===Part A===		===Part A===

			# What is the raw HTML of the /game page before any client-side JavaScript runs?
			# How do you get to the Void?
			# How is the page updated when the player moves between rooms?
			# What is the client and and server-side code for the two AJAX calls in this application?

			===Part B===

	~~===Part B===~~		# Make it so that the game lists all of the players that are in the current room by saying in the last line of text (before the buttons), "Anil, Player7, Foo are here". You should omit the current player from this list.
			# Add buttons above the exits that say "Actions:" followed by a set of actions.
			#* These actions should change the activity description of the room.
			#* Make a new actions property of rooms that is an array of objects, where each object has two properties: an action and a description. The action is used to label the action buttons. The description is the text that is used to replace the current activity when the button is pressed.
			#* The activity string should not be changed directly on the client however. Instead it should send the action to the server, the server should update the room description, and then the client should retrieve the room description again after the button has been pressed (to get the current state of the room).
			#* Note the room state will be the same for all of the current players of the game!
			#* Using this new functionality, make it possible to ring the bell in engineering (and also stop the bell ringing).

			# Add a "quit" button to the bottom that takes you back to the initial screen.
			# Get the "Load" button to work by creating editor.js so that it makes the load button gets the requested room using "/getContents" and updates the form to contain the values for the loaded room.
			# Get the "Save" button by implementing the appropriate server-side code.
			# Add a room selector to the top that lists the names of all of the rooms in the rooms collection. This should be a drop-down menu or other control of equivalent functionality.
			# Extend the editor to work with the "Actions" from the last tutorial.