(Please note that these are all in "draft" form, and subject to change prior to the day of the lecture.)

Lecture 21 - 6 / 10
<Cumulative Review,
142 Preview>
Slides

Lecture 20 - 6 / 8
<Final Exam>

Lecture 19 - 6 / 3
ICE: Logical Operators, Review
      ICE_18_PrintArray.java

      LogicalOperators.java

Notes
Slides

Lecture 18 - 6 / 1
ICE: Logical Operators
      ICE_18_PrintArray.java

      LogicalOperators.java

      HistogramWithRobots.java

Notes
Slides

Lecture 17 - 5 / 27
ICE:  Arrays
      ICE_17_P2.java

      ICE_18_PrintArray.java

      ICE_18_FindMaxInArray.java

      ICE_18_FillArray.java
Notes
Slides

Lecture 16 - 5 / 20
Quiz: Taken from Q#2 in Lect. 15
ICE:  Arrays

Notes
Slides

Lecture 15 - 5 / 18
ICE:  Arrays

      Random_Number_Generator

      ICE_14_Part_1_Test.java
      ICE_14_Part_2_Test.java

      FileName.java (PrintHelper #2)

      ICE_15_For_4.java

      ICE_17_P2.java

Notes
Slides

Nonrobotic Software:

     Demo_1.java
     Trace of the Demo

Lecture 14 - 5 / 13
ICE:  predicates; new loop types
      Demo_0.java (PrintHelper demo)

      ICE_11_Harvest.txt
      ICE_11_HarvestTask.java
      ICE_11_Harvester.java    

Instructor's Notes
Slides

Lecture 13 - 5 / 11
ICE:  Nested Loops
Nonrobotic Software:
      Nonrobot_Template

      ICE_15_For_4.java

      PrintingShapes.java

      NestedWhile.java
          Example: Nested Loop Trace

Notes
Slides

Lecture 12 - 5 / 6
< instructor out >

Lecture 11 - 5 / 4
ICE: Overriding, Loops, Boolean, Loops
    Link to 116 Demos

I/O:
      Basic (Keyboard) I/O

      ICE_05_IO.java

Overriding:
      ICE_10_Demo 1
      ICE_10_Demo 2 - Trace This!

Notes
Slides

Lecture 10 - 4 /29
Constructors, I/O, Overriding
Constructors:
     ICE_09_Demo_2.java
     Example of tracing the constructor

     (Robot) Starting Template

Notes
Slides

Lecture 9 - 4 / 27
ICE :Constructors, Instance Variables
Instance Variables:
     InstVar_Demo_1.java
     InstVar_Demo_2.java

     ICE_06_Errors_2.java

     Solution: RememberingRobot

Notes
Slides

Lecture 8 - 4 /22
Midterm Exam

Match partners for A3

Lecture 7 - 4/20
ICE:  Parameters ; Exam Review
Parameters:
      ICE_06_Demo_1.java
            Example Trace: Params

      ICE_06_Errors_1.java

     ICE_04_If_Else.java

Notes
Slides

Lecture 6 - 4/15
ICE : counting loops; Input/Output
Counting Loops:
    ICE_05_Demo_2.java
    ICE_05_Count.java
    ICE_04_If_Else.java

    ICE_05_Pattern_1.java

Notes
Slides

Lecture 5 - 4 / 13
ICE : while loops; counting
     I_04_If.java

    ICE_05_Demo_1.java

    ICE_05_Trace.java
    ICE_05_Avenues.java

    Hallways w/ While

    ICE_05_Race.java

Notes
Slides

Lecture 4 - 4/8
ICE:  If statements & while loops
     ICE_04_Demo_01.java
     ICE_04_01_Trace.java

     ICE_04_If_Else.java

     I_04_If.java
             Sample Solution
Notes
Slides

Overall game plan:

Lectures  1 - 7: robots, introduction (first 4 weeks)

This is pretty good.  Put the midterm off so that console I/O can be included (and maybe instance variables?)

Lectures  9 - 16: details, non-robotic software, arrays (second 4 weeks)

Mostly good.  BUT - remove the Nested loop stuff (impacts A4), and instead focus on stuff like logical operators, expression evaluation, etc

Lectures  17 - 22: Arrays, wrap-up (last 3 weeks)

A4 needs to be synch'd up against the arrays topic. Maybe plan on having the final revision due during the last week of the term?

Overall:

Replace A3/A4 with two tracks:
Basic should mimic A1/A2: trace, fix, short-and-sweet coding
Advanced: What the basic A3/A4 are now
Both: Provide small but constant amounts of extra credit on each ( ~5 points each)
Journal: Dump entirely.

• Was slow this time - didn't even fully complete the 'how to change around the program exercise' 
• Emphasize that they will need to start the HW ASAP
• Emphasize A LOT that if they want to work from home, they'll need to start installing the software now, so that they can hit, and then overcome, installation problems BEFORE they're at the last minute.  Promise them help if they bring their problems + laptops to next class w/ any problems
  • Also post the hours of the building, OLC
• 2009 Fall:
  • Still slow, but it felt ok.
  • Emphasized the quiz & HW, covered everything needed for the quiz
  • SHOULD CHANGE A1 P1 so that the robot is named 'Jo', as was demonstrated in class
  • There's way too much detail in the ICE - strip out the exercises, and replace with:
    1. Examine the demo that crashes into the wall, focus on the Jo.move(); part
    2. Write the 4 basic commands, challenge them to figure out what each one does (make them present their answers to the class)
    3. Once they're done figuring that out, do the quiz-oid (pick up the thing, move it over... here, end up there facing that way)
       SIDE-NOTE: It would be really interesting to (re)develop the course around the notion that a concept is explained overall (in terms of goal & syntax), and that the students then figure out what it does (perhaps with a series of leading questions?).
• Then look for time to roll into the debugging...

• Put (in comments) an objective, so that there can be logical errors in the code, as well
• Throw a 'CityFrame' error into the compile-time errors thing, or else remove it from A1
• Don't talk quite so much
• RE-Emphasize that they need to install the software way before they start the HW.  No extensions will be given for HW1.
  • Note that the building it closed on Sundays

• Again with the logical errors
• Game plan: Demo, brief blurb explaining objective of methods, DEMO TRACE (and then have them do it), COVER syntax (then have them find errors), THEN have them do work on their own.
•       EXAMPLE SOLUTION
  

• Have them trace the demo (pick a configuration that has some, but not all; cover the countThingsInBackpack() thingee)
  THEN Do the syntax
• Factor out the 'long hallway' program, so that there's a method call 'chooseDirection' at the end of 'goToNextTurn', and specify that they're only allowed to change that
  In main, do the "movex4, then call chooseDirection"
• Make sure to introduce frontIsClear and the if...else, prior to the chooseDirection part of the lecture.
• It might be good to split the first part up: tracing code (both if & if...else, then finding errors w/ the frontIsClear), this way we'll hit the long hallway problem with them having all the pieces already.
• Simplify the 'pipe' exercise, so that you can do it with just an if ( if(canPickThing, turnleft) if(frontIsClear, move)
• Introduce if/else?

• Worked pretty well, actually

• Worked pretty well, actually

• Probably better to put this off a week, then include the I/O and instance variables in the mix
• Random numbers: Provide them this code in A4, then skip it here

• This went slowly (probably too slowly).  Appears to be little retention between this class & next
• Students are getting confused between instance variables, parameters, and local variables - ICE to have them list & explain the differences?

• Can we get away with initializing instance variables directly, and leave out the constructor thing entirely?

• Nobody gets this, and it doesn't build to anything - ditch it & focus on logical operators, predicate methods, etc

• Random numbers: Provide them this code in A4, then skip it here.  Alternately, emphasize the 'number in nextInt is HOW MANY numbers, + X for the minimum end of the range'?

A3/A4: trace/etc

Does a good job of reinforcing material

use shorter traces

Alt idea:

Syntax Summary page for each construct ("if: ...., while:....."), etc
    basic structure is actually listed in the book (pg 59, for example)

Students fill in the blanks?

Book sync:

"Notes were better than book" - polish?

Lay of the land was good, but dated

only 1/2 page on return statements
   (Use more examples from the book?)

HOWTO: Use jEdit in class: http://www.stfrank.com/ExposureJavaJEdit.html

Reflective Outcomes Journal

Sample Starter File For Word 2007
(download this & start typing in Word 2007, and the correct font size, spacing, etc, should all be set up for you)