I've finally managed to find the example webs from previous years, so they are now on the project page for you all.

The code for project 7 is now available.

The code for project 5 is now available.

The code for project 4 has now been uploaded. I'm sorry about the delay for those of you who wanted immediate access to the code, but I wanted to verify that the code was the correct version. If there are any discrepancies between the posted code and the report please let me know.

I have created an examples section of the website; here I will post miscellaneous examples created to demonstrate in class problems. The first one you will find is from today's discussion on method selection at runtime.

Please read the memorandum concerning assignment reports for tips on how to achieve the highest report score. It is available at http://www.cs.utexas.edu/users/afdreher/cs315h/advice/ReportMemo.pdf.

The API for the Critter code is now online. I think the API is correct for the Critter code; if not please let me know.

This is the third assignment, so I shouldn't have to remind you all about this, but despite most of you having it down, it's become enough of a problem, so here it goes. Absolutely make sure you follow the specifications / directions to the last letter. I hate to do this to you all, but I will not be nice about this in the future. So, a few things (not exhaustive):

1. When the instructions say "prog3.jar", it means exactly that: "Prog3.jar", "proj3.jar", "pro3.zip", etc. are NOT acceptable.
2. Your JAR files MUST include your java code. Unless otherwise specified in the instructions, all of these java files should be immediately available for compilation by javac *.java; you should also not place it into any directory structure. I would also like to ask you to include the code we provide to you; it makes it much easier to compile / run your program, which I assure you is to your benefit.
3. Only include ONE version of each file. If there are multiple files with the same name, etc. I reserve the right to grade whichever one I see fit. This does not mean that I will purposefully cause your grade to be the worst of the two, but it also does not mean that I will try to interpret your files first. Likely, the first one I encounter is the first I will use. I would highly suggest that you pick the version you want graded -- it's only in your best interest.
4. Do NOT include extraneous files. If you used Word, etc. to write your documentation, fine, but submit only the PDF or TXT version. You should not include your scratch notes, images, the IDE, configuration files, etc. If you think these may be of interest while evaluating your project, place them on your website and provide the link with your report. This also means that you should not include the non-code files we give you to test your code (such as sample images, etc.).
5. DO include your test files. If you create any test cases, definitely include them. Do not include the results or output in separate files. If it's that important that you want it evaluated, include it as part of your report.

I will be compiling and running all of your from the command line; your code should be able to be run this way. However, I realize some of you may be more excited about structuring your code, using packages, etc. and I would prefer to not place too many restrictions on you, so please include instructions with your code as a README text file if your code is not compiled by just "javac *.java" and run by just "java <name of main class>".

The code for project 3 is now available.

Links to project 1 sample reports have been posted under the Project 1 page.

The code for project 2 is now available.

I have finally posted some links in the additional resources section. Feel free to check them out. They include instructions on how to create JAR files, etc.

I cannot stress this one enough: Make sure you have your UTCS UNIX or Microlab account. This is not the same as your UTEID. If you do not have a UTCS UNIX or Microlab account, you will not be able to turn in your program. To get a Microlab account, there is a kiosk computer as you walk in to the lab to request a new account, or you can go to https://udb.cs.utexas.edu/amut/acut/ to create an account. Your new account will not be active for 24 to 48 hours so that means you have needed your account; if you do not have one get it immediately. Also, test your account by logging in. If you do not do this, do not complain when you cannot turn in your program.

For this course, you will not need to use an IDE, and you may find that it actually gets in your way. However, many of you many want to use one and want to know which are acceptable. As a general rule, anything which writes code for you or uses templates for various functions (other than just main) will not be acceptable. On the microlabs, both BlueJ and Eclipse are fine. If you are using OS X, you may also use XCode. You should not use JCreator under Windows for the previously mentioned reason.

Note, however, that an IDE may be a hinderance. I know that getting this project to work under BlueJ may be difficult because of the way JIP and transformations interact; your effects do not show up in the menu bar. The easy solution is to just use the command line, by typing the following commands in order: javac Transformations.java, javac JIP.java, and then java JIP. Remember to press return after each command.

I do not really care what version of Java you use, but I will be testing your program under 1.5 or 1.6. Therefore, I would highly suggest you use on of these two versions. You can check your version with the command java -version.

The code for project 1 is now available. Try to get started early, in case you have any questions.