Visual Programming Fundamentals

VisualAge for C++ includes a state-of-the-art object-oriented visual composition editor for assembling applications visually from IBM Open Class components.

Object-oriented programming facilitates development of complex software systems by breaking them up into a number of much smaller, simpler program elements called objects. Objects work together by sending each other messages, that is, by requesting behavior that is implemented by the target object. Taken as a group, these behaviors comprise a class interface.

Using an object-oriented approach for complex systems provides the following benefits:

Despite these benefits, implementing large systems can still be expensive. One way to reduce the cost is to reuse object implementations. Many companies would prefer to buy reliable reusable classes, creating classes only for functions specific to their business. This vision of constructing custom software using standard building blocks has been called construction from parts. The building blocks themselves have popularly been called parts or components.

However, reuse is hard to achieve when the class interfaces are too specific to the application for which they were originally developed. To promote wider reuse, class interface conventions called component models have been defined, such as ActiveX, OpenDoc, and JavaBeans.

The IBM notification framework of the IBM Open Class library is the component model used by VisualAge. The IBM notification framework includes the following definitions:

An event model. Event models specify how a component sends messages to other objects without knowing the exact methods that the other object implements. This enables a component to be reused with a range of objects that have different interfaces

Events, attributes, and actions. The IBM notification framework defines a component interface in terms of the events it can signal, the attribute values that can be read and set, and the actions it implements. This definition provides more structure to the interface of a component compared with a simple class interface, facilitating the use of tools such as the VisualAge Composition Editor.

The Composition Editor enables you to create programs graphically from existing parts. Parts are simply C++ classes that comply with the IBM notification framework. The IBM notification framework is the component model supported and used throughout VisualAge, so this documentation will refer to VisualAge components as parts.

VisualAge provides user interface parts based on classes in the IBM Open Class library. The Composition Editor is also extensible. It allows you to work with parts you create yourself, and it allows you to include parts imported into the environment from other sources. You can even create your own parts graphically using the Composition Editor and then reuse these parts again within another program being created with the Composition Editor.

To build a program with the Composition Editor, you draw a picture using a canvas and palette of icons representing reusable parts. This picture specifies the set of parts that implements the function of the larger program (or part) you are creating. For parts like user interface controls, the position of the controls relative to each other in the picture specifies how the controls will appear in the final program. For parts such as database components, the position of the part in the picture generally has no significance.

The Composition Editor provides a very sophisticated connection capability to specify how components of the picture will interact to implement functions of the program. Using connections, much of the behavior of an application can be specified graphically. Connections also allow you to integrate custom code written in the C++ language.


Related concepts
How Classes and Parts Are Related
Visual Composition
Part Design Guidelines