an applet with a text field and three buttons. When you press each button, make
some different text appear in the text field.
a check box to the applet created in Exercise 1, capture the event, and insert
different text into the text field.
an applet and add all the components that cause
to be called, then capture their events and display an appropriate message for
each inside a text field.
to Exercise 3 the components that can be used only with events detected by
and display appropriate messages for each inside a text field.
an applet with a
so that if the button has the focus, characters typed into it will appear in the
an application and add to the main frame all the components described in this
chapter, including menus and a dialog box.
so that the characters in
retain the original case that they were typed in, instead of automatically
being forced to upper case.
so that it uses the Java 1.1 event model.
to the manifest file shown in this chapter and run
to create a JAR file containing both
Now either download and install the BDK from Sun or use your own Beans-enabled
program builder tool and add the JAR file to your environment so you can test
the two Beans.
your own Java Bean called
contains two properties: a Boolean called “on” and an integer
called “level.” Create a manifest file, use
to package your Bean, then load it into the beanbox or into your own
Beans-enabled program builder tool so that you can test it.
so that it handles cascading menus.
Live Event Date: April 22, 2014 @ 1:00 p.m. ET / 10:00 a.m. PT
Database professionals — whether developers or DBAs — can often save valuable time by learning to get the most from their new or existing productivity tools. Whether you're responsible for managing database projects, performing database health checks and reporting, analyzing code, or measuring software engineering metrics, it's likely you're not taking advantage of some of the lesser-known features of Toad from Dell. Attend this live …
Live Event Date: May 6, 2014 @ 1:00 p.m. ET / 10:00 a.m. PT
While you likely have very good reasons for remaining on WinXP after end of support -- an estimated 20-30% of worldwide devices still are -- the bottom line is your security risk is now significant. In the absence of security patches, attackers will certainly turn their attention to this new opportunity.
Join Lumension Vice President Paul Zimski in this one-hour webcast to discuss risk and, more importantly, 5 pragmatic risk mitigation techniques …