Saving and testing the To-Do List applet

You have already saved parts of your applet as you have been working. When you save changes to a bean, you are replacing the old specification of the bean with a new one. When you do this, VisualAge for Java will be using the new specification of the bean for all new uses of it. It is good practice to save your changes to a bean periodically as you are working with it and when you have finished editing it.

Saving your visual bean

In the Visual Composition Editor, do the following:

Testing the applet

Now that your work is saved, you can test your To-Do List applet.

  1. To begin testing your applet from within the Visual Composition Editor, select Run from the tool bar
    trunicon.gif (1013 bytes)

    The Applet Viewer starts with your applet in it.

  2. When the To-Do List applet appears, experiment with it to ensure that it behaves the way you expect it to. For the To-Do List applet, you need to ensure you can add typed items to the list and remove selected items from the list.

Note:
As you design your applet, the Swing beans are presented with Sun's Metal look. For example, a JButton will look like a Metal JButton as opposed to a Windows JButton. You can add your own code to have your beans rendered in a different system's look and feel at runtime. For example, you could add code to have your beans have a Windows look and feel. Adding this user code is not covered in this document.

Be sure to close the applet window when you have completed your testing.

At any time, you may return to the Visual Composition Editor and make changes, save the changes, then test the applet again.

Congratulations! Your To-Do List applet is finished.

Saving your workspace

Before you continue, save your workspace. When you save your workspace, you are saving the current state of all the code that you are working on and the state of any windows that you currently have open. To save your workspace: