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: December 11, 2014 @ 1:00 p.m. ET / 10:00 a.m. PT
Market pressures to move more quickly and develop innovative applications are forcing organizations to rethink how they develop and release applications. The combination of public clouds and physical back-end infrastructures are a means to get applications out faster. However, these hybrid solutions complicate DevOps adoption, with application delivery pipelines that span across complex hybrid cloud and non-cloud environments. Check out this …
Event Date: October 29, 2014
It's well understood how critical version control is for code. However, its importance to DevOps isn't always recognized. The 2014 DevOps Survey of Practice shows that one of the key predictors of DevOps success is putting all production environment artifacts into version control.
In this webcast, Gene Kim discusses these survey findings and shares woeful tales of artifact management gone wrong! Gene also shares examples of how high-performing DevOps …