cs1302-hw0.5 Implementing Tic-Tac-Toe - Part 2

This homework is designed to give students the opportunity to complete the Tic-Tac-Toe game in a Unix environment. This homework also explores the check1302 program that helps students check their code style. At the end of the assignment, students will have an opportunity to submit an assignment on Odin for the first time.

Prerequisite Knowledge

• An understanding of classes, objects, and 2-D arrays in the Java programming language.

Exercise Steps

Setup Steps

1. Log into your Odin account. You should not use an IDE to complete this homework. Instead, you are expected to use Odin and Emacs.

2. Complete the Recommended Emacs Configurations section of the CSCI 1302 Style Guide (more details soon). This will set up Emacs to minimize style errors later in the assignment. Do not skip this step. Setting up your Emacs environment will help you avoid issues throughout the semester. If you have questions about this part, please don't hesitate to ask on the course Piazza page or ask an instructor/TA during office hours.

3. Use Git to clone the repository for this exercise onto Odin into a subdirectory called cs1302-hw0.5 using the following command (remember not to type the $ as that represents our prompt):

   $ git clone --depth 1 https://github.com/cs1302uga/cs1302-hw0.5.git
   

Checkpoint 1 Steps

1. Change into the cs1302-hw0.5 directory and type the tree command. You should see three familiar files under the src directory. This is the same code you downloaded and completed in the previous homework assignment.
2. Without changing directories, open the TicTacToeGame.java file using Emacs. Take a minute to look through the file. You should recognize this as the original file without any of the modifications you made last week.
3. Take a moment to think about the process of downloading this code from GitHub (you just typed a single command) and compare that process to what you had to do to get started last week (saving the file to your hard drive, locating your favorite IDE, creating a project in your IDE, importing the code, etc.).
4. Now that we've got our environment set up, we want you to complete TicTacToeGame.java on Odin using Emacs. Please do this without copying and pasting your code from an IDE. The purpose of this part of the exercise is for you to get practice with Emacs. It may feel slow and error-prone at first. However, you will get much faster over time. Note: You should have already implemented these methods (if you haven't, please go back to the first part of this assignment).
5. Once your code is completed, exit the Emacs text editor. You should still be in the cs1302-hw0.5 diretory.
6. Create a new folder called bin directly within the cs1302-hw0.5 directory.
7. Compile the three Java files located in the src directory - placing the byte code (.class) files in the bin directory (remember, order matters!). Also, don't forget to use the -d command-line option when compiling.
   • Note that the Java files are not in a named package. For this homework, compiling to the default package is okay.
8. If you have any syntax errors, note where the error occurs, go back into TicTacToeGame.java and fix the errors.
9. Once your code compiles, run the TicTacToeTester class and make sure it passes all tests. If not, fix the bugs in the code before proceeding.
10. Once the TicTacToeTester passes all of the provided tests, run the TicTacToeRunner and play a few games of Tic-Tac-Toe keeping an eye out for any bugs that may not have been caught by the tester. If you're confident that your code is working, proceed to the next checkpoint.

---

---

Checkpoint 2 Steps

1. In this checkpoint, we want to make sure our code is readable and follows the course style guidelines which are described in the 1302 Style Guide.

2. Take a few minutes to read up to the "Recommended Emacs Configurations" section of the style guide, which explains the motivation behind having good code style.

3. Run the check1302 command on your src directory to see if you have any style errors.

4. If you receive any style errors, you can find a description of the error along with what causes the error in the Specific Guidelines section of the guide. There is no need to memorize the different types of errors. You will have access to the guide when coding in this course.

5. When there are no more style errors, you should see the following output after running check1302 on your code:

   Starting audit...
   Audit done.
   

6. Congratulations on a nice, working Tic-Tac-Toe game written on Unix with good code style! You're now ready to submit the application.

---

---

Submission Steps

Each student needs to individually submit their own work.

1. Create a plain text file called SUBMISSION.md directly inside the cs1302-hw0.5 directory with your name and UGA ID number.

   Here is an example of the contents of SUBMISSION.md.

   Sally Smith (811-000-999)
   

2. Change directories to the parent of cs1302-hw0.5 (e.g., cd .. from cs1302-hw0.5).

3. Use the submit command to submit this exercise to csci-1302:

   $ submit cs1302-hw0.5 csci-1302
   

   Read the output of the submit command very carefully. If there is an error while submitting, then it will displayed in that output. Additionally, if successful, the submit command creates a new receipt file in the directory you submitted. The receipt file begins with rec and contains a detailed list of all files that were successfully submitted. Look through the contents of the rec file and always remember to keep that file in case there is an issue with your submission.

   Note: You must be on Odin to submit.

---

---

Copyright © Michael E. Cotterell, Brad Barnes, and the University of Georgia. This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License to students and the public. The content and opinions expressed on this Web page do not necessarily reflect the views of nor are they endorsed by the University of Georgia or the University System of Georgia.