To build a compound document server application in DUIM, write your application as you would a normal DUIM application, but with the few differences summarized below.
DUIM-OLE-Server module in your server application's library and module definitions.
<embeddable-frame>.
<simple-frame>, define it as a subclass of <embeddable-frame> (page 146).
<embeddable-frame> with make, supply a class-id: argument (whose value is usually created by make-GUID, page 351). This argument is recorded next to the name of the server application in the Windows registry; it is the key that client applications use to find the server application. There are other, optional arguments that allow further control over registration. See <embeddable-frame>, page 146.
save-frame-to-storage (page 159) and load-frame-from-storage (page 160). These functions handle your server application's persistent data, ensuring that it can be saved as part of a compound document and reloaded next time the user accesses the compound document. When your application needs to save its data, call note-embedded-data-changed (page 155) on the instance of <embeddable-frame>.
frame-status-message for application status bar messages
frame-status-bar, use this idiom:
frame-status-message(frame) := "Message-text string";
For more information, see the code for the DUIM OLE Scribble example in:
Examples\duim-ole\ole-scribble\