|
Comp201: Principles of Object-Oriented Programming I
Spring 2008 -- Exam 2 Need-To-Knows
|
The following is a non-exhaustive list of topics, concepts and skills
that will be covered in Exam 2. This list is subject to frequent changes, so
check back often!
This list is in no particular order, nor does it indicate any sort of priority,
unless otherwise noted.
All topics covered in Exam 1 are required for Exam 2!
- Lists
- Tail Recursion
- Immutable list framework with visitors and factories (listFW)
- Mutable lists with visitors (LRStruct)
- Know how to write recursive algorithms for both types of lists using
visitors.
- Visitor design pattern:
- Know how to create all the classes involved, including the execute method.
- Relationship to Interpreter pattern
- Algorithms on immutable lists (listFW)
- Algorithms on mutable lists (LRStruct)
- Factory design pattern:
- As an abstraction of construction
- To hide implementations
- Usage with lists
- Classes within classes: Know how to write these, to use closures, and
to understand code that uses them!
- Nested classes
- sytnax of
- are static
- can access only static fields and methods (why?)
- Inner classes
- named inner classes
- syntax of
- difference between nested classes.
- anonymous inner classes
- syntax
- usage to reduce the number of named classes
- usage to represent singleton type objects.
- usage to create dynamically defined objects.
- usage to create listeners for GUI components
- usuage to create custom paint methods for GUI components
- closures
- Access to fields in outer class
- Access to final local variables
- persistence of communication with outer class
- Usage to minimize passing of input parameters
- Usage with factories
- Usage with visitor-type algorithms
- GUI programming
- Basic but not memorized knowledge of using frames, panels, content panes,
buttons, text fields and labels.
- Getting and setting text in textfields and labels.
- Basic but not memorized knowlege of using layout managers
- Event-driven programs
- How events work.
- defining listeners using anonymous inner classes
- adding listeners to GUI components, e.g. buttons
- State design pattern
- as a representation of dynamic reclassification
- difference between Strategy pattern
- coded using package visible external classes.
- coded using inner and/or nested classes
Last Revised
Thursday, 03-Jun-2010 09:50:26 CDT
©2008 Stephen Wong and Dung Nguyen