Adapting User-Written Classes for Use as Parts

This topic is geared toward classes that would become nonvisual parts. To adapt GUI classes for use as visual parts, start at Deriving from Visual Classes and read the topic that suits your particular circumstance.

  1. Design the part interface.
  2. Modify your code to support the part interface.
  3. Define the part interface using part information statements.
  4. Import the part information.
  5. Extend the part interface with new features as needed.

If you add a new action feature with the same name as a member function you have already written, VisualAge replaces the existing member function.


Related concepts
Part Design Guidelines
Generated Code

Related procedures
Defining Part Interfaces for Visual Composition
Specifying Code Files
Adding Part Information for Visual Composition
Assembling a Part from Generated and User-Written Code