You can use many kinds of parts to construct program elements. All parts exist as either primitives or composites. Primitive parts are the basic building blocks from which composites are constructed. You must construct new primitive parts using a programming language because there are no similar parts to use in building them. Primitive parts can be either visual or nonvisual.
Visual parts are elements of the program that the user can see at run time. The development-time representations of visual parts in the Composition Editor closely match their runtime visual forms. Users can edit these parts in the Composition Editor in their visual runtime forms. Examples include windows, entry fields, and push buttons. In general, visual parts are subclasses of IWindow.
Nonvisual parts are elements of the program that are not necessarily seen by the user at run time. On the Composition Editor's free-form surface, users can manipulate these parts only as icons. Examples include business logic, database queries, and communication access protocol parts.
Parts that have a visual representation at run time but do not support visual editing are treated as nonvisual. Examples of this kind of nonvisual part include message boxes and file selection dialogs.
Composite parts can contain both visual and nonvisual components. In general, composite parts are based on one of these classes:
How Classes and Parts Are
Related
Visual Composition
Primary Part
VisualAge Component Model
Incorporating
User-Written Code into Visual Composites
