Glossary/Master Index

Glossary

active screen: The screen at the top of the window stack. This is the screen that the user can interact with. If there is a cursor, it appears on this screen.
ActiveX control: Software components using Microsoft's COM technologies to interact with other COM objects and services.
address: An Internet machine name or location, for example, prolifics.com.
agent: In three-tier architecture, a client or an application server.
aggregate function: One of a group of database functions that calculates summary information on a group of rows.
alias: A mechanism whereby a Panther variable is explicitly named to receive information from a database column. You should use an alias when the Panther variable and the database column have different names.
anchor: The HTML tag that denotes a hyperlink in an HTML document.
applet: A Java program that is embedded within an HTML document. An applet cannot run as a standalone Java application.
application mode: The start-up mode when using the Panther runtime executable. In this mode, you can test a complete application, or portions of an application.
application server: The server component of a three-tier system. In addition to application logic, it contains the services that access the resource manager, such as a database. The services are called by clients or other services, which may or may not reside on the same physical machine.
array: A field that has one or more occurrences. The number of onscreen occurrences is specified in the Array Size property under Geometry. Each occurrence can contain data. The onscreen portion of an array contains one or more elements, where each element is identified by a field number that is unique on the screen. An array can contain more occurrences than it has onscreen elements; then it is called a scrolling array and the number of offscreen occurrences is specified in the # of Occurrences property.
attribute: In HTML, an attribute is the named component of an object or element with a specific value, requirement, or default status. Attributes give an element its unique characteristics.
authoring environment: The tools used to create and test application screens and links; the authoring environment includes application mode, the screen editor, menu bar editor, styles editor, and visual object repositories.
automatic function: A hook function that executes on all occurrences of an event type—for example, screen exit on every screen in an application. These functions are never explicitly called in the application code or screens; instead, Panther calls them automatically at the appropriate stage of program execution. Contrast with demand function.
block mode: Refers to a terminal that collects user input and transmits a set of new or changed data to the host computer in a block, as opposed to a terminal that transmits each keystroke separately.
browser: A program used to access resources located on the Internet or on an intranet. Diferent platforms and terminals can access different browser programs. The prgram can be text-based or graphical. Microsoft Internet Explorer is an example of a graphical browser program.
bundle: A buffer that stores screen data sent by JPL's send command or by sm_append_bundle_data. Panther can maintain up to ten bundles. Bundle data can be read by the receive command or by sm_get_bundle_data.
CGI: Common Gateway Interface, which determines how an HTTP server passes information to other gateway programs on the server.
check box: A selection widget used to enable or disable one or more features or options, usually occurring in a group of check boxes. Contrast with radio button.
child object: An object, either a widget or screen, that has been copied from a repository to an application screen. It has an inheritance relationship with the parent object in the repository, so that if any changes are made to the parent, they also affect any children of that parent.
child table view: One of two designations for a linked table view, the other being a parent table view. Table views must be linked to be included in database command processing; the designation of parent or child determines the order in which table views are processed by the transaction manager.
class: 1)A widget property that is applied when you run the transaction manager. The class setting specifies a style for the widget in each transaction mode. 2) The prototype for an object in an object-oriented language; analogous to a derived type in a procedural language. A class may also be considered to be a set of objects which share a common structure and behavior. The structure of a class is determined by the class variables which represent the state of an object of that class and the behavior is given by a set of methods associated with the class.
class diagram: A class diagram displays design-time information. Class diagrams can be used to define components of an application, information about the components, and what their relationship is to other components.
client: A program that extracts information from a server. In two-tier client/server applications, the program or machine containing the user interface. In three-tier, the client connects to an application server via middleware and makes requests for services from an application server or resource manager. In a two-tier environment, the client accesses data over a network from a database.
CLSID: Class Identifier. A globally unique identifier assigned to a COM component when it is created.
column: The various subsections of a database table, each containing a piece of information. actor_id, first_name and last_name are the columns in the actors table. In some database systems, a column is called a field.
COM: Component Object Model. Microsoft's specification for the building of modular, object-oriented software components. Each COM component has a unique, global identifier called a CLSID. ActiveX controls are a type of COM component.
commit: The act of saving the database changes back to the server when a transaction is complete. Contrast with rollback.
component: A unit of work that encapsulates business logic. It publishes an interface available to all foreign applications or components enabling easy integration.
configuration variable: Variables defined either in the smvars file or in the environment, which serve as pointers to required configuration files (key translation, video, and message), to alternate setup files, and to application-specific files and information. See also setup variable.
control string: Control strings can be thought of as the connectors that hold a Panther application together. A Control String property setting defines the action to take place when a push button, function key, or menu selection event occurs. Possible actions include: displaying a screen or window, calling a developer-written function, or executing a system command.
conversion server: A type of application server used in JetNet applications; advertises built-in services for use by transaction manager-enabled applications that have been converted from a two-tier application to a three-tier application with Panther's two- to three-tier conversion utility.
cookie: A piece of information set by an HTML document to be stored on the browser. If the browser subsequently requests information from the same HTTP server that set the cookie, the cookie value is returned in the HTTP request.
correlation name: A temporary alternate name for a database table which is specified in the SQL statement when implementing a join or a self-join.
cursor: 1) The positional indicator on the monitor. 2) An SQL object associated with a specific query or operation.
database: A collection of information, organized into database tables.
database engine: A DBMS product which is identified by the vendor name and version number. For example, SYBASE 16, ORACLE 11 and ORACLE 12 are three distinct database engines.
DBMS: Database Management System. The components used to create and maintain a database.
DCOM: Distributed COM, or Distributed Component Object Model. The extension of COM to support communication between components distributed across a network.
demand function: A hook function that is explicitly called from a Panther object, such as a function called from a control string on a widget or screen , a screen entry function on a specific screen, or a function called from a JPL module. Contrast with an automatic function.
dispatcher: A Panther web application broker process which acts as the messenger between a requester and a jserver. When a requester starts, it notifies the dispatcher that it intends to submit a request. The dispatcher waits for a jserver to become idle and then connects it to the incoming requester.
display text: A widget that is not altered by the user or program at runtime. Static labels and graphical widgets (boxes and lines) are considered to be display text. These widgets do not get a field number.
distributed transaction: A transaction that spans multiple resource manager instances. It starts with an XA-compliant xa_begin, and ends with an XA-compliant xa_commit, xa_rollback, or xa_end.
document root: The base of an HTTP server's document tree.
domain: A name given to a computer that is mapped to its numeric IP address. There can be several domain levels, each one separated from the next by a period. The highest domain level is to the right. Examples of the top-level domains are .com for businesses, .gov for government agencies, and .edu for schools and universities.
DTD: Document Type Definition. The specification that defines the structure of the markup elements in an HTML document and determines how to place elements inside the document.
edit mode: The start-up mode when using the Panther development executable. You can access the menu bar editor and styles editor from this mode as well as connect to databases. You can also toggle in and out of test mode in order to test portions of an application.
element

An onscreen field in an array. Contrast with an occurrence.
The basic unit of an HTML document. Each element has a unique tag that can be used to identify the structural contents of the document. TITLE, BODY, and FORM are examples of HTML elements.

embedded character: Refers to any character in a data entry field that is automatically inserted into the field and cannot be modified by the user. They are created through the Keystroke Filter property when it is set to Edit Mask or by characters in the field that do not match the Kerstrone Filter. Depending upon the filter used, the library routine sm_getfield may or may not see the embedded characters as data.
Enterprise JavaBeans (EJB): Server-side components written in Java that perform the business logic of an application in n-tier distributed applications. They must be deployed on an EJB server and within an EJB container, such as those provided by IBM WebSphere.
engine: See database engine.
event: An action that causes a change in the processing flow of an application. Some events are associated with a user action, such as a mouse click or menu selection. Other events are associated with an action internal to the application, such as a screen exit. Events are classified by how and where they are triggered, such as the completion of a service request or an error in program execution.
external menu: A submenu whose name is not defined in the menu file of the menu invoking it. External menus are useful when you want to invoke the same submenu in different menus, such as a generic Edit menu.
field: A screen object, or widget, that accepts or displays data, for example where a user enters data or the program displays variable output. Examples of fields include option menus, dynamic labels, and data entry widgets. Contrast with display text.
field number: A unique number assigned by Panther to each field in a screen. This number is based on the field's position in the screen and therefore may change if field positions or number of occurrences are changed. Although the field number can be used to refer to a field, it is recommended that you use the field name.
file access server: A type of server used by JetNet and Oracle Tuxedo applications to provide remote library and repository access in the development environment and to exchange files from a remote server.
firewall: A system that separates a local internal network from an outside network such as the Internet. When configured, a firewall prevents unauthorized TCP/IP packets from passing into the local network from the outside, and vice versa.
foreign key: A column in a database table which is defined as a primary key in another table within the same database.
form

One of two ways that a screen is displayed in an application, the other being a window. The main difference between a form and a window is that you can have multiple windows open at one time, but only one form. An example of a form is the startup screen displayed when a user begins a Panther application.
In HTML, the FORM element is used to create fill-in forms that collect data from user input. Attributes that are associated with FORM are Action and Method.

FTP: File Transfer Protocol. An Internet client/server protocol used for transferring files between networked computers.
function key: A programmable key with a function other than data entry. Its meaning can be defined by either a program or a user. Panther function keys are frequently associated with control strings that specify such actions as form and window display. Panther function keys are defined as logical keys; the mapping of functions to physical keys is done by the user, allowing the application to be terminal independent.
GET: A CGI method that is used to retrieve a document from an HTTP server or to send an input form from the user back to the HTTP server. With GET, data in the input form is appended to the URL.
GIF: Graphics Interchange Format. A compressed graphics file format widely used in HTML documents to display pictures and animation.
group: One or more selection widgets (radio button, check box, list box, and toggle button) that are functionally connected—therefore, the widgets function as a group. The group has properties that define its entry/exit/validation behavior and tabbing order. Also, the set of widgets that make up a table view.
handles: Places on a widget or screen where the object can be "grabbed" for repositioning or resizing.
help screen: An informational screen that can be attached to a screen or widget by specifying its name in the Help Screen property. The specified help screen will display at runtime when the Help key is pressed or automatically when the screen or widget is entered. Panther also supports an External Help property for displaying help using a third-party help engine.
home page: The first page that is displayed when you access a website. It usually contains hyerlinks to other documents within the site or to other websites.
hook function: A function to be invoked when certain events occur, such as screen entry or function key selection. Hook functions can be divided into two general types: demand functions that are called explicitly from a Panther component such as a screen, and automatic functions that are called automatically on all occurrences of an event type.
HTML: HyperText Markup Language. The formatting language used by documents on the Internet, which specifies via markup tags how to present document information in the browser.
HTTP: HyperText Transfer Protocol. The TCP/IP based communications protocol that defines how clients and servers communicate over the web.
HTTPS: An implementation of the HTTP protocol that provides for more secure web communications by including encryption methods.
hyperlink: A reference to another Internet resource. By clicking on a hyperlink, the resource associated with the hyperlink is downloaded to the browser.
inheritance: The propagation of properties from an object in the visual object repository to an object in a screen. The inheritance relationship can be established either by copying the parent object from the repository to your screen or by entering the repository object in the application object's Inherit From property. The application object is referred to as the child object.
Internet: A global collection of interconnected networks and computers.
intranet: An internal, organization-wide networked computing environment.
IP address: The numerical Internet protocol address of a computer on the Internet. Each computer on the Internet has a unique IP address.
ISAPI: Internet Information Server API. This API for Microsoft's HTTP servers optimizes the web application interface for faster access than a corresponding CGI program.
Java: An object-oriented programming language similar to C++.
JavaScript: An interpreted, scripting language that lets you embed simple programs in web pages.
JDB: Single-user SQL database included with Panther. JDB can be used as a prototyping tool to test and refine multi-user database applications when an external database is not available.
JetNet: Panther's middleware component.
JIF: In JetNet and Oracle Tuxedo applications, an interface file containing services information used in client/server processing. In Oracle Tuxedo, it also provides queue information. The service information in the JIF is used by clients when requesting services, and by servers when responding to these requests.
join: An SQL method of combining database tables in order to obtain the desired information. In a join, multiple tables are connected by specifying the relationship between a column in one table and a column in another table.
key translation file: A configuration file that contains the mapping between Panther logical keys and the physical keys on a terminal. You can create or edit a key translation file with a text editor. You can use the showkey utility to aid in determining the sequences that the keys on your terminal generate, for inclusion in the file.
LDB: See local data block (LDB).
LDB entry: A field in an LDB (local data block) screen.
link: A widget that defines the relationship between two table views by describing which columns or widgets connect the table views, the type of link, server or sequential, and which table view is the parent and child. Links are needed by the transaction manager to perform its processing: if a screen contains more than one table view, and they are not linked, they will not be included in any command processing.
list box: A selection widget that contains a scrolling list of choices. List boxes are one of two types: action or selection, depending on whether the user can make one or multiple choices in the box. List boxes can be populated either with data from an external source, such as a database, or with data supplied at design time via the Properties window.
local data block (LDB): A Panther screen that is used to initialize and save values on other screens, allowing applications to transfer data between screens automatically. When a screen serves as an LDB, Panther uses its fields, or LDB entries, to transfer data to and from corresponding fields on the current screen.
logical key: A device-independent mnemonic for a predefined Panther function. These logical functions have names such as TRANSMIT and EXIT. Logical keys are mapped to physical keys via the key translation file.
lookup screen: A nondisplaying screen used to validate entries made to data entry widgets at runtime.
message file: A configuration file that maps message text to message identifiers. Panther messages are stored in the message file to enable customization (e.g., for international use). User messages may be included as well. The message file also contains date, time, and numeric format specifications that can be customized.
middleware: In three-tier architecture, the software that manages communication between clients and servers. Panther's middleware is referred to as JetNet. Other middleware products supported in Panther are Oracle Tuxedo, MTS and WebSphere Application Server.
MIME: Multipurpose Internet Mail Extensions. Extensions to the Internet mail protocol that allow inclusion of sound, audio, video, graphics, and other formats besides text files.
modal window: See stacked window.
MTS: Microsoft Transaction Server. A part of Windows server providing transaction support for COM components over a distributed network.
NCSA: National Center for Super-computing Applications. Responsible for developing the NCSA HTTP'd server program.
NSAPI: Netscape Server API. An API for the Oracle iPlanet Web Server (formerly known as the Sun Java System Web Server and as the Netscape Enterprise Server).
occurrence: An entry in an array. If the number of occurrences is larger than the number of onscreen elements, then the array is a scrolling array.
parent object: A repository object, either a widget or a screen, having an inheritance relationship with a child object in an application screen. The relationship is created either by copying the object from the repository to your application screen or by identifying the repository object in the Inherit From property window. When any changes are made to a parent object, the changes propagate to any children of that object.
parent table view: One of two designations for a linked table view, the other being a child table view. Table views must be linked to be included in database command processing; the designation of parent or child determines the order in which table views are processed by the transaction manager.
path name: The location of a file in the directory tree structure. You can specify either an absolute path name or a relative path name. An absolute path name specifies the name of each parent directory, starting with the root identifier. Under Windows, an absolute path can also specify the drive name. A relative path name identifies the file's location relative to an arbitrary directory in the tree, typically the current working directory.
popup menu: A menu that can be accessed by pressing the right (menu) mouse button. The menu that is displayed is context-sensitive—its content depends on the location of the mouse pointer and the menu specification. You can specify the menu in the Popup Menu property under Help.
port: The TCP/IP numeric identifier that a program or service seeks so it can communicate with a computer in a networked environment. Programs are assigned different port numbers so the computer knows what to do when it accesses that port number.
POST: A CGI method of sending an input form from the user back to the HTTP server. With POST, data in the input form is sent to the CGI program as a message body, not as a part of the URL.
primary key: The information in a database column or columns that constitutes a unique entry for each row in the database table.
property: A display or behavioral attribute assigned to one or more application objects. Properties can be inherited from a repository, set manually using the Properties window in the screen editor, or set programmatically using the properties API. Examples of properties are an object's name, widget type, and location on a screen.
protocol: A standard for computer-to-computer communications. TCP/IP, HTTP, and FTP are examples of protocols.
prototyped function: A hook function that gets only the number and type of arguments that you specify. Prototyped functions are demand functions—that is, they must be invoked by name from a Panther component, such as a widget or screen. Prototyped functions can be Panther library functions or developer-written.
proxy: A server that acts as a guaranteed route through a firewall. It is used to isolate all traffic from the internal network and the external network; all traffic is funnelled through this route. By implementing a proxy, a machine that is on the internal network can conduct transactions with a machine on the external network, and vice versa, by using the proxy as an intermediary.
push button: Describes a widget used to carry out a command or action when selected. A push button is known as a command button in MS Windows parlance.
qbe: Query by example. In this type of database query, the WHERE clause includes specific values so that a certain subset of information can be returned.
query string: The parameters passed to an HTTP server as part of a URL. A query string is used with the GET method and, in a URL, follows the resource location and name.
radio button: A selection widget that, when grouped with other radio buttons, allows the user to select a single option from a set of choices. A radio button is known as an option button in MS Windows. Contrast with check box.
report wizard: Graphical development tool for designing database application reports that use the transaction manager. The report wizard prompts you for basic design information and uses that information to build a report that can be used either as is or as a basis for further development.
repository: See visual object repository.
requester: A Panther web application broker process that accepts a CGI request from the HTTP server and notifies the dispatcher of the incoming request. After the requester is connected to a jserver, it transmits the jserver's response back to the HTTP server.
resource manager: An interface and associated software providing access to and controlling a collection of information and/or processes. In three-tier architecture, the resource manager is the backend, typically a database server. An example of a resource manager is a database management system.
result set: The set of rows that gets returned after executing a database query with SQL SELECT.
rollback: The act of undoing the changes made to a database in a database transaction. Contrast with commit.
root table view: The table view that forms the basis of the database processing on a transaction manager screen.
row: An entry in a database table containing a value for each column. In some database systems, a row is called a record.
runtime: The environment in which a user runs a Panther application. The runtime environment is different from the development environment in that the editors and repositories cannot be accessed.
schema: An outline of your database showing the different areas of information (database tables) and the different pieces of information in each of those areas (database columns), and illustrating how the pieces relate to each other. Also called a data model.
screen: Generic term that refers to the objects created using the screen editor. Screens usually contain collections of widgets. At runtime, a screen can be opened as a form or as a window.
screen wizard: Graphical development tool for designing database application screens that use the transaction manager. The screen wizard prompts you for basic design information and uses that information to build a screen that can be used either as is or as a basis for further development.
scrolling array: An array in which the maximum number of occurrences exceeds the number of array elements. When the array contains more occurrences than elements, Panther lets you scroll the array to bring hidden occurrences into view. If circular scrolling is enabled, Panther lets you continue scrolling beyond the first and last occurrences to the last and first occurrences, respectively.
select list: In database applications, the list of columns or expressions to be processed by the SQL SELECT statement.
selection widget: A widget that allows a user to select from several choices. Panther supports four kinds of selection widgets: check box, radio button, toggle button, and list box. A set of similar selection widgets are usually grouped, so they behave in a certain fashion with respect to the number of possible choices.
sequential link: A link where the transaction manager processing for the parent table view occurs first, followed by the processing for the child table view.
server: A machine within a networked computing environment that responds to requests from client programs. In a client/server environment, the process that responds to a client's request for a service. Typically, the request is for information from a resource such as a database; the application server interacts with the resource manager to obtain the information. In a two-tier system, the server might contain application logic, in the form of database stored procedures, for example. In web applications, an HTTP server responds to requests from the web browser.
server link: A link where transaction manager processing for the parent and child table views is done at the same time by the database server.
server view: A table view and all the table views connected to it by server links.
service: In a client/server environment, a function performed by a server at the request of a client or of another server. The service is usually associated with accessing a resource manager, typically a database. In Panther, all services must be defined in the JIF.
service component: The graphical representation of a service. It is created with a screen editor and contains widgets and information required to pass data to and from a service. Service components are not visible at runtime, but are placed on the application server in order to process the service.
service group: A named collection of services, defined in the JIF.
setup file: File used by Panther at runtime to find and translate an application's configuration. The environment variables in setup files tell Panther how the application should look, how the hardware is configured, and where system-specific information is located. Setup files can be used to establish installation-wide and application-specific configuration information.
setup variable: Variables, usually defined in the smvars or smsetup file, that control the overall behavior of Panther and Panther applications. See also configuration variable.
shifting field: A field in which the maximum number of characters (Max Data Length property) allowed for input exceeds the number of characters (Length property) that the field can display at any given time. When the field contains more characters than the field can display, the user can shift the data horizontally—left and right—to bring hidden data into view.
sibling window: A window that is at the same level as another window. Sibling windows can be opened and activated without closing the calling window, and are therefore non-modal. The VIEWPORT key allows the user to select among (activate) any open sibling windows. Contrast with stacked window.
SQL: Structured Query Language. A language used to access databases employed by many relational database products. SQL was originally developed by IBM in the 1970's. ANSI standards have been issued for SQL in 1986 and 1992.
SSL: Secure Sockets Layer. When implemented, SSL allows for encrypted processing of data between the browser and the server.
stacked window: A window that is layered on top of other open screens. Once a stacked window is opened, it must be closed before the user can access any underlying screens. This is also called a modal window, and is often used for a dialog box.
standard server: A type of server used by JetNet and Oracle Tuxedo applications to access clients and resource managers. Provides only those services that have been defined in the JIF.
style: A group of settings affecting the appearance and focus protection properties of a widget. A style is applied to a widget by the transaction manager for a particular transaction mode based on the widget's class property.
submenu: A lower level menu that displays additional choices under a menu item on an upper level menu.
support routine: A module supplied with Panther's database drivers which supplies all the engine-specific instructions needed to process database statements.
synchronized array: Two or more scrolling arrays whose data scroll together. Synchronized arrays are defined via the Edit menu in the screen editor. The arrays need not be adjacent to each other on the screen, but must contain the same number of occurrences and onscreen elements.
system catalog: A series of database tables containing information about the database itself, such as the table names, column names and key information.
table: A main subset of information in a database containing a series of columns and rows. In some database systems, a table is called a file.
table view: A group of widgets, generally from the same database table, which work together in transaction manager processing.
tag: Text surrounded by < and > that identify it to the browser as HTML markup text.
target: The name of a browser window or frame that displays an HTML document.
TCP/IP: Transmission Control Protocol/Internet Protocol. The basic communications protocol that is the foundation of the Internet.
test mode: A special state in the various editors that allows you to test the object you are editing. You can toggle into and out of test mode without disrupting your editing session.
three-tier architecture: A computer architecture that adds a middle layer, called the application server, to the two-tier client-server model. In a three-tier model, the client, or front end, contains the user interface, while the backend, or resource manager, is usually a database. The middle layer, or application server, handles the application logic, providing services to the client and interacting with the resource manager as needed. Communication among the three layers is managed by middleware. Three-tier architecture allows for the greatest flexibility in distributing clients and servers across multiple platforms and machines.
toggle button: A selection widget that allows users to toggle between two settings—turning some option off or on.
transaction: A database transaction is a series of SQL statements that must either be completed as a unit, or not completed at all. At the end of the series, you commit the transaction in order to save the changes to the database. If there is an error, you can rollback the statements in order to return the database to its original state.; A transaction manager transaction is a series of transaction manager commands that are completed together. A transaction manager transaction, which generally starts on screen entry, can contain several database transactions.
transaction manager: A runtime program which performs the processing needed to view and update database information. Database statements are generated from settings stored in screen and widget properties.
transaction mode: One of a series of states which indicate the data entry status of a screen when using the transaction manager. Transaction modes include: initial, new, update and view.
Tuxedo: A TP monitor middleware product distributed by the Oracle Corporation.
two-tier architecture: A computer architecture that separates application functionality into two components: clients and servers. The client, or frontend, is responsible for user interactions and application logic. The server, or backend, is responsible for the management of resources, such as databases. In two-tier architecture, the client and server are usually located on different machines, with each client having a direct connection to the server.
URL: Universal Resource Locator. The primary naming scheme used to identify web resources. A URL contains the protocol to be used, the domain name of the web server where a resource resides, the port number to be used, and the directory path to access the named web document.
UML: UML (Unified Modeling Language) is a set of (mostly graphical) notations for describing object-oriented systems.
validation: The process of checking user data entry against the keystroke filters you specify in the screen editor. Validation generally occurs when a user tabs out of a field. Validation also occurs for all fields on a screen at screen exit, or when the XMIT key is pressed.
VBScript: Microsoft's scripting language.
video file: A configuration file that provides character-mode-Panther with the information required to use the capabilities of a specific terminal. Panther includes a set of video files for many different terminals. Optionally, you can define a custom video file using the instructions in the Configuration Guide.
viewport: The mechanism through which the user views all or part of a screen. The VIEWPORT key allows the user to move, resize, and scroll the viewport.
visual object repository: A special Panther library that can consist of one or more screens. Objects in repository entries can export their properties to other objects on your application screens. By copying repository objects to application screens, you create an inheritance relationship between the parent object and child object, which can be maintained to ensure consistency throughout your application.
web browser: See browser.
WebSphere Application Server: A middleware product available from IBM for distributed component processing using Enterprise JavaBeans.
widget: An object on a Panther screen. Some widgets are used to interact with an application, while others are for display only.
window: One of two ways that Panther displays a screen in an application. Unlike a screen displayed as a form , a screen displayed as a window overlays, but preserves, any screens beneath it. The open window is the active screen and the image hidden by the open window is saved, to be restored and made active again when the open window is closed. Windows can be stacked or sibling.
window stack: A list that is kept internally by Panther that allows it to remember the order in which windows were opened, or were rearranged with the VIEWPORT key. When a window closes, it is popped off the window stack, and the previous window comes to the fore.
word wrap: A property that is applied to multitext widgets. When characters are inserted, Panther wraps any text which is too lengthy for the current line onto to the next line. When characters are deleted from the field, Panther automatically fills the line with words from the next line in the field.
write-through: Intrascreen data transfer that uses local data block (LDB) screens.
XML: Extensible Markup Language. A formatting language commonly used for data interchange. Markup tags specify the meaning of the contrained information.