Mobile App Dev 2021W: Tutorial 8 - Revision history

Soma at 01:05, 6 April 2021

2021-04-06T01:05:19Z

← Older revision		Revision as of 01:05, 6 April 2021
Line 308:		Line 308:
	==Solutions==		==Solutions==

	[https://homeostasis.scs.carleton.ca/~soma/mad-2021w/solutions/tut8-solutions.txt ~~Tutorial 8 Solutions~~]		Tutorial 8 Solutions
			* [https://homeostasis.scs.carleton.ca/~soma/mad-2021w/solutions/tut8-solutions.txt text file]
			* [https://homeostasis.scs.carleton.ca/~soma/mad-2021w/solutions/tut8-sol.zip code + text file]

Soma at 15:35, 5 April 2021

2021-04-05T15:35:50Z

← Older revision		Revision as of 15:35, 5 April 2021
Line 305:		Line 305:
	</androidx.constraintlayout.widget.ConstraintLayout>		</androidx.constraintlayout.widget.ConstraintLayout>
	</syntaxhighlight>		</syntaxhighlight>

			==Solutions==

			[https://homeostasis.scs.carleton.ca/~soma/mad-2021w/solutions/tut8-solutions.txt Tutorial 8 Solutions]

Soma at 02:51, 30 March 2021

2021-03-30T02:51:17Z

← Older revision		Revision as of 02:51, 30 March 2021
Line 1:		Line 1:
	~~'''~~This tutorial is ~~still being developed~~.~~'''~~		This tutorial is due on <b>April 4, 2021</b> via cuLearn. Please use [https://homeostasis.scs.carleton.ca/~soma/mad-2021w/templates/tut8-template.txt this template] for your solutions.

	==Tasks==		==Tasks==

Soma at 02:30, 30 March 2021

2021-03-30T02:30:15Z

← Older revision		Revision as of 02:30, 30 March 2021
Line 8:		Line 8:
	<li>How many widgets do you have to move in order to get the input fields and their labels moved to the left side of the screen or centered? Why?</li>		<li>How many widgets do you have to move in order to get the input fields and their labels moved to the left side of the screen or centered? Why?</li>
	<li>What values do the fields take on when you delete all the text? Is it the same for every field?</li>		<li>What values do the fields take on when you delete all the text? Is it the same for every field?</li>
	<li>Change the EditText input widgets so the X and Y fields can accept negative numbers.		<li>Change the EditText input widgets so the rotation, X, and Y fields can accept negative numbers.
	<li>There is a lot of duplicated code in MainActivity.kt. What is the primary source of duplicated code?</li>		<li>There is a lot of duplicated code in MainActivity.kt. What is the primary source of duplicated code?</li>
	<li>How can the PicWatcher class be used to greatly reduce the amount of duplicated code?</li>		<li>How can the PicWatcher class be used to greatly reduce the amount of duplicated code?</li>

Soma at 02:29, 30 March 2021

2021-03-30T02:29:19Z

← Older revision		Revision as of 02:29, 30 March 2021
Line 8:		Line 8:
	<li>How many widgets do you have to move in order to get the input fields and their labels moved to the left side of the screen or centered? Why?</li>		<li>How many widgets do you have to move in order to get the input fields and their labels moved to the left side of the screen or centered? Why?</li>
	<li>What values do the fields take on when you delete all the text? Is it the same for every field?</li>		<li>What values do the fields take on when you delete all the text? Is it the same for every field?</li>
			<li>Change the EditText input widgets so the X and Y fields can accept negative numbers.
	<li>There is a lot of duplicated code in MainActivity.kt. What is the primary source of duplicated code?</li>		<li>There is a lot of duplicated code in MainActivity.kt. What is the primary source of duplicated code?</li>
	<li>How can the PicWatcher class be used to greatly reduce the amount of duplicated code?</li>		<li>How can the PicWatcher class be used to greatly reduce the amount of duplicated code?</li>

Soma: /* Tasks */

2021-03-29T21:32:57Z

Tasks

← Older revision		Revision as of 21:32, 29 March 2021
Line 12:		Line 12:
	<li>How can you change the fields so they all take on an appropriate default value when all text is deleted?</li>		<li>How can you change the fields so they all take on an appropriate default value when all text is deleted?</li>
	<li>Change PicWatcher so its constructor takes an additional function as an argument, clamp(), that takes a float as an argument and returns a float. Use this new function to implement appropriate clamping functions for each values as follows: 0 <= scale <= 5, 0 <= rotation <= 720, -1000 <= x, y <= 1000. If the current value is outside the range, it should be set to either the smallest or the largest value in the range, as appropriate.</li>		<li>Change PicWatcher so its constructor takes an additional function as an argument, clamp(), that takes a float as an argument and returns a float. Use this new function to implement appropriate clamping functions for each values as follows: 0 <= scale <= 5, 0 <= rotation <= 720, -1000 <= x, y <= 1000. If the current value is outside the range, it should be set to either the smallest or the largest value in the range, as appropriate.</li>
	<li>When PicViewer2A is rotated, it preserves its state. Add the following method to MainActivity()		<li>When PicViewer2A is rotated, it preserves its state. Add the following method to MainActivity():
	<pre>		<pre>
	override fun onSaveInstanceState(outState: Bundle) {		override fun onSaveInstanceState(outState: Bundle) {

Soma: /* Tasks */

2021-03-29T21:32:39Z

Tasks

← Older revision		Revision as of 21:32, 29 March 2021
Line 13:		Line 13:
	<li>Change PicWatcher so its constructor takes an additional function as an argument, clamp(), that takes a float as an argument and returns a float. Use this new function to implement appropriate clamping functions for each values as follows: 0 <= scale <= 5, 0 <= rotation <= 720, -1000 <= x, y <= 1000. If the current value is outside the range, it should be set to either the smallest or the largest value in the range, as appropriate.</li>		<li>Change PicWatcher so its constructor takes an additional function as an argument, clamp(), that takes a float as an argument and returns a float. Use this new function to implement appropriate clamping functions for each values as follows: 0 <= scale <= 5, 0 <= rotation <= 720, -1000 <= x, y <= 1000. If the current value is outside the range, it should be set to either the smallest or the largest value in the range, as appropriate.</li>
	<li>When PicViewer2A is rotated, it preserves its state. Add the following method to MainActivity()		<li>When PicViewer2A is rotated, it preserves its state. Add the following method to MainActivity()
			<pre>
	override fun onSaveInstanceState(outState: Bundle) {		override fun onSaveInstanceState(outState: Bundle) {
	Log.d(appName, "State saved")		Log.d(appName, "State saved")
	}		}
			</pre>
	This change should cause PicViewer2A to no longer preserve state across rotations. How can you modify this function so it again preserves the app's state? What does this change tell you about how PicViewer2A works?		This change should cause PicViewer2A to no longer preserve state across rotations. How can you modify this function so it again preserves the app's state? What does this change tell you about how PicViewer2A works?
	</li>		</li>

Soma: /* Tasks */

2021-03-29T21:32:22Z

Tasks

← Older revision		Revision as of 21:32, 29 March 2021
Line 3:		Line 3:
	==Tasks==		==Tasks==

	# Add another picture to the assets of PicViewer2A. How can you make sure this pic is shown by default?		<ol>
	# How do you change the code so your added pic will appear eventually when clicking on the current image?		<li> Add another picture to the assets of PicViewer2A. How can you make sure this pic is shown by default?</li>
	# How many widgets do you have to move in order to get the input fields and their labels moved to the left side of the screen or centered? Why?		<li>How do you change the code so your added pic will appear eventually when clicking on the current image?</li>
	# What values do the fields take on when you delete all the text? Is it the same for every field?		<li>How many widgets do you have to move in order to get the input fields and their labels moved to the left side of the screen or centered? Why?</li>
	# There is a lot of duplicated code in MainActivity.kt. What is the primary source of duplicated code?		<li>What values do the fields take on when you delete all the text? Is it the same for every field?</li>
	# How can the PicWatcher class be used to greatly reduce the amount of duplicated code?		<li>There is a lot of duplicated code in MainActivity.kt. What is the primary source of duplicated code?</li>
	# How can you change the fields so they all take on an appropriate default value when all text is deleted?		<li>How can the PicWatcher class be used to greatly reduce the amount of duplicated code?</li>
	# Change PicWatcher so its constructor takes an additional function as an argument, clamp(), that takes a float as an argument and returns a float. Use this new function to implement appropriate clamping functions for each values as follows: 0 <= scale <= 5, 0 <= rotation <= 720, -1000 <= x, y <= 1000. If the current value is outside the range, it should be set to either the smallest or the largest value in the range, as appropriate.		<li>How can you change the fields so they all take on an appropriate default value when all text is deleted?</li>
	# When PicViewer2A is rotated, it preserves its state. Add the following method to MainActivity()		<li>Change PicWatcher so its constructor takes an additional function as an argument, clamp(), that takes a float as an argument and returns a float. Use this new function to implement appropriate clamping functions for each values as follows: 0 <= scale <= 5, 0 <= rotation <= 720, -1000 <= x, y <= 1000. If the current value is outside the range, it should be set to either the smallest or the largest value in the range, as appropriate.</li>
			<li>When PicViewer2A is rotated, it preserves its state. Add the following method to MainActivity()

	override fun onSaveInstanceState(outState: Bundle) {		override fun onSaveInstanceState(outState: Bundle) {
Line 18:		Line 19:

	This change should cause PicViewer2A to no longer preserve state across rotations. How can you modify this function so it again preserves the app's state? What does this change tell you about how PicViewer2A works?		This change should cause PicViewer2A to no longer preserve state across rotations. How can you modify this function so it again preserves the app's state? What does this change tell you about how PicViewer2A works?
			</li>
			</ol>

	==Code==		==Code==

Soma: /* Tasks */

2021-03-29T21:31:11Z

Tasks

← Older revision		Revision as of 21:31, 29 March 2021
Line 11:		Line 11:
	# How can you change the fields so they all take on an appropriate default value when all text is deleted?		# How can you change the fields so they all take on an appropriate default value when all text is deleted?
	# Change PicWatcher so its constructor takes an additional function as an argument, clamp(), that takes a float as an argument and returns a float. Use this new function to implement appropriate clamping functions for each values as follows: 0 <= scale <= 5, 0 <= rotation <= 720, -1000 <= x, y <= 1000. If the current value is outside the range, it should be set to either the smallest or the largest value in the range, as appropriate.		# Change PicWatcher so its constructor takes an additional function as an argument, clamp(), that takes a float as an argument and returns a float. Use this new function to implement appropriate clamping functions for each values as follows: 0 <= scale <= 5, 0 <= rotation <= 720, -1000 <= x, y <= 1000. If the current value is outside the range, it should be set to either the smallest or the largest value in the range, as appropriate.
			# When PicViewer2A is rotated, it preserves its state. Add the following method to MainActivity()

			override fun onSaveInstanceState(outState: Bundle) {
			Log.d(appName, "State saved")
			}

			This change should cause PicViewer2A to no longer preserve state across rotations. How can you modify this function so it again preserves the app's state? What does this change tell you about how PicViewer2A works?

	==Code==		==Code==

Soma: /* Tasks */

2021-03-29T20:15:47Z

Tasks

← Older revision		Revision as of 20:15, 29 March 2021
Line 9:		Line 9:
	# There is a lot of duplicated code in MainActivity.kt. What is the primary source of duplicated code?		# There is a lot of duplicated code in MainActivity.kt. What is the primary source of duplicated code?
	# How can the PicWatcher class be used to greatly reduce the amount of duplicated code?		# How can the PicWatcher class be used to greatly reduce the amount of duplicated code?
	# How can you change the fields so they all take on a value ~~of zero~~ when all text is deleted?		# How can you change the fields so they all take on an appropriate default value when all text is deleted?
	# Change PicWatcher so its constructor takes an additional function as an argument, clamp(), that takes a float as an argument and returns a float. Use this new function to implement appropriate clamping functions for each values as follows: 0 <= scale <= 5, 0 <= rotation <= 720, -1000 <= x, y <= 1000. If the current value is outside the range, it should be set to either the smallest or the largest value in the range, as appropriate.		# Change PicWatcher so its constructor takes an additional function as an argument, clamp(), that takes a float as an argument and returns a float. Use this new function to implement appropriate clamping functions for each values as follows: 0 <= scale <= 5, 0 <= rotation <= 720, -1000 <= x, y <= 1000. If the current value is outside the range, it should be set to either the smallest or the largest value in the range, as appropriate.