CSE 132 (Spring 2015)
Lab 1: Percenterator meets Mt Evans

Abstract:

Set up

1. You are encouraged to work in pairs on labs, but if you want to work on your own, that's fine too.

2. Start Eclipse: In CEC, click on the Start button and look under "All Programs", "Programming" to start up eclipse. The first time Eclipse starts, it will be slower than usual. You will be asked where you want your workspace to be.

   We recommend using the default location, and checking the box so you won't be asked again.

   After Eclipse starts up, click the 'X' on the "Welcome" tab at the top to close the welcome screen.

3. Identifying your repository: If necessary, open the subversive tutorial in another window for the instructions on how to use subversion to load your repository in eclipse. If you need help with these instructions, ask a TA or another student to help you along.

   When you get to the point of entering the full and complete location of the repository, copy and paste the line below as the repository's URL:

   https://shell.cec.wustl.edu:8443/cse132_sp15/svn/YYYY

   After pasting:

   • Change YYYY to your WUSTL key, using lower case letters only. Include all punctuation that is normally part of your WUSTL key.

     If you would normally type in the WUSTL key shown on the left, you need to use the version shown in blue on the right to access your repository. Examples:

     • RonKCytron → ronkcytron
     • ima.StudeNt → ima.student
     • Queen.Mary.4 → queen.mary.4

     Although only you can access your repository, you should generally keep your WUSTL key a secret.

   • OK, click Finish to get the repository location validated.
   • When you are prompted for a username and password, supply your
     • WUSTL key username (again, all letters must be lower-case)
     • WUSTL key password

     Your WUSTL key username and password are what you use to log into WebSTAC for registration.

     Be careful! If you provide a bad password repeatedly, your account will get locked out after a small number of such attempts. So be sure to follow these instructions carefully and ask if things are not working.

   
   

4. Continue following the rest of the instructions in the subversive tutorial so that you are back in the Java view and have the project available for your use.

   Those instructions next ask you to Check Out a copy of the repository location so you can do the work for this lab. Be sure to right click on the whole project (your WUSTL key name) to do the checkout. Do NOT click on things below that like src.

5. As always:

   We push code to your repository throughout the semester. So before you go further, make sure your repo is up-to-date by:

   • Right (control) click on the topmost part of your repository in the package explorer.
   • Drag down to Team
   • Choose Update

6. Your lab code is found in the labs source folder in the lab1 package.
7. Open RGB.java in your lab1 package.
8. You should see a copy of the percent package, similar to what you developed in studio.
9. This RGB code won't compile until you initialize the green and blue instance variables. Each needs to be an instance of Controller, and each should be added to the RGB (as was done with red).
10. Run the RGB as a Java application, and use the sliders to change the colors. You can move the sliders as you wish, and when you want to see the resulting picture, click the "go" button.

Unnecessary detail, so skip if you want: Ok you're reading this, so you have a craving for details. I thought that might be the case.

• The code managing the picture part of this lab is from an old, old version of 131, and it's in a package called nip, which you can find in the labsupport source folder.
• The package name nip is an acronym.
• But what does it stand for? click here to set the mood
• If you come by my office and can correctly tell me its expansion, you will get a piece of candy.
• A second piece is yours if you can tell me the name of nip's predecessor.

Actually, anytime you stop by you can have the candy.

Pick one of the following

Do two of them in your lab session by the time you demo to earn 10 extra lab credit points and the admiration of your TAs.

In whatever you pick, keep in mind:

• It is the model you should be affecting and examining
• Do not change the sliders or text field from your program; let them react on their own to changes you make to the model.

• React when the sliders move: do not wait for the "go" button to be pushed.

  Hint: You can see how an ActionListener is added to the "go" button. This uses an anonymous inner class, which I'll explain in more detail in upcoming lectures. Try the same kind of thing with the model of each Controller, but use the ChangeListener instead. It reacts when the model's value is changed.

  Eclipse is pretty good about suggesting what you'll need to implement the ChangeListener interface. Click on the yellow light bulbs to get that kind of help

  Get some help from TAs or other students if you need it.

• Add a "lock" button that causes the value set by moving one slider to be set in the other sliders' models as well. Try this one slider at a time to be sure you have the right idea.

  Address your method calls to the underlying model and not the slider directly. For example, if the red model value changes, then set the same value in the green and blue models.

  You'll need the ChangeListener methodology described above.

  If possible, make your lock button toggle between locked mode and unlocked mode. Its text should reflect its current state (locked or unlocked).

• The sliders currently cause the color to be reduced, from 100% to 0%. 100% is the color's actual value. At 0%, the color intensity value is 0.

  Devise a way for a color to be increased instead of decreased, from its actual value to a maximum of 255.

Demo

When you done with this studio, you must be cleared by the TA to receive credit.

• Commit all your work to your repository!

  If you do not commit, the TAs cannot grade your work and you will receive a 0 for this assignment!

• Fill in the form below with the relevant information
• Have a TA check your work
• The TA should check your work and then fill in his or her name
• Click OK while the TA watches
• If you request propagation, it does not happen immediately, but should be posted in the next day or so

Items Completed (TA Verify!):		1 item (full credit).
		2 items (+10 points extra credit and admiration).
		All 3 items (+10 points and true bragging rights!). Sorry, no more points than 2 items.

	Last name	WUSTL Key	Propagate?
		(or your numeric ID)		Do not propagate
e.g.	Smith	j.smith
1				Copy from 1 to all others
2				Copy from 2 to all others

---

TA: Make sure they commit their code before you sign them out!

TA: Password: