LOS PIMPS Cases and Tutorials

• Learn morphic. Prefab is good for making traditional gui layouts, but it is not where as powerful as morphic. It's hard to make the gui look attractive, and for complicated GUI behaviour, it will actually take you more time to code the GUI actions using prefab than with normal morphic. BUT morphic is scary and harder to jump into, so for a quick start Prefab is an ok choice.
• Start as early as you can. We didn't and we payed with all nighters.
• Do UML in a real UML editor. We had to use Ecode this semester and we REALLY didn't like it. Design is REALLY REALLY important and the best design tool for OOD is UML. I guess the ecode scenarios helped supplement, but nothing lays stuff out like a good class diagram.
• Look at cases code. Well obviously you know that since your here but believe me cases can save your butt in a bind. Nothing helps you learn squeak and solve squeak problems than by looking at squeak code.
• Hack Squeak to fix squeak errors. Squeak and Squeak tools have design flaws. If something throws a squeak error, it isn't necessarily something you should have to bother change in your code (although it usually is). Prefab list boxes for example ARE STUPID. They die if you add a scroll bar to an empty list box. The beauty of squeak is that you can go in and change anything you want. So if you feel that a morphic object shouldn't die if you do something. Change morphic. JUST BE SURE TO FILE IT OUT AND TURN IT IN!!!
• Most importantly, don't have just one guy turn everything in. Let me tell you that you are guaranteed to have a mishap. All nighters mess with your head and if your the point man you are bound to not turn in something.
• Get back what you just turned in, and set it up on a fresh squeak image so that you can be sure your TA can run the code.

Link to this Page

• Cases last edited on 30 July 2011 at 2:33 am by r59h132.res.gatech.edu