|
|||
|
Last things Term Project Specs PLP Team Assignments Key control code Including Blackjack Including game prototype How to Lingo Sample How to Lingo Summary Blackjack project How to Lingo midterm Fallout Game, Part 1 Walker-scroller project Lingo Walker project Unique random selection Case assignment Scripted animation Hints for Part 3 Term project Timeline vs. scripting Materials from UB Course "How To Lingo" Project Syllabus |
How to Lingo Midterm ReviewI'll soon be conducting a midterm review of your How to Lingo projects. To help you get ready, here's a review of the required elements, along with some pointers about features you'll want to include. Midterm review will cover only Parts 1-6 of the project. The "Fallout" game and the final part (possibly the dice game Craps) are not part of this review, though they do count toward your grade for the project. I. Required elements Part 1: A main screen with the legend "How to Lingo" and at least five buttons, one for each subsequent part so far. All the buttons must work. The text on them may vary, but it should adequately describe the part (scene) to which it leads. There must also be a working Quit button. Part 2: The "Button Actions" scene with working tests for each of the eight button actions. In this and all scenes other than the first there must be a working button that returns us to the main menu, as well as a working Quit button. Part 3: The scene called "Conditionals," consisting of the alternating butterfly animation done with multiple frames. You may also, optionally, include the variation on the butterfly animation done with scripting in a single frame. This is not required, but including it will improve your grade. If you present an optional variation, include it in your navigation scheme. Part 4: The scene called "Randoms" or "Case," consisting of our experiments with Case statements, random numbers, colors, buttons, and a text field. (Note that in the original How to Lingo specs this was assigned for Part 7; I revised the order of assignments.) There were at least two possible variations on this project. The first involved using Lists in your code instead of Case statements. The second involved placing constraints on the random number selection. Two methods for constraining randomization were presented. Again, variations should be included in the navigation. Part 5: The first "Walker" experiment, featuring the cartoon figure running from a Film Loop. The completed version of this project includes a pause in mid-screen and a background element that slides past the walker while he is paused. Part 6: "Lingo Walker." This is the two-frame, scripted version of the Walker, featuring the cartoon, the Poser figure I provided, or any other figure of your choice. If you built a distinct variation for either of these parts (as opposed to simply including different features in the main project), be sure your variation is included in the navigation scheme. II. Feature checklist Be sure your How to Lingo project satisfies the following requirements: 1. It is contained within a single Director movie, not multiple files. This movie must be named How2Lingo[YourLastName].dir Replace [YourLastName] with your last name. 2. ALL ELEMENTS IN THE CAST ARE NAMED. I will deduct credit for Casts that contain unnamed elements. 3. There are no flaws or gaps in the navigation. I must be able to quit and return to the main menu from every scene. Scenes need not be linked directly. Optional scenes may be linked either from the main menu or from the standard scenes on which they are based. 4. Where you've done something interesting, clever, or difficult, you've included a note to that effect. You can place such notes in code comments or in text fields on the visible Stage. | ||
|
|||