What is Velosphere-MiniMultiMedia?

Velosphere-MiniMultiMedia is a small program which orchestrates the display of images and text combined with the playing of audio and video. Velosphere follows the slide show metaphor popularized by presentation programs and adds the ability to question the audience/student and record the responses. It can be used in its simplest form to add accompanying text to images, such as recording the location and subject of photographs. Narration (and perhaps music) is easily added to this to create a slide show. Other types of images besides photographs can be used, such as artwork created with the computer or captured graphics such as charts. If desired by the shows author, additional audio, video and text files can be added to the show as supplementary material.

How does Velosphere-MiniMultiMedia work?

Velosphere-MiniMultimedia reads simple text files, referred to as scripts. These scripts tell Velosphere which files to display and in what order. The scripts contain the text which is displayed with each image and on each answer button as applicable. These script files are created using a spreadsheet program, saving the files in the comma delimited format, *.csv, which stands for comma separated values. The files which Velosphere displays do not become part of the script file; rather, the script tells Velosphere where the files are located. Normally, these files will be arranged in subdirectories of the directory/folder where Velosphere is located. Arranging files in this manner simplifies the writing and editing of scripts. More importantly, this arrangement facilitates the transfer of the entire show onto a CD. By copying the entire directory (including the Velosphere executable) onto the CD, the show can be played from the CD on any computer where Velosphere was previously installed. Although Velosphere can be used purely for entertainment or to convey information, one of its strong points is its ability to question its audience. Three types of questions can be asked: TrueFalse, one choice from four, and multiple choices from four. Depending on directions by the shows author, Velosphere may or may not maintain a record of the answers to the questions. In addition, a study mode show can be developed which will display additional frames to alert the student when an incorrect answer has been entered and provide the correct answer in the form of a refresher image and accompanying text.

What is needed to use Velosphere-MiniMultiMedia?

Velosphere-MiniMultiMedia has been tested extensively using Windows 98SE and Windows 2000. Velosphere operates fine on a Pentium 166 with 128 MB of ram under Windows 98SE. Windows 2000 testing was performed using a Pentium III 800 and 512 MB of ram. As would be -1-

expected, the multimedia features were more fluid with the faster processor and more robust multitasking capabilities of Windows 2000. Velosphere has been confirmed to operate on Windows XP Home Edition, but testing was not extensive. Velosphere has not been tested in any fashion with Windows NT, Windows ME, or Windows 95. Velosphere requires a 32-bit operating system; i.e., it cannot operate under Windows versions prior to Windows 95. Velosphere has no capture or editing capabilities of any sort. Generating the script and initialization files requires a spreadsheet program capable of saving in the *.csv (comma separated values) format, also known as the comma delimited format. The necessary files can be reviewed and minor edits performed using Microsoft Notepad(tm) or other ASCII text editor, but attempting creation of the files from scratch using a text editor is not recommended. Many of the features of Velosphere are related to various types of audio, so a sound card and speakers are required. A microphone is required for one of the Tutorials and generally recommended. Show authors will need some method of generating sound files using either a microphone and the Sound Recorder program included with Windows or some other type of program and/or hardware, depending on the authors requirements and preferences. Video and image files will require additional hardware and/or software for their creation, capture, or edit. Velosphere displays video files of the *.avi type. The image types displayed can be *.bmp, *.png, *.jpg, *.fpx, and *.pcx. Due to patent constraints, Velosphere will NOT display *.gif or *.tiff file formats.

-2-

Overview During the past several years, particularly since Y2K came and went, digital capture and editing of sound, still imagery, and video have become mainstream in the consumer marketplace. Besides a proliferation of digital still and video cameras, there are numerous software packages available at reasonable prices to create, capture and edit sounds, images and videos. Most scanners, digital cameras, and color printers come with an image editing software package. The digital music revolution has spawned numerous programs capable of creating and manipulating sounds in all sorts of manner, and many of these programs are readily available to consumers. The point is, a vast majority of the computing population already has software on their computer which is capable of recording and editing sounds and images. Many computer users have software providing video editing capabilities. Velosphere-MiniMultiMedia is not another editor. On the contrary, it is designed to enhance and make use of the software already on the user's machine. It enhances by allowing the user to combine text, sound, and still images together into shows, with facilities provided for including video (*.avi) files. Velosphere-MiniMultiMedia can be used in a variety of manners, including making desktop presentations, building slide shows from photographs, or building multimedia training segments. It is somewhat straitlaced in its manner of presentation: Shows are composed of frames presented in a slideshow manner, each frame displaying an 800x600 pixel image and an accompanying text box of fixed size. These are bordered on the left and right by buttons which control the shows presentation. If desired, the text box can contain a question, and either two or four additional buttons will display at the bottom of the frame, allowing responses to the questions (and recording grades, if desired). Additional files can be attached to each frame of a show: rich text files (*.rtf), sound files (*.mp3, *.wav, *.mid), or video (*.avi) files. These files are displayed by clicking the applicable buttons along the left edge of the frame.

-3-

Watching a Show in Velosphere-MiniMultiMedia Watching a show is straightforward. Velosphere-MiniMultiMedia is started in a similar fashion to other programs on the Windows operating system. If you accepted the default installation, proceed as follows to start the default executable: 1. 2. 3. 4. 5. Click the Start button. Select Programs. Select Velosphere, the subfolder. Select Velosphere, the program. The program will begin.

As part of its functionality, as you develop shows, you may be copying the Velosphere executable file into other subfolders or onto CDs. In this case, using either Windows Explorer or My Computer, locate and double click the executable copy you wish to start. A more convenient method would be to create a shortcut to the executable and put the shortcut in an easily reached location, or even multiple shortcuts to multiple executables, all in a central location. Using whatever method is suitable for your situation, start Velosphere. The opening screen displays three buttons: 1. 2. 3. The top button is captioned I accept the terms of the license agreement. Proceed. Clicking this button starts Velosphere. The second button is captioned View license agreement. Clicking this button opens another window with a text box containing the license agreement. The third button is captioned I do not accept the terms of the license agreement. Exit program. Clicking this button exits Velosphere without proceeding further.

-4-

After clicking the button to proceed, Velosphere displays the Welcome screen. Clicking the large image in the center (Welcome to Our Show) will continue program execution. Clicking the about button will display some information about Velosphere, such as copyright date, version number, and registered licensee.

The next window displayed is a Who are you? window. Although many shows will not be examinations, Velosphere expects every viewer to sign in before watching a show, whether the show is an exam or not. No password is required, so if a viewer chose to sign in under another name, such as Demo Debbie, Velosphere will allow it. Of course, if it is an exam, signing in under a fictitious name will not give that individual credit for taking the test.

-5-

Selecting a name from the list will automatically fill in the boxes labeled ID, Name, and Classification. If an individual is not listed, they may fill in the boxes and click the Update button. The Clear Entries button clears the three boxes. Once the three boxes contain entries by whichever method, clicking the continue button will cause Velosphere to close this identification box and open the show menu. The show menu can display up to forty-four (44) different show titles. Clicking any of the displayed titles will open that show in Velosphere. An exit button is provided at the bottom of the show menu.

-6-

The next window which opens will display the first frame of the show. Velospheres appearance at this point can be somewhat manipulated by the shows author. The control buttons along the left and right sides can be resized or hidden, and the images displayed on the buttons can be changed. In addition, depending on a selection made by the show author regarding question type, Velosphere will display additional buttons at the bottom of the frame which a viewer can select as responses to questions. The following image is of the Velosphere display with the default button images on the forward, back, exit, and return to menu buttons. The resource, music, and video buttons near the top left corner are hidden.

If a show author chooses to do so, the images on the buttons can be changed to most any bitmap image, and button sizes can be changed. The following displays a (dark) image surrounded by button images which form a set of curtains on a stage:

-7-

The following image displays a show frame with additional buttons visible. Besides the Reference button (book icon), Music button (note icon) and video button (video camera icon) there are four buttons at the bottom with possible answers to the question in the text box. The question in this case was identified as being of type 1,2,3,or 4 of 4". If this type of question is asked, the viewer may select more than one answer from the multiple choices. This type of question may be recognized by the check boxes to the left of each answer buttons text.

Each selected answer will have a check mark in the box adjacent to the answer text. Selecting the same text again will deselect the answer and clear the check box. If an author has created a show as a study aid, rather than an exam, the selection of incorrect or incomplete answers will trigger the display of a correction image and correction text.

-8-

The next image is of a frame containing a TrueFalse question:

Selecting an incorrect answer causes the correction window to appear. Note the lack of buttons.

-9-

The third type of question displays four possible answers, but only one of the four may be chosen. This question type does not display check boxes beside the answers on the buttons, but it does display a check mark above the selected answer:

Selecting another answer deselects the previous answer. As before if the show author has chosen to prepare one, a correction frame will display if a viewer attempts to proceed to the next frame without selecting the correct answer. After a viewer has completed a show, one of two windows will appear, depending upon whether the show was designated as an exam or not. If the show is not an exam, the following window will appear at the end:

Clicking the Return to Beginning button will reopen the menu window which displays the various available show titles. Clicking Exit will close Velosphere.

-10-

If the show is designated as an exam by its author, the following window will appear at the end:

Besides the two buttons just described, this window displays the total number of questions, the number of questions answered correctly, and the percentage of questions answered correctly. The display of this window means that Velosphere has recorded the exam results and assigned them to the identity used by the viewer to sign in at the beginning.

-11-

Files, Folders, and More Files Although Velosphere displays a variety of files, it uses simple text files for initialization and directions on how to proceed (scripts). Every copy of Velosphere is programmed to look to an initialization file upon startup. This file, with extension *.vmm, directs Velosphere to a particular set of script files and their folder(s), together with the name of each show, what (if any) images should be shown on the program buttons, and whether responses during a show should be graded and recorded. The initialization file (such as 01 Registered to Demo Debbie.vmm) should be in the same folder as the Velosphere executable file (such as Velospherexxxx.exe or MiniMultxxxx.exe, where xxxx denotes the version). The name of the initialization file cannot be changed by the end user (and still function), varies with individual copies of the program, and is derived from the registered users name. Script files can be located anywhere on the users hard drive, provided a valid path/folder is listed in the previously mentioned initialization file. Generally, the simplest and most direct location is either in the same folder as the executable, or in a subfolder immediately off the executables folder. Each script file corresponds to one show. These files list the text to be displayed on each frame of the show, whether the frame should display response buttons and what text should be on those buttons, what image file should be put on display, what sound file should play upon frame opening, and what additional sound, video, or rich text files should be attached to each frame. Even the simplest shows have files attached, if nothing more than the image files to be displayed in each frame. Attaching sound, video, and/or rich text files can accumulate hundreds of files associated with only one show. It is in the show authors best interest to put these files into specific subfolders. Although attached files are not confined to a specific location, treating either the executable or the script folder as a root folder and locating these subfolders off that root provides a clean, simple, and direct location. This arrangement facilitates transfer of a show to CD (to be played from the CD). Velosphere expects anyone watching a show to identify themselves. A fresh installation of Velosphere will list one individual, Demo Debbie. An individual can enter their own information on their first visit; this information will be available for selection from the list box on future visits. The program will not proceed until an identity is selected. An initialization file, named MiniMultiMedia.ini, lists the name and location of the IDlist file, and the folder and file name for storing records. MiniMultiMedia.ini can be modified by the user, but not renamed. Whenever the *.vmm initialization file denotes a script as an exam file, VelosphereMiniMultiMedia generates/appends two text files. One is specific to a particular instance that an exam is taken, and lists the questions, choices, correct choice, and actual choice, as well as the identity and grade of the individual. This file is named by combining the individual identity with the script name. The other file is constantly being appended (added to) after its initial creation. This records summary file lists each exam taken, by whom, when taken, and what score. This

-12-

files name and the folder for storing both types of generated/appended files are listed in the MiniMultiMedia.ini file. The appearance of Velosphere-MiniMultiMedia can be changed by button dimensions and images in a Button.csv file listed in the *.vmm file. Button dimensions can be adjusted to hide buttons or to accommodate a range of image sizes. Button images can be any bitmap image. A provision allows transparency to be included in the images.

-13-

Editing Velosphere-MiniMultiMedia Files Most users have some type of spreadsheet program. This may be Microsoft Excel 2000, Microsoft Works 2000, or Corel Quattro Pro 10. All of these are capable of saving files in the "comma separated values" (*.csv) format (other spreadsheet programs/versions may or may not be capable of this). These files consist of simple text values in rows and columns, with similar types of values arranged in the same column. Columnar items are separated by commas, as the name suggests. Essentially, this format allows a variety of programs to easily read files created by other programs. Velosphere-MiniMultiMedia reads comma separated value (*.csv) files, allowing the producer of a show to use a spreadsheet program already installed on his or her machine. Thus, no additional space is required for a show editor on the hard drive. However, the downside to this is that the show producer will not be able to create a show with click-and-point ease. At this time, no Velosphere-specific editor is available or under development. Text editors can be used for very minor editing, but they are unwieldy for creating a show from scratch compared to a spreadsheet. As noted in the section of this document entitled Files, Folders, and More Files, Velosphere uses two initialization files, an IDlist file and at least one script file, as well as all of the multimedia files pulled together as the program operates. Additionally, record files are generated by Velosphere when a script is an exam. The initialization files will require some editing, but are simple (due to size) in comparison to script files. Velosphere is capable of developing its own IDlist file, provided a name and location for the IDlist are provided by the show producer. Listed below are the various files and the value types in each column of their contents: The MiniMultiMedia.ini file Path and name of Idlist Path to Records Folder Name of Records File The Registered to Username.vmm file Script File Path and Folder Script File Name Script Title Is this an Exam? Path and name of Buttons File The IDlist file User Number User Name User Classification (in *.csv format):

(in *.csv format):

(in tab delimited format):

-14-

The Button File Left Width Increase Right Width Increase Reference Height Increase Note Height Increase Movie Height Increase Exit Height Increase Start Over Height Increase The Script File Flag 1 Flag 2 Flag 3 Question Type Picture Name Wave File Seconds to Hide Buttons MIDI File Name AVI File Name Rich Text File Name Correction Text Correction Picture Primary Text Answer A Boolean Answer A Tip Answer A Boolean Correct Answer A Answer B Boolean Answer B Tip Answer B Boolean Correct Answer B Answer C Boolean Answer C Tip Answer C Boolean Correct Answer C Answer D Boolean Answer D Tip Answer D Boolean Correct Answer D

(in *.csv format): Reference Image Filename Note Image Filename Movie Image Filename Back Button Image Filename Exit Image Filename Start Over Image Filename Forward Button Image Filename (in *.csv format): Text Wave Folder MIDI Folder AVI Folder Picture Folder Reference Folder Boolean Answered Correctly Flag 4 Flag 5 Flag 6 Flag 7 Flag 8 Flag 9

-15-

Editing Instructions MiniMultiMedia.ini The primary initialization file (MiniMultiMedia.ini) directs the VelosphereMinimultimedia program to the locations of (1) the path and name of an electronic file listing persons who will view shows, (2) the folder for maintaining records, and (3) the name of the master records data file.

Note backslash \ at end of subfolder path. This is required. Registered to (your name.vmm) The secondary initialization file (Registered to UserName.vmm, where UserName refers to the person the software is registered to) provides the VelosphereMiniMultiMedia program menu with the information (show titles) it needs to display. In addition, it informs the program of (1) the electronic file name of each show, (2) the path to the electronic file, and (3) a TRUE/FALSE value indicating whether the results of answers to questions during the show should be recorded in the records datafile. Show titles can be multiple words separated by spaces, but if they contain commas the entire title must be enclosed in double quotation marks. Note the use of the # symbol on each side of the #TRUE# and #FALSE# to denote that these are Boolean values. Drive:\path\Show Folder\ Show script file name Show title #IsExam?# Button images list file name Months until retest Passing percentage Views of UserName.vmm opened in Microsoft Notepad(tm) and in Microsoft Excel(tm). Note backslash \ at end of subfolder path. This is required.

-16-

Script Files Each show file is a comma delimited table, which is read by Velosphere as a script directing it to the various files it should display and telling it what text to show with each image displayed, as well as what text to display on answer buttons if questions are part of the show. Finally, the table contains the correct answers for any questions contained in the script. At the time this is being written, the table is 41 columns wide. Script sizes are as follows: Standard Version of Velosphere: Professional Version of Velosphere: (This is currently the only difference between the versions.) A single Professional Version show can contain 220 different frames of images, text, music, data, and sound files (and ask as many as 220 questions if so desired) and the Standard Version can contain 15. Actually, contain is misleading. Velosphere opens image, video, and sound files which are external to the program itself, and the only information truly contained in the script files for display is text. The script file columns contain the following information, in left to right order: Flag 1 Flag 2 Flag 3 Question Type Picture File Wave file Seconds Music file Movie file Rich text file Repetition text Repetition Picture Primary Text Answer A Text Users Answer A Answer A Tool Tip Correct Answer A Answer B Text Users Answer B Unused at this time. Unused at this time. Unused at this time. 0=no question; 1=option buttons; 2=TF; 3=checkboxes *.jpg, *.bmp, etc. Plays when frame changes (such as narration of text) Music and Video button display delay Can be: *.wav, *.mid, or *.mp3 *.avi only *.rtf can be created by Wordpad, MSWord, Wordperfect Text; Can be used to provide a prompt if an incorrect response is made to a question; otherwise not used. Ditto, except filename of type *.jpg, *.bmp, etc. Shown at the bottom of each frame; can be information or a question. Question type (above) must be chosen to provide capacity for an answer. Displayed on top left answer button #TRUE# or #FALSE#; #FALSE# indicates not yet chosen Hover the mouse over the button and this is displayed #TRUE# or #FALSE#; #FALSE# indicates it should not be chosen. The program will compare the Users answer with this. Displayed on next answer button #TRUE# or #FALSE#; #FALSE# indicates not yet chosen -1715 lines long 220 lines long

Answer B Tool Tip Correct Answer B Answer C Text Users Answer C Answer C Tool Tip Correct Answer C Answer D Text Users Answer D Answer D Tool Tip Correct Answer D Wave File Folder Music File Folder Movie File Folder Picture File Folder Answered Correctly?

Flag 4 Flag 5 Flag 6 Flag 7 Flag 8 Flag 9

Hover the mouse over the button and this is displayed #TRUE# or #FALSE#; #FALSE# indicates it should not be chosen. The program will compare the Users answer with this. Displayed on next answer button #TRUE# or #FALSE#; #FALSE# indicates not yet chosen Hover the mouse over the button and this is displayed #TRUE# or #FALSE#; #FALSE# indicates it should not be chosen. The program will compare the Users answer with this. Displayed on next answer button #TRUE# or #FALSE#; #FALSE# indicates not yet chosen Hover the mouse over the button and this is displayed #TRUE# or #FALSE#; #FALSE# indicates it should not be chosen. The program will compare the Users answer with this. Subfolder of folder containing the script file; location of wave files (column 6 above), such as Wavfiles\. BE SURE TO INCLUDE THE BACKSLASH (but not the quotes). Subfolder of folder containing the script file; location of Music files (column 8 above), such as Midifiles\. BE SURE TO INCLUDE THE BACKSLASH (but not the quotes). Subfolder of folder containing the script file; location of Movie (*.avi) files (column 9 above), such as AVIfiles\. BE SURE TO INCLUDE THE BACKSLASH (but not the quotes). Subfolder of folder containing the script file; location of wave files (column 3 above), such as Graphicfiles\. BE SURE TO INCLUDE THE BACKSLASH (but not the quotes). #TRUE# or #FALSE#; set to #FALSE# by show or exam author, Velosphere will set to #TRUE# internally if a user completes an exam and the question has been answered correctly. Unused at this time. Unused at this time. Unused at this time. Unused at this time. Unused at this time. Unused at this time.

-18-

Remember: 1. Boolean values begin and end with the # symbol, as #TRUE# or #FALSE#. 2. The items listed are columns in a table, as illustrated below by the first dozen columns and part of another:

3. Text (Repetition Text, Primary Text, Answer Text) is entered directly into the table and is part of the script file; it is not contained in separate files. As you fill out a table, the easiest place to make a mistake (except for misspelling) is the improper use of drive letters or backslashes when declaring the subfolders. VelosphereMiniMultiMedia does NOT expect a drive letter or backslash at the beginning of a folder name. It DOES expect a backslash at the end of a folder name, such as: Show15\moviefiles\ LongAndLonesomeHighway\images\

At the beginning of program execution, initialization information is expected to be in the same folder as the executable file (minimult.exe), specifically the Registered to *.mmm (where * represents the registered user) and the MiniMultiMedia.ini files. The Registered to file contains a list of the script filenames and can also contain a list of the subfolders where the script files are located. It is not necessary for the script files to be in a different subfolder than the minimult.exe file; however, it is generally good practice to separate data files of any sort from their associated program. Once a show has been chosen from the menu window (the window with 44 buttons, some or all displaying show titles), if a folder was NOT specified, the current folder will be assumed by the program to be the same one it started in. If a folder was specified in the MiniMultiMedia.ini file and the show started from this new subfolder, then the new subfolder will be considered to be the current folder. Whichever is the current folder, ALL SUBFOLDERS LISTED IN THE SCRIPT FILE WILL BE CONSIDERED TO BE SUBFOLDERS OF THE CURRENT FOLDER, and the current script file will be in the current folder. -19-

When a show is loaded into memory, the subfolders listed in the script file are appended to the current folder. Thus, if the chosen show title is The Finest Script Written and its associated script file is FinestWritten.csv in the subfolder C:\Programs\MiniMultiMedia\MyShows\Finest Written\, then the following will occur: If *.avi files are in movies\, one of those is named Birthday8.avi, and its turn has been reached in the FinestWritten.csv script, clicking the movie button will cause the program to open and play the file: C:\Programs\MiniMultiMedia\MyShows\Finest Written\movies\Birthday8.avi. Note: all *.avi files do not have to be kept in the same subfolder, but the correct location must be specified, and that location must be a subfolder of the folder containing the script file. The same holds true for the other files opened by the program, such as *.rtf, *.wav, *.mid, *.bmp, *.jpg, etc. Subfolder names can be whatever you like (within operating system constraints), but their location and the use of the \ backslash character must be as specified in the preceding paragraphs. Program control is largely related to the existence (or nonexistence) of image files. A primary image is expected for each frame displayed by clicking the forward button. If an image file is not named for display (in the Primary Image column of the script file), then Velosphere assumes that the show is over and loads the ending routine. A similar approach is used when a show includes questions to be answered by the user. If an image is supplied in the column described earlier as Repetition Picture, then the image and associated text will be displayed if a question is answered incorrectly. If a Repetition Picture is not specified for display, then nothing will be displayed in response to a wrong answer and the program will continue to the next frame. Another method whereby a script file controls program execution is by the integer value entered in the Question Type column. The integer value of 0 will cause the program to display only the text box containing the sentence(s) typed in the column Primary Text, and no answer buttons. An integer value of 1 causes the text box to be moved upward and four buttons to be displayed below it. These are labeled with answers to the question in the text box; only one of the answers may be chosen. Choosing an answer causes a small checkmark to become visible above the answer and the button to appear depressed. An integer value of 2 causes the text box to be moved upward and two buttons to be displayed below it. These are routinely labeled with True and False, but the show author may choose other labels; only one of the answers may be chosen. Choosing an answer causes the button to appear depressed. An integer value of 3 causes the text box to be moved upward and four buttons to be displayed below it. These are labeled with answers to the question in the text box; more than one of the answers -20-

may be chosen. Choosing an answer causes a small checkmark to become visible in the small box beside the answer and the button to appear depressed. In summary: 0: 1: 2: 3: denotes a statement denotes a question of type 1 of Four denotes a question of type True / False denotes a question of type 1,2,3, or 4 of Four

The script file column previously denoted as Seconds contains a numeric value which controls the display of two buttons: the Note button and the Camera button. Although multiple media players are called by Velosphere, behavior of two or more players attempting to perform identical functions simultaneously is unpredictable (the players are better behaved under Windows 2000 than Windows 9x). The Camera and Note button remain hidden if no file is named to be opened in a particular frame. If a *.avi file is named in the script file, then the Camera button will be displayed. The display of the button will be delayed by the number of seconds entered in the Seconds column. The amount of time should approximately equal the amount of time required for the *.wav file played upon frame change to nearly finish. The same effect occurs with the Note button: if no *.mid, *.mp3, or *.wav file is in the script file, the button is hidden, otherwise it will become visible after the number of seconds entered in the Seconds column. Camera button delay is unnecessary if the *.avi is silent; nevertheless, it will be delayed if a time is entered to delay the display of the note button. The script file columns containing the Boolean values #TRUE# and #FALSE# should initially be filled with #FALSE# when beginning to author a new show. Then in the columns previously described as Correct Answer A, Correct Answer B, Correct Answer C, and Correct Answer D all of the cells corresponding to correct answers should be changed to #TRUE#. The script file column described as Answered Correctly? should be filled with #FALSE#. If an author has some reason to mark the question as answered correctly prior to the user viewing the show, it will work, but the Users Answer A, Users Answer B, Users Answer C, and Users Answer D will also need to be marked correctly to avoid erroneous data. In effect, this would be pre-marking the answer. If the shows author has listed a Rich Text File (*.rtf ) for display with a given frame, a button with a book graphic is displayed in the upper left corner of the show frame (no delay column for this button). Rich Text Files can be created by a number of programs, particularly mainstream word processing programs. These files can display a variety of text formats and graphics. One cautionary note: including more than one high color graphic in the same *.rtf may result in a file which will display so slowly the user will believe the program is locked up. A typical response by the user is to start clicking -21-

buttons haphazardly while the file is still attempting to load. This random clicking probably WILL result in the program locking up. Buttons File If an author desires, the button images of the primary display window can be changed for a show. The button sizes can also be changed to a certain extent to accommodate various size images or completely hide certain buttons. The generic primary display window has seven visible buttons, although the reference, music, or camera button will not display if an applicable file is not available. Four of the seven buttons are along the left side of the window, and three are along the right side. The width of all of the buttons along the left side may be reset simultaneously, but not individually. Similarly, the width of all of the buttons along the right side may be reset simultaneously, but not individually. Button heights may be reset individually, to a point. The forward and the back button are on the bottom of the right and left side respectively. These buttons change height automatically based on the height adjustments chosen for the buttons above them. The height can be either increased or decreased for the other buttons (reference, music, camera, exit, return to menu) within a range of values. The following table lists the minimum and maximum adjustment values which may be used for the buttons: Minimum Adjustment* Left Width Right Width Reference Height Music Height Movie Height Exit Height Start Over Height Back Height 0 0 => -480 => -450 => -450 => -980 => -410 automatic (Exit+Start Over) <= 3760 automatic Maximum Adjustment (Left Width+Right Width) <= 5416 (Reference+Music+Movie) <= 3755

Forward Height automatic automatic *Regarding negative values: For example, the reference button can be hidden by setting to -480, but setting to -481 will cause an error and shutdown the program.

-22-

A button file is generated by the show author using a text editor or spreadsheet. This file is one-dimensional, so it may be generated either horizontally (comma delimited) or vertically as a single column of text with no commas. The following table lists values in the necessary order: ADJUSTMENT
LEFT WIDTH RIGHT WIDTH REFERENCE HEIGHT NOTE HEIGHT MOVIE HEIGHT EXIT HEIGHT START OVER HEIGHT REFERENCE IMAGE NOTE IMAGE MOVIE MAGE BACK BUTTON IMAGE EXIT IMAGE START OVER IMAGE FORWARD IMAGE

SAMPLE VALUE 500 500 300 500 800 500 500 Glasses.bmp Instrument.bmp BigCamera.bmp Previous.bmp GetOut.bmp Menu.bmp NextPicture.bmp

The same image may be used on multiple buttons if desired. The following is a sample file in vertical format:

-23-

Records Files

(These are edited by Velosphere, not the show author)

Three records files are associated with Velosphere-MiniMultiMedia. One is a list of individuals who will be users of the shows (members of the audience, not show authors). Although shows do not necessarily ask questions or grade responses, the software will still request that an individual be identified. A fictitious character (Demo Debbie as of this writing) is automatically inserted in the list box during the first use of the software. If a user does not wish to be identified, the fictitious character can be selected. If an individual wishes to be identified but is not in the list, the program provides the means to add an individual. The ID list is stored in a simple ASCII text file and the name and folder location of that file is declared in the primary initialization file (MiniMultiMedia.ini). The format of the file is tab delimited; that is, each row is a record and the items on each row are separated by tabs.

The various entries can be composed of any alphanumeric characters (no tabs), with single spaces between words and true tabs between entries. As mentioned, Velosphere creates the file and/or adds entries to it. After a user has completed a show designated as an exam in the secondary initialization file, Velosphere-MiniMultiMedia will grade the responses given to the questions. Two records will be created. One is a file containing all of the questions, the possible answers, the correct answers, the users answers, and the date, together with the users grade and classification information. A new file is created every time an exam is completed by another user. These files are stored in subfolders created by the program. Each subfolder name is a combination of the user ID number and user name. These subfolders are created in the folder designated in MiniMultiMedia.ini for record storage. The files all have the extension *.graded and begin with the users ID number; between these is the name of the show/exam file, such as: -24-

1474_NewMultimediaII.csv.graded

The other record is a tab delimited file containing the users name, ID, exam file name, grade, date and classification. This file is appended as additional exams are taken by any user, as long as the initialization file (MiniMultiMedia.ini) remains the same.

-25-

Tutorials
Preparing scripts for Velosphere is relatively simple for those accustomed to typing on a computer, but can be less so for those who prefer working through selections with a mouse. The tabular nature of the scripts lends preference to organizing files into directories (folders). The advantage of this is that shows can be packaged up onto CD's after editing is complete by simply copying the applicable directories onto a formatted CD. The following tutorials demonstrate one method of organizing files into directories; other methods may be used. Although the image, sound, and video files remain external to Velosphere proper and do not actually cause a show to grow, many media files are quite large, and authors are encouraged to plan ahead for moving completed shows to CD. The tutorials are numbered in a recommended sequence of learning. Students should review the example scripts which correspond to each tutorial. Tutorial 1 is simply setting up a basic slide show composed of pictures with accompanying text. The images used in the tutorial are simple shapes (circle, square) and colors (red, blue, green) which can be created with nearly any graphics program. Any images could be used, but later tutorials build on this one and include questions concerning color and shape. The main things a student should learn from this tutorial are (1) how to use a spreadsheet program to create a *.csv file and (2) the correct order of entries into the script file. Although Tutorial 1 creates a simpler show than those which follow, it can easily take the longest since the script file is being built from scratch. Later tutorials continue to build on this original file. Tutorial 2 introduces narration (sound) into the script. These simple *.wav files can be created with the "Sound Recorder" which comes with 32-bit Windows (Win 95 and later). This program can generally be found under Programs>Accessories. Of course, other programs may be used for this, provided they can save in the *. wav format. A later tutorial introduces the method for playing other sound formats (MIDI and *.mp3). Tutorial 3 demonstrates the use of Velosphere for development of training/educational materials. In this tutorial, additional frames are inserted into the show to allow the author to quiz the student during the show. The text and sound files accompanying the frames ask questions, and buttons with choices for answers are displayed at the bottom of the window. Also demonstrated in this tutorial are the use of repetition frames which pop up if a student answers incorrectly. Tutorial 4 introduces video into the script through the use of *.avi files. Although this file type is somewhat outdated by file types exhibiting higher compression, short clips using commonly available compression (such as Indeo(tm)) can be fun, interesting and informative. If extensive video is needed, the show author should consider creating a pure video show and forego the slide metaphor. There are numerous video editing programs on the market at reasonable prices. Of course, pure videos do not lend -26-

themselves to the same electronic testing style as Velosphere. The video used in the tutorial are simply the still images used since Tutorial 1 strung together into an animation, with some effects added to the screen changes. Other video files may be used. Tutorial 5 introduces music into the script file. The *.wav file used for narration (introduced earlier) plays in response to frame changes. Other sound files can be included which play in response to the press of a button on each frame. These files can be *.mp3 or MIDI files, as well as *.wav files. The sound files used in the tutorial are the same spoken words used for narration, except they have been converted into *.mp3 files from the *.wav format. Other sound files may be used. Tutorial 6 introduces the use of *.rtf files (rich text files) to provide additional reference material to accompany a particular frame. Generally, an author is encouraged to simply use another frame if it is desired to show another image, but *.rtf files can display images as well as text. The use of rich text files containing multiple high color images is not recommended with Velosphere. Tutorial 7 demonstrates the reduction of a show script down to only the questions, but retains the repetition frames which pop up with the correct response if a student answers incorrectly. Such a script could be used for a refresher or as a study quiz prior to an actual test. Tutorial 8 further reduces the script from Tutorial 7 to questions WITHOUT the repetition frames. This is essentially all there is to creating a test, except for indicating that the script is an exam in an initialization file. If the initialization file indicates a script is an exam, then the student responses are recorded and graded, whether the script contains repetition frames or not. A second initialization file is reviewed to verify that the record files are stored in the correct location on the hard drive. Hopefully working through these tutorials helps the budding script writer to understand the nuts and bolts of using Velosphere sufficiently to prevent the software getting in the way of the creative process.

-27-

Tutorial 1 Tutorial 1 is simply setting up a basic slide show composed of pictures with accompanying text. The images used in the tutorial are simple shapes (circle, square) and colors (red, blue, green) which could be created with nearly any graphics program. Any images could be used, but later tutorials build on this one and include questions concerning color and shape. The main things a student should learn from this tutorial are (1) how to use a spreadsheet program to create a *.csv file and (2) the correct order of entries into the script file. Although Tutorial 1 is simpler than those which follow, it can easily take the longest since the script file is being built from scratch. Later tutorials continue to build on this original file. First of all, one needs a spreadsheet program which can save files in the *.csv filetype. This type of file is a simple text file, with entries separated by commas, hence Comma Separated Values, or csv. Most modern spreadsheets are capable of this, such as Microsoft Excel 2000, Corel Quattro Pro 10, and Microsoft Works 2000 (earlier versions may or may not have this ability). When saving a prepared file, the author needs to select File>SaveAs and then select the *.csv file type. One of the quirks about doing this is the spreadsheet program may give multiple warnings about saving as this file type. These include the following (paraphrased): 1. "Warning: this file type will cause you to lose all of your formatting! Are you sure you want to proceed?" Answer: Yes 2. "Warning: this file type does not support multiple page workbooks; only the current page will be saved! Are you sure you want to proceed?" Answer: Yes The following one is more common and happens when you edit an existing file and save it. But it can also happen when you attempt to close or exit a *.csv file, because the spreadsheet program REALLY wants to save the file in its native format: 3. "Do you want to save this file?" Answer: You will soon learn to answer No when applicable (i.e., you have saved already or you want to discard your changes). Yes is fine, even if you have already saved your work. However, answering Yes will lead you through the SaveAs dialog, where, after you pick the same filename, you will be met with the following common error message: 4. "Warning: a file with this name already exists! Are you sure that you want to copy over it?" -28-

Answer: Yes, unless you want to create a new file. If so, you should type in a new name. If you answer Yes to #4, you may once again be greeted with warnings #1 and #2. Although startling if not forewarned, these warnings are nothing to be concerned about, only dealt with. If your spreadsheet program does not give these warnings, consider yourself fortunate. It is advisable to practice saving as *.csv a few times with a small file of no value. Also, open the created file in Notepad or other text editor to see what it looks like. One of the more aggravating things a spreadsheet program may do is switch text formats from comma delimited to tab delimited. (Actually, this is a user error, caused by selecting a text format in too great of a hurry.) Unfortunately, this will not be obvious from the spreadsheet program unless another save is performed. However, open the file in a text program and the problem will be obvious. Although Velosphere creates tab delimited files, it cannot read them. Generally Velosphere can read a file while it is still open in the spreadsheet program, but Velosphere will only read saved files. However, Velosphere cannot write to records files when a student takes an exam if the record files are concurrently open in another program. After verifying that your chosen spreadsheet program can indeed save to the *. csv format, open a new file. In the first row of cells, enter the column headings following this paragraph. (It is generally OK to use formatting at this point if you wish, but you need to experiment by opening a saved *.csv file with Notepad or similar text editor; some formatting may introduce extraneous commas or tabs. When you save the file, the formatting will be lost the next time you open it.) It is a good idea to save the file in the spreadsheet program's native file type while composing a show, and then save the first cut as a *.csv to see how it looks in Velosphere. One advantage of this approach is that multiple scripts can be saved as separate sheets in a workbook saved in native format; whichever sheet is active while saving will be saved in the *.csv format. Flag 1 Flag 2 Flag 3 Question Type Picture File Wave file Seconds Music file Movie file Rich text file Repetition text Repetition Picture -29-

Primary Text Answer A Text Users Answer A Answer A Tool Tip Correct Answer A Answer B Text Users Answer B Answer B Tool Tip Correct Answer B Answer C Text Users Answer C Answer C Tool Tip Correct Answer C Answer D Text Users Answer D Answer D Tool Tip Correct Answer D Wave File Folder Music File Folder Movie File Folder Picture File Folder Answered Correctly? Flag 4 Flag 5 Flag 6 Flag 7 Flag 8 Flag 9

As mentioned, the above headings should be listed across the top of the spreadsheet columns, beginning with the first column, as shown:

Although it is not necessary to use exactly these titles (or even use titles), you should use these for a while (during the Tutorials) before you make up you own. You will delete these as a row before saving your script as a *.csv file, so put all of the title entries into a single row, using wordwrap if desired.

-30-

Before we go on, save your new file in the spreadsheet programs native format, such as *.xls for Microsoft Excel 2000 or *.qpw in Corel Quattro Pro 10. Now, lets begin scriptwriting. The columns titled flag#, where # represents a single digit, should contain zero as their entry. These are more or less ignored by Velosphere and can contain any text, but zero is easier for the show author to ignore. These columns are set aside for future upgrades to Velosphere. [Note: If you know how to sort with a spreadsheet and you author an exam, you can insert random but non-repeating numbers in one or more of these columns to re-sort and change the order of your exam questions.] In Tutorial1 we are not going to ask questions, so put zero in the column titled Question Type. This simply means do not display answer buttons of any type. The pictures we are using are very basic, and so shall be the names of the files. As mentioned, the images used in the tutorial are simple shapes (circle, square) and colors (red, blue, green) which could be created with nearly any graphics program. For file names, we will use: GreenSquare.png RedSquare.png BlueSquare.png GreenCircle.png RedCircle.png BlueCircle.png

[Please note: The filenames listed indicate the *.png image format. Velosphere is capable of displaying numerous image formats, but it is NOT capable of displaying *.gif or *.tif images. Velosphere can display *.jpg, *.png, *.bmp, *.fpx, and *.pcx formats. Generally, you will use *.jpg for your photos and *.png for your drawn graphics, but please experiment. Velosphere is designed to show 800x600 pixel images; smaller images will be centered, and larger images will align at the top left corner. Although photos may not necessarily resize well, they can often be cropped with good results. Note that image compression (and loss of quality/information) takes place every time you save a *.jpg image, so do all of your editing before saving to maintain quality, and keep a copy of the original.] Tutorial1 is not going to use sound, so we do not need to list *.wav file names. This column may be filled with zeros. Leaving blank is OK, but zeros are easy to recognize for a visual cue when examining a file in a text editor. The column titled Seconds is not being used in this tutorial; entering 3" now will have it set up later when we introduce more multimedia file types. No music files will be used in Tutorial1; enter zero in this column. No *.avi movie files will be used in Tutorial1; enter zero in this column. -31-

No *.rtf rich text files will be used in Tutorial1; enter zero in this column. So far we have completed the following columns:

We will now continue these six rows across the table, left to right in columnar order. Since we are not asking questions and, hence there will be no incorrect answers, no entries will be made in the Repetition text column. For the same reason, no entries will be made in the Repetition Picture column. The next column, Primary Text, will have entries which match the picture files. These entries will describe the picture files listed earlier, as shown in the following image. We have now completed the following additional columns:

Note that repetition text and repetition picture do not have entries. Using entries in these columns will tell Velosphere to display a repetition window, which we do NOT want at this point. The next sixteen columns all relate to answering questions; that is, they correspond to the various buttons shown when questions are asked by the show author. Since there are no questions, it may be tempting to fill all of these with zero, but a better plan is to consider all of the answers to be false. This will vastly simplify the editing of this show in later tutorials (and, generally, ALL shows) as we add questions and eventually create a test. Also, the Boolean values must always be either #TRUE# or #FALSE#. You can use autofill or copy/paste in your spreadsheet program to fill in columns with the same values. Use zero for the answer text columns, and This is false for the tool tip columns.

-32-

Fill the columns as follows, remembering the # signs to indicate Boolean values:

The next columns specify what folders Velosphere should look in for the various files it plays or displays. Generally, these will repeat throughout their respective columns. Folder names can be whatever is acceptable to Windows, but use the ones which follow for the Tutorials. Pay particular attention to the use of the backslash character.

The column Answered Correctly should always be filled with #FALSE# as follows:

During a show which asks questions, Velosphere will change these values in memory to #TRUE# when a question is answered correctly. Those correct answers are totaled for a grade if a show is designated as an exam in the initialization file. -33-

The remaining columns are flag# columns, which were filled with zeros earlier:

Now our script is complete. First, save the file in the spreadsheet programs native format as we did earlier. Now, delete the first row, containing the titles of the columns. This will move the second row, which is the first row of the actual script, into the first row position.

Choose File>Save As from the menu and save the file as Tutorial1.csv, paying attention to the folder location to which you are saving. If you have already copied a file by the same name from the Velosphere distribution disk, you may wish to change the name to avoid overwriting that file.

-34-

Tutorial 1b
Okay, now we have saved our first script, but we are not quite ready to let Velosphere read it. For one thing, Velosphere needs to know where to look for the script. Second, the files and their respective folders specified by the script need to be created. Third, (this will be applicable later) we should tell Velosphere where to store records if the script is an exam. Now, lets create our own folder structure. Depending on your choices during installation, Velosphere may be installed in the following path: c:\Program Files\Velosphere\velosphere.exe Velosphere searches the folder where the executable is located for its initialization files. Other files, such as the script files and multimedia files, can be located in other subfolders. So, assuming that the above path is where we are starting from, let us create the following subfolders: c:\Program Files\Velosphere\ScriptFiles\ c:\Program Files\Velosphere\ScriptFiles\Buttons c:\Program Files\Velosphere\ScriptFiles\MIDIfiles c:\Program Files\Velosphere\ScriptFiles\Movies c:\Program Files\Velosphere\ScriptFiles\Photos c:\Program Files\Velosphere\ScriptFiles\ReferenceFiles c:\Program Files\Velosphere\ScriptFiles\WavFiles c:\Program Files\Velosphere\RecordFiles The method we use for passing information to Velosphere is through initilization files. For most programs, initialization files use a standardized single column format. Initialization files in our case are simple text files, with the individual pieces of information separated by commas, much like the script file just created. However, the initialization files are generally smaller than the script files. There are two files which initialize Velosphere. One tells Velosphere where to store exam results and names of individuals viewing shows. This file is named MiniMultiMedia.ini and contains three values: the path and filename of the list of individuals who view shows, the folder for storing record files, and the filename to use for storing a summary of the records. [Velosphere creates other record files besides this summary for each individual and test taken; those filenames are created by Velosphere based on exam name and individual name.] To summarize, MiniMultiMedia.ini contains: Viewer List, Records Folder, Records Name. The Viewer List will apply to all shows, whether exams or not. If the Viewer List does not exist, Velosphere will create it. Demo Debbie will be the first entry. Velosphere can accept filename extensions of more than three characters. The following is an example of entries into a MiniMultiMedia.ini file (note commas): c:\program files\minimult2\MNM_Records\idlist.txt, c:\program files\minimult2\MNM_Records\, Records.other If you want Velosphere to create the viewer list from scratch, leave the first entry blank, as: ,c:\program files\minimult2\MNM_Records\,Records.other but be sure that the leading comma is in the file. The viewer list file is a three column, tab delimited text file. Now let us create a MiniMultiMedia.ini file which matches our folder structure. One of the subfolder paths we just created is: c:\Program Files\Velosphere\RecordFiles\

-35-

This path is where we would like to have our records stored if we write an exam, and where we would like to store the list of individuals viewing our shows. We will let Velosphere create the list as individuals log in, so we will leave the first entry (viewer list) blank. For our current purposes we will name the records summary file Records.other. The MiniMultiMedia.ini file can be created using either a text editor or a spreadsheet program (saving as *.csv filetype). Since this file is so simple, it is probably easiest to use Notepad or similar ASCII text editor. The following is the text contained in our completed MiniMultiMedia.ini file: ,c:\Program Files\Velosphere\RecordFiles\,Records.other Save MiniMultiMedia.ini in the same subfolder as Velosphere.exe: c:\Program Files\Velosphere\MiniMultiMedia.ini Put the script file created earlier, Tutorial1.csv, in the ScriptFiles subfolder: c:\Program Files\Velosphere\ScriptFiles\Tutorial1.csv The other initialization file we need to be concerned with has a different name for each licensee. The name of the file must always be the same and contains the name of the licensee. Suppose that the name of the licensee is Demo Debbie. Then the name of this initialization file may be: 01 Registered to Demo Debbie.vmm From here on we will refer to this file as the vmm file. This file is another comma delimited text file and may be up to 44 lines long, each line corresponding to another show. The entries in this file are used to fill out the menu where an individual viewer may select which show to watch. The following is an example vmm file with column headings added for clarity:

The Script File Folder instructs Velosphere where to look for the chosen script. Note the use of the backslashes in this case. The Script File is the file name of the chosen script. The script file we wrote earlier was named Tutorial1.csv The Script Title is what is displayed on the menu. Take care here with punctuation. If you use a comma in the title, most spreadsheet programs will save the title in quotes (in the *.csv format) to indicate a single entry, but you need to verify that this takes place. Otherwise, when reading the file Velosphere will assume the part of the title following the comma is a separate entry which belongs under the Exam? heading and generate an error because it is not Boolean. Note that if you create/edit the file using a text editor you will need to insert any required quotes yourself.

-36-

The column titled Exam? contains Boolean values (#TRUE# or #FALSE#) indicating whether or not a show is an exam; #TRUE# indicates question responses should be recorded and graded. Buttons Files list different images which a show author may use to change the appearance of Velosphere. These will be explained in a later Tutorial. Years to Retest is a specialized entry for some training/qualification applications. Fractions may be used to indicate months. The Passing% column indicates the percentage a show viewer must answer correctly to pass an exam. Although this has no real value unless the Exam? Column contains #TRUE#, it is generally simpler and clearer to fill the column with a fraction rather than with zero. Note that 0.7 corresponds to 70%. Our file will appear as follows in a spreadsheet program:

The headings must be deleted before saving in the *.csv format. Note that the file will have to be renamed to end with .vmm rather than .csv at some point before use. This file is saved in the same manner as the script file was done earlier. First, save the file in the default file type for the editor you are using, whether spreadsheet or ASCII text editor. Second, the top row (column headings) must be deleted. If you are using a text editor and the items are already comma delimited, like so: \ScriptFiles\,Tutorial1.csv,Tutorial #1,#FALSE#,0,0,0.7 simply save with the applicable name (required by your license), as: 01 Registered to Demo Debbie.vmm If you are using a spreadsheet program, save the file using the *.csv format as you did the script file earlier. In the spreadsheet program, you may be forced to accept the csv extension on the filename, such as 01 Registered to Demo Debbie.vmm.csv. You can rename the file after it is closed to match the filename required by your license. This file should be saved in the same folder as Velosphere.exe, as: c:\Program Files\Velosphere\01 Registered to Demo Debbie.vmm Now, the only files remaining are the files to be displayed by Velosphere.

-37-

Tutorial 1c
Except for text contained in the script file and titles contained in an initialization file, everything displayed or played by Velosphere is in separate files and not actually contained in either the program or the script. The most important of these external files are the image files. The existence of an image file continues show progression; once the last image is reached, the show ends. Velosphere is designed to display 800x600 pixel images and images will display at actual size; smaller images will display in the center of the image window; larger images will be truncated. Velosphere will display a variety of image types: *.png, *.jpg , *.bmp, *.fpx, and *.pcx. Velosphere will not display *.gif or *.tif formats. Our tutorial uses simple color drawings and does not use photographs. As mentioned earlier, we are creating circles and squares in one of three colors: red, green, and blue. The following table lists the required images and filenames.

BlueCircle.png

BlueSquare.png

RedCircle.png

RedSquare.png

GreenCircle.png

GreenSquare.png

-38-

Create these six files and save in the folder created earlier:
c:\Program Files\Velosphere\ScriptFiles\Photos

[Note: If your graphics program cannot save to the *.png format, you can save to the *.bmp or another supported format and use the appropriate filename here and in the script file created earlier (Tutorial1.csv).] So, now you should have the following six files:
c:\Program Files\Velosphere\ScriptFiles\Photos\GreenCircle.png c:\Program Files\Velosphere\ScriptFiles\Photos\GreenSquare.png c:\Program Files\Velosphere\ScriptFiles\Photos\BlueCircle.png c:\Program Files\Velosphere\ScriptFiles\Photos\BlueSquare.png c:\Program Files\Velosphere\ScriptFiles\Photos\RedCircle.png c:\Program Files\Velosphere\ScriptFiles\Photos\RedSquare.png

Finally, we are ready to try out our show! If Velosphere is not displayed on your start button, go to c:\Program Files\Velosphere\ and double click Velosphere.exe. If you get an error message immediately, open your initialization files created earlier (MiniMultiMedia.ini and Licensed Name.vmm) and verify that there are no extraneous commas or quotes and that the individual elements are separated by commas, not tabs. The best way to perform these verifications is to open the files in Notepad or similar ASCII text editor. Also, check the spelling of the filenames. If everything works according to plan, the following should appear:

Please click the button labeled View License Agreement and read the license. Upon satisfaction that the terms are acceptable, exit the license window and click the button labeled I accept the terms of the license agreement. PROCEED. This will start Velosphere and display the following window:

-39-

If you wish, you may click the button labeled About Velosphere. Otherwise, click the button labeled with the graphic Welcome to Our Show. This will display the What Is Your Name? window:

This is a fairly typical data entry box. You only need to fill it out the first time you use Velosphere. If you prefer to not be identified, simply choose Demo Debbie as your identity:

-40-

Click the continue button. This will display the menu window, which will list the show title(s) listed in the initialization file created earlier (If you are following along with Tutorial 1, your window will only list Tutorial #1 as a selection.):

Click the button labeled Tutorial #1". This will start the script we created earlier and display the first image and associated text:

-41-

No sound is played at this point because we do not create sound files in Tutorial 1. However, normally a sound file can be played at each image change. We will refer to each window like that above as a frame, with a different frame corresponding to each line in the script file. Now, hover the mouse over the different parts of the frame. Tiny help notes, known as Tool Tips, will display for each portion. Clicking the tall buttons on the left and right edges with the multi-arrow image cause the show to either progress forward or go back a frame, and their tool tips reflect this. The button with the curved arrow returns to the menu. The button labeled EXIT will cause Velosphere to close. The following screen shot shows the tool tip displayed when the mouse is hovering over the main picture. Clicking the main picture will cause the show to progress forward one frame.

-42-

After all of the frames of this (non-exam) show have been viewed, the following image will be displayed. Clicking the Exit button exits Velosphere. Clicking the Return to Beginning button will return to the menu window and allow the viewer to choose another show to watch, if one is available, or to repeat the same show.

If the show is specified as an exam in the initialization file, then the responses to the questions are totaled and the following window is displayed when the show is completed:

By the time you have completed Tutorial 8 you will know how to create an exam. This completes Tutorial 1. KEEP ALL OF YOUR FILES-DO NOT THROW THEM AWAY! You will need them in the tutorials which follow.

-43-

Tutorial 2
You should complete Tutorial 1 before starting this tutorial. The files created in Tutorial 1 are required for this tutorial. Previously (in Tutorial 1) we developed a show which displayed images and accompanying text. In Tutorial 2 we will add sound to our slide show in the form of narrations which match the text. There are numerous sound recording programs on the market, but in this tutorial we will use the Sound Recorder program which comes with Microsoft Windows. In Windows 98 and Windows 2000 Professional this program can be reached under the Accessories item on the Start menu: Programs>Accessories>Entertainment>Sound Recorder This program records sounds if a microphone and sound card are installed. Nearly all computers now include a sound card which is suitable, but you may have to track down a microphone. Any computer microphone (which will plug into your sound card or USB port) will be adequate for recording speech. If you plan to use it for other purposes, such as speech recognition or music, you should do additional research before your purchase. Sound Recorder saves sound in the *.wav format. To keep things simple, we will use the same naming convention for our sound files that we used with our image files earlier. That is, we will use the following filenames: BlueCircle.wav GreenCircle.wav RedCircle.wav BlueSquare.wav GreenSquare.wav RedSquare.wav

As you may recall, our script file specified the following six lines of text to be displayed with their corresponding image:

We are going to read each of these sentences into the Sound Recorder via our computer microphone. -44-

Lets get started. Click your Start button, then select: Programs>Accessories>Entertainment>Sound Recorder or whatever path exists on your particular machine. Note that the Sound Recorder program, sndrec32.exe, is actually in the Windows path, but there should be a shortcut installed under the Start Menu>Programs path. Sound Recorder presents five buttons and a slider; the buttons are similar to a tape recorder. Clicking the button labeled with a circle (the Record button) starts the recording process. Clicking the button labeled with a square stops recording. Hovering the mouse cursor over a button causes a tool tip to pop up which names the buttons purpose. Lets record the first sentence. Click the record button on the Sound Recorder and immediately begin speaking. Wait a short fraction of a second after speaking to click the stop button. The reason for the wait is that some hardware setups will produce an audible click when clicking the stop button. By waiting briefly you leave a portion which can be easily deleted from the file, removing the audible click. After you stop the Sound Recorder, click the Play button and listen to your sentence. Sound Recorder allows you to cut off either end of a file for editing purposes, but if that is not sufficient, simply record the same sentence again and toss the first file.

Repeat for each of the six sentences, saving each file with the filenames listed earlier, respectively. Now, open the script file created earlier and save it with a new name. It would probably be a good idea to use the file created in the spreadsheet programs native format so you can have access to the column headings. Go to the column labeled Wave Files and enter the filenames of the sound files you just created, being careful to enter each (correctly spelled) filename into the correct row to correspond to each image:

-45-

Be sure that the files are in the correct subfolder. If you have used the folder setup described in Tutorial 1, the *.wav files you just created need to be in the following folder: c:\Program Files\Velosphere\ScriptFiles\WavFiles Save your new script as Tutorial2.csv, following the same instructions listed in Tutorial 1 for creating *.csv files. This new script needs to be saved into the same folder as the Tutorial1.csv file, c:\Program Files\Velosphere\ScriptFiles\ and the LicensedName.vmm file needs to be updated to display the new show on the Velosphere menu window:

As noted earlier, be careful when saving your files to be sure that the *.csv format is selected. Simply selecting text is probably wrong since tab delimited is considered a text format as well and is usually the default chosen by the spreadsheet program for text. Also, do not forget to delete the column headings before saving as *.csv. There is no need to edit the MiniMultiMedia.ini file; we will plan to locate any records in the same folders and files as previously specified. Now, start Velosphere and watch the show Tutorial #2". This time, sound should accompany each new frame and narrate the show. If the show appears correctly but there is no sound, check to be sure that your computer can produce sound, such as by adjusting the slider on your volume control in the system tray. If you receive an error, open your *.vmm file in a text editor and verify that there are no extraneous commas and that the items are correctly separated by commas. If the error does not occur until after selecting the Tutorial #2" show, open that script in a text editor and examine it for the same things. This completes Tutorial 2.

-46-

Tutorial 3 If you have not already completed Tutorial 1, you should do so before attempting Tutorial 3. The files created in Tutorial 1 are required for this tutorial. In Tutorial 1 we created a simple script which displayed images and accompanying text. Then, in Tutorial 2 we added sound to our simple show in the form of narration which matched the text. In this tutorial, Tutorial 3, we will add questions to our show. We will not specify this show as an exam; rather, we will include additional frames which act as reminders if someone selects the wrong answer. Such a show can be used effectively to teach or train. To get started, open the file we saved earlier in your spreadsheet programs native format so that you will have access to the column titles. If you do not already know how to insert rows into a spreadsheet, open your programs help file or manual and learn how. Row insertion will make room for the new frames we plan to add. The following images illustrate the change made between the original script and the script we will save as Tutorial3.csv:

First, note the column titled Question Type; it is no longer filled with zeros. The rows which do not contain zeros are the new rows. The new rows all contain questions in the column titled Primary Text, which previously only contained statements, such as This is a blue circle. The audience must answer each question correctly in order to proceed to the next frame. If a question is answered incorrectly, then an additional frame (the Correction Frame) will appear which displays the correct answer. -47-

The column labeled Repetition Text contains the text which will be displayed on the correction frame; the column title refers to the fact that an individual has been presented with this information earlier in the show. Similarly, the column titled Repetition Picture contains the image which will be displayed on the correction frame. When the correction frame is displayed, the normal display frame hides and the computer beeps. The viewer must click anywhere on the correction frame to make it go away and allow the show to continue. When the normal display frame reappears, the viewer must select the correct answer in order to proceed. [NOTE: If repetition picture and repetition text are not filled out in the script, then a viewer is allowed to proceed without supplying the correct answer.] Using the images above for reference, insert rows to allow questions in rows 4, 6, 7, 11, 12, and 13. Then insert zeros in the flag columns and make other entries as displayed in the images below. Additional columns are displayed below. The Primary text and Answer column entries have also changed. These changes are shown in the images below:

Notice the ampersands (&) in the answer text columns. These cause the letter following the ampersand to be underlined. If the viewer prefers to use a keyboard rather than click with a mouse, the answer can be chosen by pressing the alt key and the underlined letter -48-

simultaneously, somewhat like selecting from a menu in many programs. The use of ampersands is not required. A little mind trick may trip up a show author using the Boolean value when specifying the correct answer to a true-false question. If Answer Text A is True and Answer Text B is False, and False is the correct answer, then the entry in the column titled Correct Answer B must be #TRUE# (i.e., False is #TRUE#). It is logical, but requires that you pay attention. After making all of the entries and edits, go ahead and save the file in the spreadsheet programs native format, then delete the column titles and save the script to the *.csv format as Tutorial3.csv. Once again, the Licensed Name.vmm file will need to be edited, where Licensed Name varies by licensee. The edited file should match the following image:

Now, start up Velosphere and watch Tutorial #3. If you included the ampersands in the answer text columns, try holding down the alt key and pressing the underlined letter to answer at least some of the questions. Also, repeat the show and answer the questions wrong to verify that the repetition text and repetition picture display as expected. The beep may or may not function, depending on your computers setup. Since we did not specify this as an exam in the Licensed Name.vmm file, the users responses are not recorded on the hard drive. We will explore that option in a later tutorial. This completes Tutorial 3.

-49-

Tutorial 4 If you have not already completed Tutorial 1, you should do so before attempting Tutorial 4. The files created in Tutorial 1 are required for this Tutorial. In addition, changes made to the Tutorial 1file in Tutorial 3 will be required in some later tutorials. In Tutorial 1 we created a simple script which displayed images and accompanying text. Then, in Tutorial 2 we added sound to our simple show in the form of narration which matched the text. In Tutorial 3, we added questions to our show in a study format by providing images and text to provide the correct answers if a student responded incorrectly. In this tutorial, we will add some moving pictures (videos) to our show. To make this tutorial meaningful, you will need some *.avi files. These files are the digital worlds version of movies. Moving graphics create very large file sizes, and numerous compression methods have been developed, loosely collected under the heading codecs. If you create your own *.avi files, you should compress them with a codec which will be available on the computer you will play them on. If you simply wish to try out this feature of Velosphere without creating your own files, use the Windows search/find command on your start bar and search for *.avi. Chances are you will find a file or two you can experiment with. Just do not give away any copyrighted movies to other individuals. Note: Velosphere is incapable of playing mpeg-1 and mpeg-2 format files. The smaller file sizes of mpeg-1 and mpeg-2 are preferable for long videos. If you have a great deal of video you wish to incorporate into a show, you should consider using a video format for the entire show and avoid the slide show metaphor. On the other hand, Velosphere can be used to organize your thoughts and materials for your video project. In our earlier tutorials, we left the column titled Movie Files filled with zeroes. In this tutorial, we will fill that column with file names. Or, if you prefer, only enter a filename once.

-50-

After you have created or found a *.avi file, enter its name into the column labeled Movie File. If you wish to use multiple files, use the various applicable names, but only one per row. You should end up with something like the following, which uses a file named ColorShapes.avi from the Velosphere CD:

In the above example, the ColorShapes.avi file has been copied into the Movies\ subfolder we created in earlier tutorials. It is recommended that you copy your *.avi file(s) to that subfolder for this tutorial. Later, you can experiment with different file paths.

In Tutorial 1, we filled the column labeled sec. above (for seconds) with 3's. This represents the period of time Velosphere will wait after opening a new frame before displaying the movie button. It is not necessarily three seconds; different machines yield different results, but it is seldom longer and often shorter. This is nothing more than a programming kludge to prevent someone watching a show from starting a movie before the narration is completed. A movie without sound will occasionally behave fine if you wish to fill the Seconds column with zeroes, but attempting to play simultaneous sounds from multiple sources can yield unpredictable results. -51-

After making all of the entries and edits, go ahead and save the file in the spreadsheet programs native format, then delete the column titles and save the script to the *.csv format as Tutorial4.csv. As in the earlier tutorials, the Licensed Name.vmm file will need to be edited, where Licensed Name varies by licensee, this time adding a fourth row:

When you save Tutorial4.csv and Licensed Name.vmm, be sure to delete the header row with the column titles before creating/saving the comma delimited versions. Now, try out your new show. When you reach a frame where a *.avi file has been assigned, a small button in the upper left corner of the frame should appear shortly after the frame opens. Click this button, and a new window will open displaying the *.avi file, which will begin running immediately. When you click to advance to the next frame of the Tutorial4.csv show, the *.avi display window will close. If the next frame has an associated *.avi file the button will reappear; if not, the button will remain hidden. That is, if the movie camera button is not visible, a *.avi file is not associated with that frame of the show and no motion pictures will be shown. If someone wishes to watch a video more than once, they can click the video button again. Oftentimes this will move the Velosphere window to the front, partially covering the video display window. Clicking the video display will bring it to the front. This completes Tutorial 4.

-52-

Tutorial 5 If you have not already completed Tutorial 1, you should do so before attempting Tutorial 5. The files created in Tutorial 1 are required for this Tutorial. In addition, changes made to the Tutorial 1 file in Tutorial 3 will be required in some later tutorials. In Tutorial 1 we created a simple script which displayed images and accompanying text. Then, in Tutorial 2 we added sound to our simple show in the form of narration which matched the text. In Tutorial 3, we added questions to our show in a study format by providing images and text to provide the correct answers if a student responded incorrectly. In Tutorial 4 we added moving pictures (videos) to our show in the form of *.avi files. In this tutorial we will add music files to our show. In the earlier Tutorial 2, we added sound to our show, and there is no compelling reason those files could not be music, except one. The files we used in Tutorial 2 were *.wav files, which can become rather large if high fidelity is used. This makes *.wav suitable for speech or short sounds, but not as desirable for music. In Tutorial 5 we are going to introduce two new file types: *.mp3 and *.mid. These are different not only from *.wav files, but also different from each other. The *.mp3 file type has become very well known in recent years. This file type allows a great deal of compression of sound files. The compression algorithm used can accept parameters which allow a user to choose between extreme compression or high fidelity, or some compromise between the extremes. Generally, a compromise is chosen. There are quite a few programs on the market which can convert *.wav or other sound files into *.mp3; some of these programs are freeware. A lot of them are designed to rip and burn from music CDs. The *.mid file type (MIDI files) is well known in the music industry. Rather than being a reproduction of a sound, this file type instructs a device (in our case, the computers sound card) what sound to play. Different sound cards may produce different sounds in response to these instructions. For instance, the file may instruct the sound card to play a violin note E. One sound card may respond by creating a synthetic approximation based on hardware programming. Another sound card may have a wavetable built in, which are essentially digital recordings of actual instruments playing different notes. Wavetable cards nearly always sound more realistic, but there is considerable variation among the various models of wavetable cards. MIDI files are extremely small for the amount of music they can produce, both in length and in depth (number of instruments, tonal range, etc.) If you plan to create your own music files from scratch and you have access to the required hardware, MIDI is the way to go, with one BIG caveat: the music will be instrumental only. Admittedly, computer voices exist, but I have never heard one sing beautifully. Of course, Velosphere can also play *.wav files. If you only want to try out this function without creating or finding the appropriate files, you can substitute the *.wav files we created earlier, in Tutorial 2. However, consider trying the other file types; the difference in file sizes is impressive. -53-

After you have determined which files you plan to use, either your own creations or by others, enter their names into the column labeled Music File in your script file. In Tutorial 1, we filled that column with zeros. In the following image, the files used are not music files, but simply the same speech files saved earlier as *.wav format, converted into *.mp3 format:

In Tutorial 1, we filled the column labeled sec. above (for seconds) with 3's. This represents the period of time Velosphere will wait after opening a new frame before displaying the music button. It is not necessarily three seconds; different machines yield different results, but it is seldom longer and often shorter. This is nothing more than a programming kludge to prevent someone watching a show from starting to play music before the narration is completed. Attempting to play simultaneous sounds from multiple sources can yield unpredictable results.

In the above example, the *.mp3 files file have been copied into the MIDIfiles\ subfolder we created in earlier tutorials. It is recommended that you copy your *.mp3 or *.mid file(s) to that subfolder for this tutorial. Later, you can experiment with different file paths.

-54-

After making all of the entries and edits, go ahead and save the file in the spreadsheet programs native format, then delete the column titles and save the script to the *.csv format as Tutorial5.csv. As in the earlier tutorials, the Licensed Name.vmm file will need to be edited, where Licensed Name varies by licensee, this time adding a fifth row:

When you save Tutorial5.csv and Licensed Name.vmm, be sure to delete the header row with the column titles before creating/saving the comma delimited versions. Now, try out your new show. When you reach a frame where a *.mp3 (or *.mid) file has been assigned, a small button in the upper left corner of the frame should appear shortly after the frame opens. [Note: This button is in addition to the button which appears if there is an associated *.avi file.] Click this button, and the sound file will begin running immediately. If there is any silence at the beginning of the file, you will have to wait until the player gets past it to hear anything. When you click to advance to the next frame of the Tutorial5.csv show, the music will end. If the next frame has an associated *.mp3/*.mid file the button will reappear; if not, the button will remain hidden. That is, if the music button is not visible, a *.mp3/*.mid file is not associated with that frame of the show and no music will be played. If someone wishes to listen to a music file more than once, they can click the music button again. As mentioned earlier, advancing to the next frame in the show will stop the music. This completes Tutorial 5.

-55-

Tutorial 6 If you have not already completed Tutorial 1, you should do so before attempting Tutorial 6. The files created in Tutorial 1 are required for this Tutorial. In addition, changes made to the Tutorial 1 file in Tutorial 3 will be required in some later tutorials. In Tutorial 1 we created a simple script which displayed images and accompanying text. Then, in Tutorial 2 we added sound to our simple show in the form of narration which matched the text. In Tutorial 3, we added questions to our show in a study format by providing images and text to provide the correct answers if a student responded incorrectly. In Tutorial 4 we added moving pictures (videos) to our show in the form of *.avi files. In Tutorial 5 we added music files to our show in the form of *.mp3 files (or *.mid or *.wav, if you so chose). In this tutorial we will add access to another file type, the rich text file format, or *.rtf. This file format is primarily for text, but will handle graphics fairly well. Using these files in a show allows you to inject supplementary text, supporting graphics, or other additional information like maps of where a photo was taken. [Note: In Velosphere, the display of *.rtf files is somewhat limited in that the graphics should be either few in number or simple in nature; i.e, few colors or small dimensions. Velosphere will display a rich text file containing several high color photographs if you so choose, but the display will load slowly. If at all possible, use your graphics editing program to reduce color counts of any images in the rich text files for use in Velosphere.] Rich text files can be created by a large number of the word processors available today, under the menu selection File>SaveAs. The most commonly available is WordPad, which comes with Microsoft Windows. This program is located under Programs>Accessories from the Start button on your computer Desktop. Open WordPad and create one or several text files, adding graphics if desired, keeping in mind the previous paragraphs warning. When saving these files, be sure to choose the Rich Text File format, which will add the extension *.rtf to the file name. After you have created the files you plan to use, enter their names into the column labeled Rich Text Files in your script file. In Tutorial 1, we filled that column with zeros.

-56-

In the above example, the *.rtf files file have been copied into the ReferenceFiles\ subfolder we created in earlier tutorials. It is recommended that you copy your *.rtf file(s) to that subfolder for this tutorial. Later, you can experiment with different file paths.

After making all of the entries and edits, go ahead and save the file in the spreadsheet programs native format, then delete the column titles and save the script to the *.csv format as Tutorial6.csv. As in the earlier tutorials, the Licensed Name.vmm file will need to be edited, where Licensed Name varies by licensee, this time adding a sixth row: When you save Tutorial6.csv and Licensed Name.vmm, be sure to delete the header row with the column titles before creating/saving the comma delimited versions.

Now, try out your new show. When you reach a frame where a *.rtf file has been assigned, a small button in the upper left corner of the frame should appear immediately (no delay) when the frame opens. [Note: This button is in addition to the button(s) which appears if there are associated *.mp3, *.mid, or *.avi files.] Click this button, and another window opens which displays the rich text file. When you click to advance to the next frame of the Tutorial6.csv show, the second window will close. If the next frame has an associated *.rtf file the button will reappear; if not, the button will remain hidden and the second window will not be displayed. If someone wishes to display the rich text file more than once, they can click the reference button again. As mentioned earlier, advancing to the next frame in the show will close the second window. This completes Tutorial 6. -57-

Tutorial 7 If you have not already completed Tutorial 1, you should do so before attempting Tutorial 7. The files created in Tutorial 1 and edited in Tutorial 3 are required for this Tutorial. In Tutorial 1 we created a simple script which displayed images and accompanying text. Then, in Tutorial 2 we added sound to our simple show in the form of narration which matched the text. In Tutorial 3, we added questions to our show in a study format by providing images and text to provide the correct answers if a student responded incorrectly. In Tutorial 4 we added moving pictures (videos) to our show in the form of *.avi files. In Tutorial 5 we added music files to our show in the form of *.mp3 files (or *.mid or *.wav, if you so chose). In Tutorial 6 we added rich text files to our show to provide supplementary text and supporting graphics. In this tutorial we will condense our show into a study summary of the show. As mentioned, in Tutorial 3 we added questions with additional text and graphic frames to provide correction to a student who answered incorrectly. In this Tutorial, we will keep the rows of our script which ask the questions, retaining the correction frames, but discard the rows which are simple statements. The following image displays some columns of the show file created in earlier tutorials. Note that the sentences listed under the column heading Primary Text are a mixture of statements and questions; the statements correspond to the zeros in the column titled Question Type while the questions correspond to ones, twos, or threes.

One item which you may or may not choose to edit or delete are the tool tips which pop up over the answer buttons (Answer A Tool Tip column is shown above). This is a style issue in this case, since an incorrect answer will yield a correction frame displaying the correct answer. A show author may choose to delete the tool tip text so the audience will be forced to make an unassisted choice, or perhaps change the tool tip to less directly convey the correct answer. -58-

The idea behind the study summary we are creating is to review all of the questions asked during the full show created earlier, without watching the frames which do not ask questions. This is sort of like having a copy of an old exam to study, complete with an answer sheet. In a later Tutorial, we will convert this study summary into an exam by removing the frames which correct the student. After opening our script from earlier tutorials (at least through Tutorial 3) we examine the script and note which rows do NOT contain questions; these are easily recognized by the zeros in the Question Type column. Now, remove each of those rows from the spreadsheet. Do a complete delete of the row (not simply erasing its contents) so that the next row beneath a deleted row rises to meet the row above. Compare the image below to the image earlier in this tutorial.

Note that the text in the column where the spreadsheet cursor is located can be deleted is desired, as can the text in the other tool tip columns. Try out a show both ways before you decide which you prefer, and experiment with different text. Now, save the spreadsheet in its native format, then delete the column header row and save the file in *.csv format as Tutorial7.csv. That is about all there is to creating a study summary, except for updating the initialization file Your Name.vmm. Add a row corresponding to the Tutorial7.csv file, as shown in the next image:

-59-

Delete the header row and save the Your Name.vmm file in comma delimited format as in earlier tutorials, and watch the show. Be sure to answer questions both correctly and incorrectly to check out your scripts response to both situations. Also, hover your mouse over the answer buttons to verify the tool tip behavior (or lack of tool tip) is what you expect. As was the case in previous tutorials, since we entered #FALSE# in the column titled Exam? in the *.vmm file, the audience responses will not be recorded. In our next tutorial, that will finally change. This completes Tutorial 7.

-60-

Tutorial 8 If you have not already completed Tutorial 1, Tutorial 3, and Tutorial 7, you should do so before attempting Tutorial 8. The files created in Tutorial 1 and edited in Tutorials 3 and 7 are required for this Tutorial. In Tutorial 1 we created a simple script which displayed images and accompanying text. Then, in Tutorial 2 we added sound to our simple show in the form of narration which matched the text. In Tutorial 3, we added questions to our show in a study format by providing images and text to provide the correct answers if a student responded incorrectly. In Tutorial 4 we added moving pictures (videos) to our show in the form of *.avi files. In Tutorial 5 we added music files to our show in the form of *.mp3 files (or *.mid or *.wav, if you so chose). In Tutorial 6 we added rich text files to our show to provide supplementary text and supporting graphics. In Tutorial 7 we condensed our show into a study summary of the show by removing frames which did not ask questions. In this tutorial, we are going to convert the study summary show we created in Tutorial 7 into an exam. Essentially, this requires two types of edit to the script, and a slight variation in the routine editing of the Your Name.vmm file. In addition, we need to confirm that the other initialization file used by Velosphere (MiniMultiMedia.ini) contains valid entries. The first edit we are going to make to the script is the removal of the correction text and the correction images, leaving the columns blank or filled with zeros as shown in the following image (columns titled Repetition Text and Repetition Picture):

By removing these, a show will be allowed to continue uninterrupted if the audience (student) chooses an incorrect answer. If you will recall from earlier shows, since Tutorial 3 the selection of an incorrect answer would trigger display of the text and image in these columns, providing the correct answer to the student. Deleting the text and image from these columns turns off the trigger mechanism (and there is nothing to display, anyway).

-61-

The second edit we need to make (unless you chose to make it during Tutorial 7) is the deletion of the tool tips. In this case, we MUST delete the entries (no zeros or spaces). If we enter zeros, the tool tip balloons will still appear, now containing zeros (try it, if you like).

Now, save the spreadsheet in its native format, then delete the column header row and save the file in *.csv format as Tutorial8.csv. That is about all there is to creating an exam script, but we still need to update the two initialization files. A little more is involved in updating the initialization file Your Name.vmm than in earlier tutorials. Besides simply adding a row corresponding to the Tutorial8.csv file, we enter #TRUE# in the column with the heading Exam?, as shown in the next image:

Entering #TRUE# does not change a shows appearance; it causes files on the hard drive to be created or appended which record the answers given by the student. In addition, the percentage of correct answers are calculated, compared to the value in the Passing% column, and recorded. The names of those files and their locations on the hard drive are specified by the MiniMultiMedia.ini initialization file.

-62-

Delete the header row and save the Your Name.vmm file in comma delimited format as in earlier tutorials, then open the MiniMultiMedia.ini file and verify that the file names and locations are correct. The following image is an example of a MiniMultiMedia.ini file opened in Notepad(tm). Note that this file is a comma delimited file, similar to the others we have been working with, with three entries: the file name and path of the list of registered audience members, the name and path of the folder where the record files are stored, and the file name used for the record summary. In Tutorial 1, we decided to let Velosphere create the list of registered audience members (students) from scratch, so we left the first of the three entries blank (note the leading comma):

Velosphere will create the records files it needs if they do not already exist, but the shows author should create or verify the existence of the folders. The folders can be anywhere on the hard drive(s) accessible by Velosphere and named anything acceptable to the operating system. Use of removable media for this purpose has not been tested. After creating/verifying the MiniMultiMedia.ini file and saving it into the same folder as the Velosphere.exe program, start Velosphere and watch the show. Be sure to answer questions both correctly and incorrectly to check out your scripts response to both situations. Also, hover your mouse over the answer buttons to verify the lack of tool tip. Since we entered #TRUE# in the column titled Exam? in the *.vmm file, the student responses will be recorded. After you complete the exam, go to the records folder and review the files created by Velosphere. The simplest way is to open each file in a text editor such as Notepad(tm) or WordPad(tm); however, the records summary file is easier to read if opened in a spreadsheet program as a tab delimited file. The image on the following page is of a file created by a student logged on as Demo Debbie taking a Velosphere exam. The numbered lines are the questions asked during the exam, in order. Along the left margin are two columns filled with True and False. The leftmost column corresponds to the students response, with True meaning selected. The second column corresponds to the correct answer, with True meaning correct. The third column lists the text on the answer buttons. In this particular case, Demo Debbie answered one of the questions incorrectly. Question number 3 was of question type 3. This question type allows the student to select more than one response from multiple choices. The correct answers in this case are Green and Circle, but Demo Debbie selected Circle and Square. Thus, although one of the two was correct, the answer was marked as incorrect. There is no partial credit. Exam authors need to remember this. The lower portion of the file image lists information such as the student name, ID, and classification, as well as the exam title, percentage correct, and pass/fail. The image is on the following page:

-63-

See the previous page for an explanation of this image.

The records summary file is a tab delimited file which is appended (a new line is added) every time another exam is completed. Each line contains information about a single instance of examination, including: Exam file name, Student name, ID#, classification, percentage correct, Pass/Fail, date of examination, and date of reexamination. The tab delimited format used for this file provides compatibility with nearly all database formats, allowing Velosphere exam results to be imported into existing records systems using common programming techniques. If use of a database is not needed or desired, the file can be opened with either a text editor or a spreadsheet program (the preferred method for clarity). -64-

The following images show the same records summary opened multiple ways. First opened in a text editor (Notepad(tm) in this case):

Next, the same file opened in spreadsheet format:

The following image shows the file opened in spreadsheet format, with a title row and formatting added in the spreadsheet program (Microsoft Excel(tm) in this case):

If you choose to open the records summary file in this manner, be careful if you choose to save it from the spreadsheet program. The best method from a safety standpoint would be to change the name to one not used by Velosphere and use the spreadsheet programs native format. Barring that, you should delete the row of column headings and select tab delimited format when saving the file. PRACTICE WITH A SAMPLE FILE BEFORE DOING THIS WITH AN IMPORTANT FILE! The primary danger comes from possibly saving in the wrong format, but an additional danger is that the names selected for column headings may change the file so it appears corrupt from Velospheres viewpoint. If you have sufficient confidence in your expertise with file formats, try some variations to see if any work for you. Just remember that some of the file entries are not considered text by Velosphere.

-65-

Note: If you do not tell Velosphere where to save records, it stores them in either Windows\Temp or WinNT\Temp, depending on your operating system. These are not secure locations; many system utilities clear these folders. Please direct Velosphere to store in other locations in the manner outlined in this tutorial. This completes Tutorial 8.

-66-