CSC 216 F09/pretty-pretty-program - Revision history

Ewkochuk: /* The script */

2009-11-18T03:53:35Z

The script

← Older revision		Revision as of 03:53, 18 November 2009
Line 37:		Line 37:
	#GUI Elements: Add the GUI Elements to your LinkedList.		#GUI Elements: Add the GUI Elements to your LinkedList.
	#Instance Variables: Add Instance Variables to your LinkedList.		#Instance Variables: Add Instance Variables to your LinkedList.
			#Getters / Setters : Add Getters/Setters to your LinkedList.

	Maintaining your LinkedList		Maintaining your LinkedList

Ewkochuk: /* The script */

2009-11-18T03:53:04Z

The script

← Older revision		Revision as of 03:53, 18 November 2009
Line 36:		Line 36:
	#JUnit Test: Add a single JUnit Test to your LinkedList. If you already have a JUnit Test, you may take another.		#JUnit Test: Add a single JUnit Test to your LinkedList. If you already have a JUnit Test, you may take another.
	#GUI Elements: Add the GUI Elements to your LinkedList.		#GUI Elements: Add the GUI Elements to your LinkedList.
			#Instance Variables: Add Instance Variables to your LinkedList.

	Maintaining your LinkedList		Maintaining your LinkedList

Kdgraves: /* The script */

2009-11-18T03:51:24Z

The script

← Older revision		Revision as of 03:51, 18 November 2009
Line 30:		Line 30:
	Spaces on the Game Board		Spaces on the Game Board
	( The spaces on the game board mean different things when you land on them.)		( The spaces on the game board mean different things when you land on them.)
	#Compiler: Add the ~~Compilerto~~ your LinkedList if no one has yet added it. Otherwise, use a Remove method to take the Compiler from them, and then add it into your LinkedList instead.		#Compiler: Add the Compiler to your LinkedList if no one has yet added it. Otherwise, use a Remove method to take the Compiler from them, and then add it into your LinkedList instead.
	#Null Pointer Exception: If you land on the Null Pointer Exception object, you must add it to your LinkedList. If another player already has a Null Pointer Exception in their linked list, use a remove method to take it from them and add it to your own list. The Null Pointer Exception replaces your team's getter/setter object, if you already have one.		#Null Pointer Exception: If you land on the Null Pointer Exception object, you must add it to your LinkedList. If another player already has a Null Pointer Exception in their linked list, use a remove method to take it from them and add it to your own list. The Null Pointer Exception replaces your team's getter/setter object, if you already have one.
	#Steal Code!: Add a single piece of code to your LinkedList. This can come from other players (in which case, they must remove the item from their list) or from the unclaimed pile (so you only must add it to your own). You can take the compiler, even if no one else has claimed it.		#Steal Code!: Add a single piece of code to your LinkedList. This can come from other players (in which case, they must remove the item from their list) or from the unclaimed pile (so you only must add it to your own). You can take the compiler, even if no one else has claimed it.

Ewkochuk: CSC 216 F09/pretty-pretty-programmer moved to CSC 216 F09/pretty-pretty-program: fixing title

2009-11-18T03:49:10Z

CSC 216 F09/pretty-pretty-programmer moved to CSC 216 F09/pretty-pretty-program: fixing title

← Older revision	Revision as of 03:49, 18 November 2009
(No difference)

Kdgraves: /* The problem */

2009-11-18T03:49:02Z

The problem

← Older revision		Revision as of 03:49, 18 November 2009
Line 8:		Line 8:
	This exercise is loosely based on the board game, "Pretty Pretty Princess", a game in which players must acquire 5 pieces of jewelry: 2 earrings, a necklace, a crown, and a ring.		This exercise is loosely based on the board game, "Pretty Pretty Princess", a game in which players must acquire 5 pieces of jewelry: 2 earrings, a necklace, a crown, and a ring.

	In this exercise, students will play a variant called "Pretty Pretty ~~Programmer~~", where they will try to ~~collect everything they need to complete their Java program. However, instead of jewelry, the students will~~ collect the different parts of a program. The students must demonstrate their mastery of Java by storing the items in a LinkedList. Students must be able to both add, swap, and remove objects from the list, as programmers are very greedy, and much stealing, replacing, and bickering over each others LinkedLists is bound to occur.		In this exercise, students will play a variant called "Pretty Pretty Program", where they will try to collect the different parts of a program. The students must demonstrate their mastery of Java by storing the items in a LinkedList. Students must be able to both add, swap, and remove objects from the list, as programmers are very greedy, and much stealing, replacing, and bickering over each others LinkedLists is bound to occur.

	===Participants and props===		===Participants and props===

Kdgraves: /* Formatting Resources */

2009-11-18T03:48:12Z

Formatting Resources

← Older revision		Revision as of 03:48, 18 November 2009
Line 1:		Line 1:
	~~===Formatting Resources===~~
	~~[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]~~

	==Pretty Pretty Program==		==Pretty Pretty Program==

Ewkochuk: /* The script */

2009-11-18T03:48:09Z

The script

← Older revision		Revision as of 03:48, 18 November 2009
Line 35:		Line 35:
	#Steal Code!: Add a single piece of code to your LinkedList. This can come from other players (in which case, they must remove the item from their list) or from the unclaimed pile (so you only must add it to your own). You can take the compiler, even if no one else has claimed it.		#Steal Code!: Add a single piece of code to your LinkedList. This can come from other players (in which case, they must remove the item from their list) or from the unclaimed pile (so you only must add it to your own). You can take the compiler, even if no one else has claimed it.
	#Crash Without Saving!: You must remove any piece of your code or the Compiler from your LinkedList. If you have the Null Pointer Exception, you must remove this from your LinkedList instead of getting to choose. If there is nothing for you to return, your turn is over.		#Crash Without Saving!: You must remove any piece of your code or the Compiler from your LinkedList. If you have the Null Pointer Exception, you must remove this from your LinkedList instead of getting to choose. If there is nothing for you to return, your turn is over.
			#JUnit Test: Add a single JUnit Test to your LinkedList. If you already have a JUnit Test, you may take another.
			#GUI Elements: Add the GUI Elements to your LinkedList.

	Maintaining your LinkedList		Maintaining your LinkedList
Line 41:		Line 43:

	Winning		Winning
	# To win the game, you must collect all the necessary code in your LinkedList: This includes TWO JUnit Tests, Instance Variables, Getters/Setters, and GUI Components. You must also have the Compiler and not have the Null Pointer Exception. If you have all of that, you win. Turn to the programmers all around you and haughtily announce, "I'm a Pretty Pretty ~~Programmer~~!"		# To win the game, you must collect all the necessary code in your LinkedList: This includes TWO JUnit Tests, Instance Variables, Getters/Setters, and GUI Components. You must also have the Compiler and not have the Null Pointer Exception. If you have all of that, you win. Turn to the programmers all around you and haughtily announce, "I have a Pretty Pretty Program!"

	See http://www.ehow.com/about_5076372_pretty-pretty-princess-game-rules.html as a reference		See http://www.ehow.com/about_5076372_pretty-pretty-princess-game-rules.html as a reference

Kdgraves: /* Pretty Pretty Program */

2009-11-18T03:47:36Z

Pretty Pretty Program

← Older revision		Revision as of 03:47, 18 November 2009
Line 2:		Line 2:
	[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]		[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]

	==Pretty Pretty ~~Programmer~~==		==Pretty Pretty Program==

Ewkochuk: /* The script */

2009-11-18T03:45:52Z

The script

← Older revision		Revision as of 03:45, 18 November 2009
Line 27:		Line 27:
	Game Play		Game Play
	# Players may place their team marker on any of the 16 spaces to start.		# Players may place their team marker on any of the 16 spaces to start.
	# Spin the spinner and move your piece the number of spaces the spinner lands on. The space you land on will have a direction for you to follow. If you land on a space and already have that piece of ~~jewelry~~, your turn is over. If you land on a space with the ~~earrings~~, you may only add one ~~earring~~ to your LinkedList. That is the end of the turn, and the play goes to the next person. You can also share spaces with other people.		# Spin the spinner and move your piece the number of spaces the spinner lands on. The space you land on will have a direction for you to follow. If you land on a space and already have that piece of code, your turn is over. If you land on a space with the JUnit tests, you may only add one JUnit to your LinkedList. That is the end of the turn, and the play goes to the next person. You can also share spaces with other people.

	Spaces on the Game Board		Spaces on the Game Board

Kdgraves: /* The problem */

2009-11-18T03:45:44Z

The problem

← Older revision		Revision as of 03:45, 18 November 2009
Line 9:		Line 9:
	This exercise is loosely based on the board game, "Pretty Pretty Princess", a game in which players must acquire 5 pieces of jewelry: 2 earrings, a necklace, a crown, and a ring.		This exercise is loosely based on the board game, "Pretty Pretty Princess", a game in which players must acquire 5 pieces of jewelry: 2 earrings, a necklace, a crown, and a ring.

	In this exercise, students will play a variant called "Pretty Pretty Programmer", where they will try to collect everything they need to complete their ~~java~~ program. However instead of ~~actually wearing~~ the ~~items in question,~~ the students must demonstrate their mastery of Java by storing the items in a LinkedList. Students must be able to both add, swap, and remove objects from the list, as programmers are very greedy, and much stealing, replacing, and bickering over each others LinkedLists is bound to occur.		In this exercise, students will play a variant called "Pretty Pretty Programmer", where they will try to collect everything they need to complete their Java program. However, instead of jewelry, the students will collect the different parts of a program. The students must demonstrate their mastery of Java by storing the items in a LinkedList. Students must be able to both add, swap, and remove objects from the list, as programmers are very greedy, and much stealing, replacing, and bickering over each others LinkedLists is bound to occur.

	===Participants and props===		===Participants and props===