Abstract: A componentizing object designer is used to define a componentization of visual forms and other object-oriented technologies. The componentized object designer includes a set of tightly integrated protocols enabling Component Object Model (COM) objects to replace standard built-in visual form and other objects. The componentized object designer allows the design-time object and the run-time object to differ in implementation. The componentized object designer allows class identifiers for the run-time objects which are different than design-time objects. With a different class identifier, the run-time object can be saved as an object which is radically different from the design-time object. This enables the run-time object to be stored in a different object library than the design-time object. The componentized object designer allows for different persistence formats to be saved for run-time objects.

Abstract: A componentizing object designer is used to define a componentization of visual forms and other object-oriented technologies. The componentized object designer includes a set of tightly integrated protocols enabling Component Object Model (COM) objects to replace standard built-in visual form and other objects. The componentized object designer allows the design-time object and the run-time object to differ in implementation. The componentized object designer allows class identifiers for the run-time objects which are different than design-time objects. With a different class identifier, the run-time object can be saved as an object which is radically different from the design-time object. This enables the run-time object to be stored in a different object library than the design-time object. The componentized object designer allows for different persistence formats to be saved for run-time objects.

Abstract: A component integration system including a component manager that controls the main message loop of the application program and allows a multiplicity of components running within a single process to share in main message loop services. If the application program supports multiple threads running within a single process, then the component manager allows a multiplicity of components running within a single thread to share in main message loop services. Specifically, the component manager routes messages from the main message queue to the various components and allows the components to share in the following services: (1) allocation of idle time, (2) pretranslation of accelerator and other messages, (3) notification of program state changes, and (4) pushing the main message loop. The component manager and the cooperating components define standard interfaces for introducing new components into the application program.