WebFund 2015W: Assignment 6 - Revision history

Soma at 20:52, 28 March 2015

2015-03-28T20:52:30Z

@@ Line 1: / Line 1: @@
 In this assignment you will be modifying [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/persistent-notes.zip the persistent notes demo] from [[WebFund 2015W: Tutorial 6|Tutorial 6]].  There are 10 points in 5 tasks.  This assignment is due by 10 AM on <del>Monday, March 9, 2015</del> '''Wednesday, March 11, 2015'''.
@@ Line 21: / Line 19: @@
 #* POST /changeusername should report whether the username change succeeded or failed and should then have a link that goes back to <tt>/notes</tt>.
 #* The new username can be any username that is not currently being used by any stored notes.  Note that you'll need to change the username in the session and update the owner field in stored notes as appropriate.

Soma at 20:49, 28 March 2015

2015-03-28T20:49:58Z

← Older revision		Revision as of 20:49, 28 March 2015
Line 1:		Line 1:
			'''Solutions to this assignment [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/persistent-notes-sol.zip are now available].'''

	In this assignment you will be modifying [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/persistent-notes.zip the persistent notes demo] from [[WebFund 2015W: Tutorial 6\|Tutorial 6]]. There are 10 points in 5 tasks. This assignment is due by 10 AM on <del>Monday, March 9, 2015</del> '''Wednesday, March 11, 2015'''.		In this assignment you will be modifying [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/persistent-notes.zip the persistent notes demo] from [[WebFund 2015W: Tutorial 6\|Tutorial 6]]. There are 10 points in 5 tasks. This assignment is due by 10 AM on <del>Monday, March 9, 2015</del> '''Wednesday, March 11, 2015'''.

Soma at 19:04, 8 March 2015

2015-03-08T19:04:55Z

← Older revision		Revision as of 19:04, 8 March 2015
Line 1:		Line 1:
	In this assignment you will be modifying [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/persistent-notes.zip the persistent notes demo] from [[WebFund 2015W: Tutorial 6\|Tutorial 6]]. There are 10 points in 5 tasks. This assignment is due by 10 AM on Monday, March 9, 2015.		In this assignment you will be modifying [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/persistent-notes.zip the persistent notes demo] from [[WebFund 2015W: Tutorial 6\|Tutorial 6]]. There are 10 points in 5 tasks. This assignment is due by 10 AM on <del>Monday, March 9, 2015</del> '''Wednesday, March 11, 2015'''.

	Please submit your answers as a zip file called "<username>-comp2406-assign6.zip", where username is your MyCarletonOne username. This zip file should uncompress to a directory called "<username>-comp2406-assign6" and inside this directory should be two things: a directory "persistent-notes" that contains the application and a text file "comments.txt".		Please submit your answers as a zip file called "<username>-comp2406-assign6.zip", where username is your MyCarletonOne username. This zip file should uncompress to a directory called "<username>-comp2406-assign6" and inside this directory should be two things: a directory "persistent-notes" that contains the application and a text file "comments.txt".

Soma: /* Tasks */

2015-03-06T20:15:45Z

Tasks

← Older revision		Revision as of 20:15, 6 March 2015
Line 14:		Line 14:
	# [2] Implement a note delete button on the edit note page. This delete button should redirect to a page /delete/<note ID> that asks the user to confirm whether to delete the note. This page should have a form that does a POST to /delete with a hidden id field for the note ID that actually does the deletion. The result of this POST should be a page that says whether the deletion succeeded or not then gives a link to go back to /notes. The delete button should have an <tt>id="delete"</tt> assigned. On the confirmation page, the form should have a <tt>name="form_confirm"</tt>.		# [2] Implement a note delete button on the edit note page. This delete button should redirect to a page /delete/<note ID> that asks the user to confirm whether to delete the note. This page should have a form that does a POST to /delete with a hidden id field for the note ID that actually does the deletion. The result of this POST should be a page that says whether the deletion succeeded or not then gives a link to go back to /notes. The delete button should have an <tt>id="delete"</tt> assigned. On the confirmation page, the form should have a <tt>name="form_confirm"</tt>.
	# [2] Allow links to be embedded in notes using the syntax of "[<link> <label>]" where link is a URL for an <a> tag and the label (the rest of the text in the square brackets) is the label for the URL. If there is no label then the link itself should be the <a> tag's label.		# [2] Allow links to be embedded in notes using the syntax of "[<link> <label>]" where link is a URL for an <a> tag and the label (the rest of the text in the square brackets) is the label for the URL. If there is no label then the link itself should be the <a> tag's label.
	# [4] Add a Change Username button to /notes that allows you to change the username for a user. This button should have an <tt>id=changeusername</tt> assigned. It should ~~redirect to~~ a page called <tt>/changeusername</tt>. The text field for the changed username should have a <tt>name="username"</tt>. The new username can be any username that is not currently being used by any stored notes. Note that you'll need to change the username in the session and update the owner field in stored notes as appropriate.		# [4] Add a Change Username button to /notes that allows you to change the username for a user.
			#* This button should have an <tt>id=changeusername</tt> assigned. It should cause a GET of a page called <tt>/changeusername</tt>.
			#* GET /changeusername should ask the user for the new username. The text field for the changed username should have a <tt>name="username"</tt> as part of a form that has a POST action of <tt>/changeusername</tt>.
			#* POST /changeusername should report whether the username change succeeded or failed and should then have a link that goes back to <tt>/notes</tt>.
			#* The new username can be any username that is not currently being used by any stored notes. Note that you'll need to change the username in the session and update the owner field in stored notes as appropriate.

Soma at 17:53, 5 March 2015

2015-03-05T17:53:52Z

← Older revision		Revision as of 17:53, 5 March 2015
Line 1:		Line 1:
	~~'''This assignment is not yet finalized.'''~~

	In this assignment you will be modifying [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/persistent-notes.zip the persistent notes demo] from [[WebFund 2015W: Tutorial 6\|Tutorial 6]]. There are 10 points in 5 tasks. This assignment is due by 10 AM on Monday, March 9, 2015.		In this assignment you will be modifying [http://homeostasis.scs.carleton.ca/~soma/webfund-2015w/code/persistent-notes.zip the persistent notes demo] from [[WebFund 2015W: Tutorial 6\|Tutorial 6]]. There are 10 points in 5 tasks. This assignment is due by 10 AM on Monday, March 9, 2015.

Soma at 19:16, 4 March 2015

2015-03-04T19:16:48Z

← Older revision		Revision as of 19:16, 4 March 2015
Line 13:		Line 13:
	==Tasks==		==Tasks==
	# [1] Make it so the contents of notes escape embedded HTML tags (just as is done in the note title).		# [1] Make it so the contents of notes escape embedded HTML tags (just as is done in the note title).
	# [1] Add a Cancel button to the Note editor page. It should be a button (like the other buttons in the application) that takes the user back to the notes listing page.		# [1] Add a Cancel button to the Note editor page. It should be a button (like the other buttons in the application) that takes the user back to the notes listing page. The cancel button should have an <tt>id="cancel"</tt> assigned.
	# [2] Implement a note delete button on the edit note page. This delete button should redirect to a page /delete/<note ID> that asks the user to confirm whether to delete the note. This page should have a form that does a POST to /delete with a hidden id field for the note ID that actually does the deletion. The result of this POST should be a page that says whether the deletion succeeded or not then gives a link to go back to /notes.		# [2] Implement a note delete button on the edit note page. This delete button should redirect to a page /delete/<note ID> that asks the user to confirm whether to delete the note. This page should have a form that does a POST to /delete with a hidden id field for the note ID that actually does the deletion. The result of this POST should be a page that says whether the deletion succeeded or not then gives a link to go back to /notes. The delete button should have an <tt>id="delete"</tt> assigned. On the confirmation page, the form should have a <tt>name="form_confirm"</tt>.
	# [2] Allow links to be embedded in notes using the syntax of "[<link> <label>]" where link is a URL for an <a> tag and the label (the rest of the text in the square brackets) is the label for the URL. If there is no label then the link itself should be the <a> tag's label.		# [2] Allow links to be embedded in notes using the syntax of "[<link> <label>]" where link is a URL for an <a> tag and the label (the rest of the text in the square brackets) is the label for the URL. If there is no label then the link itself should be the <a> tag's label.
	# [4] Add a Change Username button to /notes that allows you to change the username for a user. This username can be any username that is not currently being used. Note that you'll need to change the username in the session and update the owner field in stored notes as appropriate.		# [4] Add a Change Username button to /notes that allows you to change the username for a user. This button should have an <tt>id=changeusername</tt> assigned. It should redirect to a page called <tt>/changeusername</tt>. The text field for the changed username should have a <tt>name="username"</tt>. The new username can be any username that is not currently being used by any stored notes. Note that you'll need to change the username in the session and update the owner field in stored notes as appropriate.

Soma: /* Tasks */

2015-03-01T23:34:23Z

Tasks

← Older revision		Revision as of 23:34, 1 March 2015
Line 13:		Line 13:
	==Tasks==		==Tasks==
	# [1] Make it so the contents of notes escape embedded HTML tags (just as is done in the note title).		# [1] Make it so the contents of notes escape embedded HTML tags (just as is done in the note title).
	# [2] Allow links to be embedded in notes using the syntax of "[<link> <label>]" where link is a URL for an <a> tag and the label (the rest of the text in the square brackets) is the label for the URL. If there is no label then the link itself should be the <a> tag's label.
	# [1] Add a Cancel button to the Note editor page. It should be a button (like the other buttons in the application) that takes the user back to the notes listing page.		# [1] Add a Cancel button to the Note editor page. It should be a button (like the other buttons in the application) that takes the user back to the notes listing page.
	# [2] Implement a note delete button on the edit note page. This delete button should redirect to a page /delete/<note ID> that asks the user to confirm whether to delete the note. This page should have a form that does a POST to /delete with a hidden id field for the note ID that actually does the deletion. The result of this POST should be a page that says whether the deletion succeeded or not then gives a link to go back to /notes.		# [2] Implement a note delete button on the edit note page. This delete button should redirect to a page /delete/<note ID> that asks the user to confirm whether to delete the note. This page should have a form that does a POST to /delete with a hidden id field for the note ID that actually does the deletion. The result of this POST should be a page that says whether the deletion succeeded or not then gives a link to go back to /notes.
			# [2] Allow links to be embedded in notes using the syntax of "[<link> <label>]" where link is a URL for an <a> tag and the label (the rest of the text in the square brackets) is the label for the URL. If there is no label then the link itself should be the <a> tag's label.
	# [4] Add a Change Username button to /notes that allows you to change the username for a user. This username can be any username that is not currently being used. Note that you'll need to change the username in the session and update the owner field in stored notes as appropriate.		# [4] Add a Change Username button to /notes that allows you to change the username for a user. This username can be any username that is not currently being used. Note that you'll need to change the username in the session and update the owner field in stored notes as appropriate.

Soma: /* Tasks */

2015-03-01T22:18:44Z

Tasks

← Older revision		Revision as of 22:18, 1 March 2015
Line 15:		Line 15:
	# [2] Allow links to be embedded in notes using the syntax of "[<link> <label>]" where link is a URL for an <a> tag and the label (the rest of the text in the square brackets) is the label for the URL. If there is no label then the link itself should be the <a> tag's label.		# [2] Allow links to be embedded in notes using the syntax of "[<link> <label>]" where link is a URL for an <a> tag and the label (the rest of the text in the square brackets) is the label for the URL. If there is no label then the link itself should be the <a> tag's label.
	# [1] Add a Cancel button to the Note editor page. It should be a button (like the other buttons in the application) that takes the user back to the notes listing page.		# [1] Add a Cancel button to the Note editor page. It should be a button (like the other buttons in the application) that takes the user back to the notes listing page.
	# [2] (Implement a note delete button on the edit note page.)		# [2] Implement a note delete button on the edit note page. This delete button should redirect to a page /delete/<note ID> that asks the user to confirm whether to delete the note. This page should have a form that does a POST to /delete with a hidden id field for the note ID that actually does the deletion. The result of this POST should be a page that says whether the deletion succeeded or not then gives a link to go back to /notes.
	# [4] (Add a Change Username button to /notes that allows you to change the username for a user. This username can be any username that is not currently being used. Note that you'll need to change the username in the session and update the owner field in stored notes as appropriate.)		# [4] Add a Change Username button to /notes that allows you to change the username for a user. This username can be any username that is not currently being used. Note that you'll need to change the username in the session and update the owner field in stored notes as appropriate.

Soma at 21:54, 1 March 2015

2015-03-01T21:54:52Z

← Older revision		Revision as of 21:54, 1 March 2015
Line 10:		Line 10:
	* optionally, should discuss any issues or concerns you had when completing this assignment.		* optionally, should discuss any issues or concerns you had when completing this assignment.
	Remember that while you are allowed to collaborate with others, plagiarism is not allowed. In other words you '''should not''' be copying any code or data directly from anywhere, and any assistance or inspiration should be credited. Any significant code similarity (beyond the code already given to you) will be considered plagiarism and will be reported to the Dean.		Remember that while you are allowed to collaborate with others, plagiarism is not allowed. In other words you '''should not''' be copying any code or data directly from anywhere, and any assistance or inspiration should be credited. Any significant code similarity (beyond the code already given to you) will be considered plagiarism and will be reported to the Dean.


	==Tasks==		==Tasks==

Soma at 21:54, 1 March 2015

2015-03-01T21:54:40Z

← Older revision		Revision as of 21:54, 1 March 2015
Line 9:		Line 9:
	* list your collaborators, and		* list your collaborators, and
	* optionally, should discuss any issues or concerns you had when completing this assignment.		* optionally, should discuss any issues or concerns you had when completing this assignment.
	Remember that while you are allowed to collaborate with others, plagiarism is not allowed. In other words you '''should not" be copying any code or data directly from anywhere, and any assistance or inspiration should be credited. Any significant code similarity (beyond the code already given to you) will be considered plagiarism and will be reported to the Dean.		Remember that while you are allowed to collaborate with others, plagiarism is not allowed. In other words you '''should not''' be copying any code or data directly from anywhere, and any assistance or inspiration should be credited. Any significant code similarity (beyond the code already given to you) will be considered plagiarism and will be reported to the Dean.