visualage - Synonyms for visualage | Synonyms Of visualage

Examples of "visualage"
VisualAge was the name of a family of computer integrated development environments from IBM, which included support for multiple programming languages. VisualAge was first released in the 1980s and was still available in 2011. VisualAge was also marketed as “VisualAge Smalltalk”. IBM has stated that XL C/C++ is the 'follow-on' product to VisualAge.
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.
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.
IBM VisualAge Java is an example of an integrated development environment implementing SCID features.
Various members of the family have been replaced by products in the WebSphere Studio family of products. , the original VisualAge product continues to be promoted by IBM as “VisualAge Smalltalk”. In 2005, Smalltalk specialist Instantiations, Inc. acquired a worldwide license to VisualAge Smalltalk, and offers an “enhanced product” VA Smalltalk. The C, C++ and Fortran compiler on AIX, Linux and z/OS are renamed as XL C/C++ series.
IBM VisualAge Pacbase is a code-switching structured programming language that is developed and maintained by IBM. VisualAge Pacbase runs on both IBM and non-IBM mainframes and integrates with IBM WebSphere Studio Application Developer. When compiling Pacbase code it is first translated into COBOL and then compiled to binary.
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.
IBM VisualAge for COBOL Standard is “Year 2000 ready” and Requires: Warp Version 4.0 plus FixPak 1 or Windows NT 4.0 plus Service Pack 3
In 1994 IBM released a successor product called VisualGen which incorporated "the ability to develop client/server applications (particularly the addition of Graphical User Interfaces (GUIs) to applications), the ability to access data from non-IBM vendors’ data stores, and the ability to execute application in operating environments beyond the mainframe." In 1996 this product was again renamed to VisualAge Generator. VisualAge Generator was withdrawn from service in 2009 and succeeded by Rational Business Developer.
The original prototype which led to VisualAge was an attempt "to make something like the NeXT interface builder" 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.
Also in 2001, IBM replaced the VisualAge for Java and WebSphere Studio products with WebSphere Studio Application Developer (WSAD), version 4.0. WSAD extended the Eclipse platform and included tools to develop Web services and XML applications, and for performance profiling.
The supported technologies, depending on the version, are available for Web, Java (Core and Advanced), .Net, WPF, SAP, Oracle, Siebel, PeopleSoft, Delphi, Power Builder, Stingray 1, Terminal Emulator, Flex, Web Services, Windows Mobile, VisualAge Smalltalk, Silverlight and mainframe terminal emulators.
Eclipse was inspired by the Smalltalk-based VisualAge family of integrated development environment (IDE) products. Although fairly successful, a major drawback of the VisualAge products was that developed code was not in a component-based software engineering model. Instead, all code for a project was held in a compressed lump (somewhat like a zip file but in a proprietary format called .dat). Individual classes could not be easily accessed, certainly not outside the tool. A team primarily at the IBM Cary NC lab developed the new product as a Java-based replacement.
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.
IOC was an extensive set of C++ classes used to build CLI and GUI applications which could then be easily cross-compiled to OS/2, Microsoft Windows, and AIX. IOC also formed the basis for IBM's VisualAge for C++ graphical application builder. The non-GUI portions of IOC were available for z/OS and OS/400.
Object Technology International (OTI) was founded in Ottawa, Ontario (Canada) in 1988 and acquired by IBM in 1996. OTI, in conjunction with the IBM development lab in Cary, NC, developed the VisualAge line Smalltalk and Java development tools that eventually culminated in the open source Eclipse tool platform and integrated development environment (IDE).
The initial codebase originated from IBM VisualAge. The Eclipse software development kit (SDK), which includes the Java development tools, is meant for Java developers. Users can extend its abilities by installing plug-ins written for the Eclipse Platform, such as development toolkits for other programming languages, and can write and contribute their own plug-in modules. Since Equinox, plug-ins can be plugged-stopped dynamically and are termed (OSGI) bundles
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.
The IOC was included as part of IBM's C++ compiler environment. Applications developed with IOC could be distributed with a royalty-free runtime, or could be statically linked against the IOC libraries. Initially only available for OS/2, the IOC was eventually made available for Windows, AIX, z/OS, and OS/400. Support for the OS/2 and Windows VisualAge for C++ compiler—as well as the accompanying IOC—was officially withdrawn by IBM on April 27, 2001. IOC was removed from z/OS 1.9, introduced in 2007.
IBM used parts of CommonPoint to create the Open Class class libraries for VisualAge for C++. IBM spawned an open source project called International Components for Unicode from part of this effort. Taligent also created a set of Java- and JavaBeans-based development tools called WebRunner, a groupware product based on Lotus Notes called Places for Project Teams, and licensed various technologies to Sun which are today part of Java, as well as to Oracle Corporation and Netscape. HP released the Taligent C++ compiler technology (known within Taligent as "CompTech") as its "ANSI C++" compiler, aCC. HP also released some graphics libraries that had been developed at Taligent.