CoWeb Assignment 1 (due 5/22)

1. Mini Java-to-Squeak Tutorial
   This tutorial, like the title suggests, is devoted to showing how the concepts are coded in Java and in Squeak. It's very useful because I would argue that many of us are have only used Java in college (I know have be cause Matlab isn't a real language to me), and when lerning a new language, it is best to first notice the similarities it has with another language instead of starting from scatch.
   
2. Chowder Powder's Sudoku PA2
   Right away the author mentions the mistake he made on starting the first assignment too late and without a partner and thus receiving a great big zero. However he's turned over a new leaf and started the next assignment early and with a partner. He and his partner worked in the "Extreme Programming" fashion instead of using the "divide and conquer" that inevitably leads to disaster. Besides providing an algorithm they used for the auto solver portion and a warning about remembering to do the Sunit testing first, Team Chowder Powder actually doesn't reveal the secrets of their code to the public.
   
3. A tutorial for Morphic by Mike Noonan
   Mike Noonan discusses his favorite aspect of Squeak, Morphic, specifically regarding his 2-d animation project. Mike analyzes the qualities of SketchMorph, which he used to draw the arms and legs of his actor for the project. However he ran into a problem trying to rotate on an axis that was not based on the center. He solved this problem "by loading an image into the sketchmorph that was transparant on one half of the side." (see figures below)
   
   But Mike also discovered by using TransformMorph in the first place he could've avoided the whole problem entirely. Mike gives an example code of how to use CurveMorph/ PolygonMorph and explains that TextMorph is used for text manipulations. Using the morphs he advises to not forget to intialize the super:

   super initialize.

   Mike then gives examples of basic functions and how to display an image inside SketchMorph. He then adds each portion of the actor to the main Morph. In order to manage all of the submorphs, Mike iterates through the submorphs and when he find a PolygonMorph he makes it invisible.

   self submorphs do: [:each |
   (each isKindOf: (PolygonMorph)) ifTrue: [each visible: false]]
   ].

   Mike's tutorial is fairly detailed and presented with pictures and definately with help on projects using Morph.
   
4. Video Professor: Because reading is HARD.
   Frankly I must say that this case is awesome. It quickly introduced me to the world of Squeak though video. Though the quality of the video kind of required me to view the movie a couple of times, it was well worth it. The topics that were filmed included: how to file in new code, edit code, quickly save, quickly share code, work with Morphs and much more.
   
5. A Tutorial on Good Design

• Tips for creating excellent UML
  Team Half & Half recommend Rational Rose or Microsoft Visio for UML diagrams. The single most important idea regarding UML diagrams is that you must remember that everything must connect and in effect work together and resemble your CRC cards.
• Tips for creating perfect CRC cards
  Team Half & Half recommend maintaining an electronic copy of your CRC cards in case they are not returned before the next assignment is due. Also remember to divide the responsibilities evenly across the CRC cards to prevent the creation of a "god class" which according to Team Half & Half is bad news.
• Tips for creating grade A Scenarios
  Team Half & Half warned you that the graders are expecting "a detailed, sentence-form analysis of the different situations a user may encounter" and that you should include all the possible types of errors and how your program handles them. Team Half & Half direct you to both good and bad examples in their own work.
• Tips for creating lovely test cases
  A test case document actually is is a document that discusses the specific details about the test cases. Team Half & Half tells you to create a graph with five column headings: TestCase Number, Context, Test, Expected Result, and Actual Results; the Context fields refers to the actual class that is being tested, and the Test fields tells what test to use to ensure that the program works.

Link to this Page

• Assignments last edited on 27 July 2006 at 8:06 pm by r33h146.res.gatech.edu