Abstract Window Toolkit
|
- An API that provides graphical user interfaces for Java programs. The Abstract Window Toolkit (AWT) also provides imaging tools, event-handling methods, layout managers, and data transfer classes. The AWT components are implemented using native-platform versions of the components and have largely been replaced by the Swing components, which have a pluggable look and feel.
|
applet
|
- A program, written in the Java programming language, that runs in a web browser.
|
application
|
- A standalone software program that enables the user to perform a specific task, such as database management.
|
class
|
- A group of attributes and methods that define the implementation of a particular type of object.
|
component
|
- An object that is identified by its properties, operations, and relationships. For example, a button is a visual component whose properties include size and foreground and background color.
|
Component Inspector
|
- A window in which you can view both the visual (such as a button) and non-visual (such as a layout manager) components in your application. From the Component Inspector, you can modify a component's properties and specify its events.
|
component palette
|
- A collection of toolbars that provides easy access to frequently used components, including AWT and Swing components. You can create your user interface by clicking a component in the component palette and then clicking in the Form Editor.
|
container
|
- A component that contains other components. Windows and dialog boxes are examples of top-level containers. Panels, scroll panes, and tabbed panes are examples of intermediate-level containers.
|
dock
|
- To anchor an object, such as a toolbar, to the edge of the window or pane to which it applies.
|
dynamic code completion
|
- The automatic completion of an expression that you are typing in the Editor window. To use dynamic code completion, type the first few characters of the expression, and then press CTRL+SPACE. A list of of classes, methods, and variables that can be used to complete the expression is displayed.
|
Editor
|
- A tool for editing Java, HTML, and plain text files as well as files specified by modules. Source code in the Editor window is automatically updated and generated as you work in the Form Editor window and Component Inspector. The generated source code is indicated by a shaded background and cannot be edited in the Editor window.
|
event
|
- An action to which an object can respond. Most events are initiated by a user action, such as a click, key press, or mouse movement.
|
event handler
|
- A method that is called when an event is triggered on a component.
|
Explorer window
|
- A window that provides a unified view of all objects and files in the Forte for Java environment. The Explorer window is a good starting point for working with your application, including organizing files, editing object properties, and creating component connections.
|
Form Editor window
|
- An area for creating and modifying a graphical interface. You can select a component (such as a panel, scroll bar, or menu) in the component palette and add it to your graphical interface by clicking in the Form Editor window.
|
Java Foundation Classes
|
- An extension to the Abstract Window Toolkit (AWT) that provides the Swing classes, a collection of graphical user interface components with a pluggable look and feel. The Java Foundation Classes (JFC) also provide the Java Accessibility API, which can be used to create applications that interact with assistive technologies. For the Java 2 platform, the JFC also includes the Java 2D API (for 2D graphics and imaging) and drag and drop.
|
layout manager
|
- A property of a container component that controls the size and location of components within the container. A layout manager ensures that the container can adjust to resizing and to differences between systems, such as different font sizes. The Java platform supplies six layout managers:
BorderLayout , BoxLayout , CardLayout , FlowLayout , GridBagLayout , and GridLayout .
|
main window
|
- A window that acts as the control center for Forte for Java. The main window contains menus, toolbars, and a component palette for developing Java applets and applications. From the main window you can access the five workspaces in Forte for Java.
|
method
|
- A procedure that belongs to a class and that can be applied to a specific object or the class itself.
|
module
|
- An independent piece of software that is part of a larger program but is usually compiled separately. Modules are implemented in such a way that you can change one module without affecting the other modules in the program.
|
Object Browser
|
- A three-pane window in which you can view the hierarchy of packages, objects, and members in your application. Like the Explorer window, you can use the Object Browser as a base for many tasks in the development of your application. For example, you can open a source file and add new packages, objects, and members from the Object Browser.
|
package
|
- A collection of Java classes and interfaces, grouped in a single entity.
|
project
|
- A collection of files that make up an applet or application. The files in a project can be operated on as a whole.
|
property
|
- An attribute or characteristic of a GUI object that you can set. The properties of an object might define its size, color, and value.
|
Swing components
|
- A collection of GUI components with a pluggable look and feel so you can design an application that can have the look and feel of any OS platform. Swing is part of the Java Foundation Classes and includes interface elements such as windows, dialog boxes, choosers, panels, panes, menus, controls, text components, tables, lists, and tree views.
|
template
|
- Software code that serves as a guide for creating a component. A template provides the initial appearance and behavior of the object, which you can easily change. In the Forte for Java environment, components such as Swing and AWT containers are provided as templates.
|
workspace
|
- A collection of windows with related functions. For example, when you edit your user interface, you use a workspace that displays the Component Inspector, the Form Editor, and the source Editor. When you debug your program, you use a workspace that displays a window for setting breakpoints, monitoring threads, and watching the value of variables.
|