ToolTalk User's Guide

Integrated Toolsets

Another significant application for which the Desktop Services Message Set can be implemented is integrated toolsets. These environments can be applied in vertical applications (such as a CASE software developer toolset) or in horizontal environments (such as compound documents). Common to both of these applications is the premise that the overall solution is built out of specialized applications designed to perform one particular task well. Examples of integrated toolset applications are text editors, drawing packages, video or audio display tools, compiler front-ends, and debuggers. The integrated toolset environment requires applications to interact by calling on each other to handle user requests. For example, to display video, an editor calls a video display program; or to check a block of completed code, an editor calls a compiler. The following scenario illustrates how Desktop Services Message Set might be implemented as an integrated toolset:

  1. George is working on a compound document using his favorite editor.

    He decides to change some of the source code text.

  2. George double clicks on the source code text.

    1. The Document Editor first determines the text represents source code and then determines what file contains the source code.

    2. The Document Editor sends an edit message request, using the file name as a parameter for the message.

    3. The ToolTalk session manager matches the pattern in the edit message to a registered application (in this case, the Source Code Editor), and finds an instance of the application running on George's desktop.

      Note –

      If the ToolTalk session manager does not find a running instance of the application, it checks the statically-defined ptypes and starts an application that best matches the pattern in the message. If none of the ptypes match, it returns failure to the Document Editor application.

    4. The Source Code Editor accepts the edit message request.

    5. The Source Code editor determines that the source code file is under configuration control, and sends a message to check out the file.

    6. The Source Code Control application accepts the message and creates a read/write copy of the requested file. It then passes the name of the file back to the Source Code Editor.

    7. The Source Code Editor opens a window that contains the source file.

  3. George edits the source code text.