Welcome to the CS100A Home Page!
This page is the premier source for information regarding CS100A. Be sure to check this
page often, especially for late breaking news close to assignment submission times! You
can find copies of handouts and assignments here, as well as some other useful links.
- Carpenter consulting. The consulting
room will be open from 1 to 3PM this week (Mon-Fri) and on Mon., 14 Dec.
- Regrades. Please turn in
all regrade requests by Friday morning (tomorrow), 10AM, so that we can finish all the
grading and regrading over the weekend.
- Checking grades. Next
Tues-Thurs (8-10 Dec.), please check all your grades, which will be posted in Carpenter.
If there is a discrepancy --a missing or wrong grade-- write a note about it and leave it
with the consultant; attach the assignment/prelim for which the grade is wrong so that we
can check it.
- Review session. A review
session is scheduled in Olin 155 on Sunday, 13 December, at 3PM.
- Office hours. The TAs and
Professor Cardie will hold their regular office hours during the period 7 December -- 14
December. Gries will have office hours during that time as follows:
Tues.
8 Dec, 2--3:30, Thurs. 10 Dec 2--3:30, Mon. 14 Dec 1--3:00
- Final. The final is on 15
December, 9:00--11:30, in . IN the Center of Barton. At the moment, no makeup is
scheduled. Anyone who has a conflict that may require us to have a makeup should email
Gries at gries@cs.cornell.edu.
- 12/7 - Dec1-2 Sections notes up in sections.
- ANSWERS TO QUIZA and QUIZB
i= n; c= 1;
i= n-1; x= 1;
while (i > 0) {
while (i >= 0) {
if (b[i] != b[i-1]) c= c+1;
if (b[i] ==
b[i+x]) x= x+1;
i= i-1;
i= i-1;
}
}
- NT ON SPECIAL CREDIT FOR CHECKERS. Right now, there are two "states", which
are indicated by clickflag=0 and clickflag=1 (or something like that). You probably want
to add a third one, clickflag=2, which means that another jump is possible.
- Specification for the Extra Credit Checkers Assignment. We asked that you hand in a specification
of the changes you will make. Many of you wrote designs instead; you described
how you would implement it. A specification of a programs says what the program
does, not how it does it.We wanted to know the details about what the players
would see concerning double jumps and how they could respond. Here is a sample
specification:
After red (say, the spec for black is similar) makes a jump, if red can jump again, the
piece stays highlighted and the text on the right of the GUI is changed to say "red
can jump again or black can play.". Red can then click on a destination square; if it
is a legal jump for the highlighted piece the jump is made; otherwise nothing happens. If
red does not want to jump, black can simply select a piece to move, and the game
continues.
Note: if you want to make jumps mandatory, you may do so.
- ASSIGNMENT 10 HAS BEEN CANCELED. There is no assignment 10.
- NOTE ON ASSIGNMENT 9! People are asking how one writes text onto the SystemOutput
window. Here is how you could (should have) figured it out. In class CruiseControl,
variable sysout contains the instance of SystemOutput that is associated
with the output window. So, we now look at class SystemOutput. There, we see that
a variable area contains an instance of class TextArea and that area
is added to the Frame (the output window). Obviously, the text gets written in this TextArea.
So, we have to see what methods are available in class TextArea. On my computer,
I look at C:/Program Files/Metrowerks/CodeWarrier/Java Support/Java Source/java/awt/ and
there, I find file TextArea.java. Admittedly, this took a bit of time and experience to
find. And I find that there is a method appendText(String s),
which appends String s to the TextArea. So that is the method I
use. When append a String to the TextArea, make sure you put a line feed
"\n" in suitable places.
Programming, these days, includes the ability to search for what you need, in a
knowledgeable way.
- The Final in CS100 is on Tuesday,. 15 December, 9:00--11:30.
- 11/12 - Lecture and section notes available in source format as well as HTML.
lectures sections
- 10/29 - Bug list for Code Warrior available here.
Links to important course pages:
- CS100 General Information
- Guide to CodeWarrior Java for CS100 and CS211
- Debugging Java Program with CodeWarrior for CS100
and CS211
- Installing CodeWarrior Java on a Macintosh
- Installing CodeWarrior Java on a PC
- Notes on Java Programming Style
- Registration form (to be handed out in
class, Tuesday, 1 September)
- Course syllabus (giving proposed contents
of lectures, dates of exams, dates of assignments, etc.)
- Bug List for Code Warrior
- Lecture handout: Definitions
- CUCS Java stationary. Below are links to two files: one for the PC and the other for the
Mac. Each contains "Java stationary" --two projects of a certain nature that we
will use in CS99, CS100A, and CS100B. If you have your own computer, choose the
appropriate file: (0) download it, (1) extract the files from it, and read and follow the
README file, which gives directions on storing the two projects into your CodeWarrior IDE
(Interactive Development Environment) so you can use this "stationary".
- File to download for the PC
- File to download for the Mac
If you have any questions or comments about this page, please
contact: pyen@cs.cornell.edu
Page last modified: 23 August 2000