Shivam Patel 502c228cf5 ye olde tale of code | 6 years ago | |
---|---|---|
.gitignore | 6 years ago | |
Account.java | 6 years ago | |
AccountException.java | 6 years ago | |
Calendar.java | 6 years ago | |
Calendar1.java | 6 years ago | |
CalendarGraphic.java | 6 years ago | |
Date.java | 6 years ago | |
DateException.java | 6 years ago | |
DepositAccount.java | 6 years ago | |
README.TXT | 6 years ago | |
README.md | 6 years ago | |
Scrabble.java | 6 years ago | |
ScrabbleTest.java | 6 years ago | |
Squares.java | 6 years ago | |
SquaresTest.java | 6 years ago | |
TextIO.java | 6 years ago | |
TriangleOne.java | 6 years ago | |
TriangleTwo.java | 6 years ago | |
package.bluej | 6 years ago |
Java has been around a long time, and this code proves that point.
Take a look at each class, see how they are linked. They are not all linked together, but each class has something useful for you find.
Take a look at how a case statement is used instead of a whole lot of IF statements. Kind of cool, huh?
Dig around and look at how loops are used, even a nested loop or three. Play around with different parametera to the functions. Run a few.
Look at how the logic allows for various calendar operations. Much of this you can rely on the Java standard library to use, but the ideas here are good to look at and try to follow.
Run CalendarGraphic, and step through the code used to create the simple window. It uses Java's older AWT library, but does show a little bit of how to display in a window.
Notice how we create an Account object and subclass it in DepositAccount. What does the exception do? why does this seem like a good idea?
Read through this class, carefully. See how the developer is trying to simplify Java IO? Do what you find there.
Write tests for many of these classes (leave OUT TextIO). The more you do, the more points you get.