1. Early History

VisualAge was born in the IBM development lab in Cary, North Carolina, which was established in 1984 and had responsibility for application development tools. The EZ-VU dialog manager product, a personal computer derivative of the user interface elements of the ISPF 327x product was one of the first products in this family. The lab also had a group which was one of the early adopters of object-oriented programming technologies within IBM using an internally developed language called ClassC to develop applications with more sophisticated graphical user interfaces which were just starting to be widely available.

Eventually, the availability of usable implementations of Smalltalk for IBM PC-AT class machines allowed IBM advanced technology projects to experiment with Smalltalk. At about the same time, visual interface construction tools were coming up on the radar screens. Smalltalk research projects such as InterCons by David N. Smith of IBM, and Fabrik by a team at Apple led by Dan Ingalls were building interactive graphical applications built from composition of graphical primitives. Higher level construction of user interfaces was evidenced by other tools such as Jean-Marie Hullot's interface builder first done in Lisp and then evolved to become the Interface Builder tool in NeXTStep, and later Mac OS X, which allowed for building user interfaces by WYSIWYG composition of UI widgets which could be "wired" to each other and to application logic written in Objective-C.

The original prototype which led to VisualAge was an attempt "to make something like the NeXT interface builder"^[1] within the Smalltalk/V development environment. By the time VisualAge was released as a product, much more emphasis was placed on visual construction of application logic as well as of the user interface. This emphasis was in part due to the "positioning" for "strategic" reasons of Smalltalk as a generator rather than a language within IBM's Systems Application Architecture.

1.1. Name Brand

The name VisualAge was the result of a contest between the members of the development team. After the initial release of VisualAge/Smalltalk the name VisualAge became a brand of its own and VisualAges were produced for several different combinations of languages and platforms.

Languages (not every language is available on every platform listed):

• BASIC
• COBOL
• C
• C++
• EGL
• Fortran
• Java
• Pacbase
• PL/I
• IBM RPG
• Smalltalk

Platforms:

• IBM AIX
• OS/2
• i5/OS (formerly named OS/400)
• Linux
• Mac OS X
• Microsoft Windows
• TPF
• z/VM
• z/OS (formerly named OS/390, MVS)
• z/VSE

1.2. Evolution

Most of the members of the VisualAge family were written in Smalltalk no matter which language they supported for development. The IBM implementation of Smalltalk was produced by Object Technology International which was acquired by IBM and run as a wholly owned subsidiary for several years before being absorbed into the overall IBM organization.

VisualAge for Java was based on an extended Smalltalk virtual machine which executed both Smalltalk and Java byte codes. Java natives were actually implemented in Smalltalk.^[1]

VisualAge Micro Edition, which supported development of embedded Java applications and cross system development, was a re-implementation of the IDE in Java. This version of VisualAge morphed into the Eclipse Framework.

Various members of the family have been replaced by products in the WebSphere Studio family of products. (As of 2009), the original VisualAge product continues to be promoted by IBM as “VisualAge Smalltalk”.^[2] In 2005, Smalltalk specialist Instantiations, Inc.^[3] acquired a worldwide license to VisualAge Smalltalk, and offers an “enhanced product” VA Smalltalk.^[4][5] The C, C++ and Fortran compiler on AIX, Linux and z/OS are renamed as XL C/C++ series.

2. Released Versions

Applications designed with VisualAge C++ could be portable between platforms without any code changes needed (Windows, OS/2, AIX, Linux etc) if VisualAge guidelines were followed. IBM also included additional tools and libraries in instances where portability was not possible without code changes.^[6]

2.1. OS/2 and Windows

• VisualAge C++ 3.0 (OS/2 & Windows)
• VisualAge C++ 3.5 (Windows 95/NT only)
• C and C++ Compilers for OS/2, AIX and Windows NT Version 3.6
• VisualAge C++ Professional 4.0 (OS/2 and Windows)
• VisualAge Generator Developer V3.1 for OS/2
• VisualAge Generator Server V3.1 for OS/2^[7]
• VisualAge for OS/2 1.0 (1993-10-12)^[8]
• VisualAge COBOL for OS/2 1.0 (1994-03-29)^[9]
• VisualAge for COBOL for OS/2 1.1
• VisualAge for COBOL for OS/2 1.2
• VisualAge for COBOL for OS/2, Version 1 Release 2
• VisualAge COBOL for OS/2 2.0
• VisualAge for COBOL Version 2.1
• VisualAge COBOL 2.2
• VisualAge COBOL Enterprise 3.07 (Windows only)

2.2. OS/400

• VisualAge C++ for AS/400 V3R6
• VisualAge C++ for AS/400 V3R7
• VisualAge C++ for AS/400 V4R4

2.3. AIX

• VisualAge C++ Professional for AIX
• VisualAge C++ Professional for AIX, V5.0
• VisualAge C++ Professional for AIX, V6.0

2.4. POWER Linux

• VisualAge C++ V6.0 for Linux
• VisualAge C++ V6.0 for Linux refresh