This chapter is from the book
This chapter is from the book
This chapter is from the book
The planning process
When creating a project that will contain a generous amount of ActionScript, it's wise to do some planning up front. Dealing with problems in the idea stage makes a lot more sense than dealing with them in the development stage, where they often require a great deal of time and frustration to fix. We guarantee you'll save time in the long run.
Many issues must be addressed before you even open Flash and start scripting. A good way to go about this is to ask yourself a series of questions.
What do you want to occur?
This is most important question in the script-planning process. Be as clear, informative, and visual as possible in your answer, but avoid going into too much detail.
For the project we'll create in this exercise, we want to create a scene that acts as a front end for paying your electric bill. We want the amount of the bill to be loaded into the movie from an external source, a text file. We then want to allow the user to enter an amount to pay into a text box. When a button is pressed, the amount the user paid will be compared to the amount he or she owed, and a visual and textual representation (a custom message) of the result—overpaid, underpaid, or paid in full—will be presented. When the user releases that button, we want the visual and textual elements in the scene to return to their original state. The script that accomplishes this will be the main script in the project.
What pieces of data do you need to track?
In other words, what numbers or values in the application are integral to its function? In our case, that data is the amount of the electric bill—$60. We will also need to keep track of the difference between what the user owes and what he or she has paid, so that we can display that value in custom messages.
What needs to happen in the movie prior to a script being triggered?
In our project, the amount of the electric bill must be established in the movie before anything else can happen. Since the primary goal of our project is to compare the amount of the electric bill with the amount the user chooses to pay, if the amount of the electric bill isn't established when the movie first plays, there will be nothing to compare when the script is executed. Creating and setting data prior to a script being executed, or when a movie first plays, is known as initializing the data—a common practice in scripting and something that's usually transparent to the user.
At this point, you need to start thinking about how the data—the amount of the electric bill—will get into the movie. You can place it within the movie when you author it, or you can have it loaded from an external source (for example, a server or text file) when the movie plays. For our project, we're going to opt for the latter: We'll use a simple script to load a text file containing the amount of the electric bill ($60) into the movie. This text file that's loaded into the movie to provide data is known as a data source.
What event will trigger the main script?
In our case, the answer is obvious: a button press. However, all kinds of events can trigger a script in Flash, so it's important to give some thought to this question. Does something need to happen when a user moves, presses down, or releases the mouse, or when he or she presses a key? How about when a movie clip first appears in the scene? Or does the event need to happen continuously (the whole time the movie is playing)? We'll discuss such events in detail in your next lesson.
Are there decisions to be made when the main script is triggered?
When the main script in our movie is triggered, the amount the user enters to pay needs to be compared with the amount he or she owes to determine whether the payment amount is too much, too little, or right on target. The answers to these questions will determine what custom message will be displayed as well as what is visible on the screen.
What elements make up the scene? How do they function?
Our scene will be made up of a number of elements, some of which we need to name so that ActionScript can use, control, and/or interact with them. Our scene will need a button to trigger the script, which in light of the project (pun intended), we'll make appear as a light switch flipping on and off as it's pressed and released.
We'll also need a dynamic text field to display the amount of the bill; we'll name this text field owed. In addition, we'll need an input text field where the user can enter the amount he or she wishes to pay; we'll name this text field paid. We'll also need a dynamic text field to display the custom message generated by the script; we'll name this text field message. Lastly, for visual purposes, we'll add a big light bulb to the scene. Initially, and if the user has not paid enough, it will appear off. The bulb will light if the user pays the exact amount, and it will glow red-hot if the user overpays. This light bulb will be a movie clip instance named simply light.
What will your scene look like?
Use whatever means you want—an illustration program or even a napkin—to create a rough graphical representation of your scene (both its appearance and the action that will take place). Include all of the information you've gathered up to this point. This important part of the planning process is often referred to as storyboarding.
)
As you grow more proficient at ActionScript and develop additional projects, you'll soon be able to ask (and answer) these questions intuitively. However, no matter what your skill level, storyboarding remains an essential part of the planning process.