Microsoft's Component Object Model [L1 ] ...
tcom offers both client and server COM functionality.
This is also included in recent ActiveTcl releases.
optcl ...
TclScript also is COM-aware.
COSH ...
Many popular Windows applications expose a COM automation [L2 ] interface, which allows external programs to launch and control them. The starting point to an application's COM automation interface is through its programmatic identifier (ProgID). Here are a few example ProgID's, any of which might be used in, for instance, tcom with
set application [::tcom::ref createobject $ProgID]
Netscape.Network.1 [http://developer.netscape.com/docs/manuals/communicator/OLE/ole2net.htm]
FrontPage.Editor.Document
Word.Document (note that WordPad is ''not'' a COM server)
InternetExplorer.Application
Excel.Application
Excel.Application.8
PDF.PdfCtrl.1
Word.Application
DSOleFile.PropertyReader
How does one discover the API for a COM-exporting application of interest? One place to start is by Googling "$app_name object model". The (full) help for most Microsoft applications includes this information, often disguised as instructions on use of Visual Basic for Applications or VBScript. These reference guides usually are not installed by default during the typical installation. They can be added later by rerunning the setup program with the custom install option. Also, one can often start the application in question, and select Tools/Macros/Visual Basic Editor, then View/$app Explorer, and the API should be within a click or two more.
You can also record a macro and then examine the code.
To record a macro
Use the following steps to record a macro:
To view a recorded macro
Use the following steps to view a recorded macro:
[Explain relation between COM and WSH.]