Jun 12, 2009 7:00 AM
Your Help in Defining The Direction of VisualAge for RPG
Hi. Those of us at IBM who are committed to bringing you the latest RPG programming tools such as the ones in RDi, are continually searching for new ways to improve your productivity and competitiveness. One of the tools that we have always been proud of is VisualAge for RPG. Due to our priorities in bringing you an integrated set of tools, such as Remote Systems Explorer, Application Diagram, Screen Designer and a full line of source editors, VisualAge for RPG was unable to be given as much attention as some of its users have asked for. We would like to request your help in defining a direction for VisualAge for RPG.
For those of you who are unfamiliar with VisualAge for RPG, here is a quick overview. VisualAge for RPG allows RPG programmers to create applications that run on a desktop operating system, while accessing an IBM i back end. VisualAge for RPG introduced three concepts to RPG programmers.
The first concept is a graphical user interface. A design tool allows RPG programmers to assemble an application's graphical user interface without having to write any user interface code. User interface 'parts' are dragged from a palette onto a design area. The user interface definition is saved in a workstation file. At runtime, the application's user interface is automatically created from the user interface definition contained in the file. VisualAge for RPG has over forty types of parts, including common parts such as Checkbox, Image, Menu Item and Window, as well as more familiar ones, such as Subfile and Message Subfile, and utility parts such as Timer.
The user interface definition that is stored in a workstation file is portable across operating systems. This portability has allowed us to provide runtimes for OS/2, various Windows platforms, as well as Java Swing and Java applets capable of running in a web browser. As operating systems became available, VisualAge for RPG has provided runtimes to match, without requiring changes to the application's RPG code.
The second concept is event driven programming which is a common feature of other modern programming languages. In order to facilitate this concept, action subroutines were added to RPG. These subroutines are called when a user interface event, such as a button press,or subfile record selection occurs. At design time, RPG programmers decide which of their action subroutines are called when a user interface event occurs.
The third concept is that of reusable components where a component is defined as a pairing of a user interface definition and its associated RPG code. When an application starts, a user interface is created from a component's user interface definition, and the component's associated RPG code is executed whenever user interface events occur. An additional opcode allows an RPG programmer to load a second component from within the starting component. When this happens, the second component's user interface is created from its user interface definition and added to the application's user interface, and the second component's associated RPG code is executed whenever user interface events occur in the second component's user interface. Any component may be an application's starting component, and any component may load another component as a sub-component.
VisualAge for RPG continues to be used for a wide variety of applications. Some of these rich client applications consist of multiple reusable components with very complex user interfaces. Those of us who develop tools for your use, would like to hear from you. We desire to attain a better feel for the number of users of VisualAge for RPG, and applications that are currently deployed. We would also like to hear your ideas about the direction we should take VisualAge for RPG. Should we provide the ability for your existing applications to run on other platforms such as Linux, and the newest netbooks? Perhaps your applications could be purchased and downloaded from a web site, and could update themselves when you made a new update available. As usual, we appreciate the time that you spend in helping define the future direction of any of our products. Thanks ahead to those who contribute input to a possible future for VisualAge for RPG by replying to this post.
Tags:
visualage_for_rpg,
rpg,
rdi
