How to Lingo Final Requirements

To help you prepare your How to Lingo project for grading, here's a complete list of required elements:

Part 1: A main screen with the legend "How to Lingo" and at least seven buttons, one for each part or scene described below. All the buttons must work. The text on them may vary, but it should adequately describe the 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. Scripted animation is described at iat.ubalt.edu/courses/mult201.001_F03/scriptedButterfly.shtml. If you present an optional variation, include it in your navigation scheme -- that is, add a button to your menu and be sure the user can return to the main menu from the optional scene.

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. Most people who included these variations simply built them into the main scene. Specific instructions for the Case assignment are available at iat.ubalt.edu/courses/mult201/caseAssignment.shtml.

Part 5: The first "Walker" experiment, featuring the cartoon figure delivered as 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. Instructions for "Lingo Walker" are available at iat.ubalt.edu/courses/mult201.001_F03/lingoWalker.shtml.

Part 7: "Arcade Game Prototype." This scene includes the continuous scrolling background (using the Vue d'Esprit images provided) and the right-left Poser figure animated via Lingo. The figure's movements are controlled either through arrow keys or buttons on screen. The background moves either independently or when the walker moves. Hazard objects (cinderblocks) fall from the top of the stage at random times and positions. You are not required to build any scoring or game logic into the prototype. By adding these elements and creating three distinct levels of play, you may convert Part 7 into your Term Project. Instructions for the Game Prototype were given in two documents, available at iat.ubalt.edu/courses/mult201.001_F03/walkerScroller.shtml and iat.ubalt.edu/courses/mult201.001_F03/fallout1021.shtml.

Part 8: "Blackjack." This scene comprises the completed Blackjack simulator with both player and dealer actions included. In this case you must complete game play, scoring, and outcomes. You are not required to convert the card names (strings) to graphics, or to include a betting mechanism--though you may add these features to convert Part 8 into your Term Project. Instructions are available at iat.ubalt.edu/courses/mult201.001_F03/part8.shtml.