|
File "linear.dir" contains six commandments that will be used as screens for navigation. You will use it as a starting point. It contains in addition a title page as a first cast member. The seven members are placed in different channels and play slowly linearly, one frame per second. If you want to give some control to the user on when to move on to the next commandment, you can insert timing commands in the Tempo channel to proceed only after a click. File "jumplinear.dir"has
a little interactivity; you have to click the mouse to
advance the slide show, and
you always have the opportunity to go back to the title
page. This is done through the go to command that is placed
in
the sprite. Do Instead of 'go to frame 1' create a marker "title" on
the initial frame and go to it. gives the impression that there is not much movement in the user experience. The center of the screen changes, but the navigational aids (the buttons in this case) stay in the same place. The users feel that they can access any part of the application at the click of a button. File "network.dir" allows movement between commandments on demand. You are always presented with a menu of commandments and you can bring up to the screen each one on demand. Notice that even this is a network, it actually behaves as the "frame" navigation technique. File "tree.dir"tries to implement the tree of screens shown in cast member "tree" (and in the beginning of the movie). The first level is implemented through markers. The three cast members that send the playback head to three different frames, do it through cast member scripts. The movie's progression is being stopped through frame script "go to the frame" (the "car's breaks") that is shown in the frame script channel (aka, the "score script"). No need of sprite scripts and movie scripts yet. Notice that the second set of branches of the tree is not implemented in this file. How would you implement it?
|
|
|
Maintained By: Takis Metaxas
|
|