home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
opendc12.zip
/
SG244883.ZIP
/
2.6
< prev
next >
Wrap
Text File
|
2001-01-27
|
7KB
|
139 lines
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<HTML>
<HEAD>
<base href="http://publib.boulder.ibm.com:80/cgi-bin/bookmgr/BOOKS/EZ30OZ00/2.6">
<title>
2.6 "OS/2 WARP and OpenDoc"
via IBM BookManager BookServer
</title>
</head>
<body background="/bookmgr/backdrop.gif">
<banner><br>
<a href="../../library"><img src="/bookmgr/libicon2.gif" border=0 alt="[Library]"></a>
<a href="CONTENTS#2.6"><img src="/bookmgr/contents.gif" border=0 alt="[Contents]"></a>
<img src="/bookmgr/drevs.gif" border=0 alt="[Revisions]">
<a href="2.5.2.3"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="2.6.1"><img src="/bookmgr/next.gif" border=0 alt="[Next Topic]"></a>
<a href="../../search?book=EZ30OZ00"><img src="/bookmgr/search.gif" border=0 alt="[Search]" ></a>
<img src="/bookmgr/dslist.gif" border=0 alt="[Search Results]">
<img src="/bookmgr/dsprev.gif" border=0 alt="[Prev Topic Match]">
<img src="/bookmgr/dsnext.gif" border=0 alt="[Next Topic Match]">
<img src="/bookmgr/dnotes.gif" border=0 alt="[Notes]">
<img src="/bookmgr/dlnotes.gif" border=0 alt="[List Notes]">
<a href="../../print?book=EZ30OZ00"><img src="/bookmgr/print.gif" border=0 alt="[Print]"></a>
<a href="../../download/EZ30OZ00.boo"><img src="/bookmgr/download.gif" border=0 alt="[Download]" ></a>
<a href="../../help/book"><img src="/bookmgr/help.gif" border=0 alt="[Help]"></a>
<hr>
<a name="HDROSA"><H2> 2.6 Open Scripting Architecture</H2></a>
</banner>
<pre width="80">
<p>
<a name="FIG4610D53"><hr>
</a>
<p>
<p>
<a href="picture-32?mode=zoom"><img src="/bookmgr/pictures/EZ30OZ00.P32.GIF" alt="PICTURE 32"></a>
<p>
<p>
<hr>
Figure 32. OpenDoc Open Scripting Architecture
<p>
One of the major goals of OpenDoc is to increase the level of
customization that you can do with documents or applications. Experienced
users or system integrators want to do much more with components than just
assemble them. Many tasks can be automated. OSA provides the automation
technique done by scripts. OSA defines also how components can
collaborate and communicate using events. OSA enables collaboration
between components beyond the very basic mechanisms of layout and resource
negotiations OpenDoc is dealing with, as described in <a href="2.3.2.1#HDR4610DFF">"Frames and Facets"</a>
<a href="2.3.2.1#HDR4610DFF">in topic 2.3.2.1</a>. These OSA events can be launched either directly or by
scripts. Scripts can be attached to parts, and a user-interface control
such as a button might consist of nothing more than a part that executes a
script when activated.
<p>
Scripts are programs executed by interpreters. Scripting forms a rich
medium for coordinating the work of parts in documents, and allows you and
parts to work together to perform tasks.
<p>
Today script programs are the base for an agent technology. They can be
small pieces of code that can perfrom specific tasks such as buying or
selling shares. They may be coded so that they control whether a stock is
bought or sold depending on its price. They could also be coded to
collect infromation from different internet sites. The scripting language
provided with OS/2 is REXX. Because OS/2 TCP/IP is providing a socket API
and an OS/2 FTP API for REXX, it is possible to run REXX programs also on
the Internet.
<p>
REXX, with its extension to Object REXX as delivered with the The
Developer Connection for OS/2 Volume 9 Special Edition, can also be used
as a scripting language for OSA, to enable collaboration between parts or
to customize OSA-aware applications.
<p>
The implementation of this collaboration between parts in an OS/2
environment is called the interapplication communication (IAC). The IAC
architecture comprises the following parts, as shown in the next figure
<a href="#FIG4610D32">Figure 33</a>:
<p>
1. Open scripting architecture (OSA) provides a mechanism that allows
users to control multiple applications by means of scripts, or sets of
instructions, written in a variety of scripting languages. Each
scripting language has a corresponding scripting component that is
managed by the Component Manager. When a user executes a script, the
scripting component sends OSA events to one or more applications to
perform the actions the script describes.
<p>
2. OSA Event Manager allows applications to send and respond to OSA
events.
<p>
3. Presentation Manager allows applications to send and respond to
high-level events other than OSA events.
<p>
<p>
<a name="FIG4610D32"><hr>
</a>
<p>
<p>
<a href="picture-33?mode=zoom"><img src="/bookmgr/pictures/EZ30OZ00.P33.GIF" alt="PICTURE 33"></a>
<p>
<p>
<hr>
Figure 33. Interapplication Communication
<p>
OSA is based on events. OSA extends the existing messaging mechanism
provided by Presentation Manager in OS/2 by semantic messages. That means
the objects addressed by a message can be described in a semantic way.
For example in <a href="2.6.2#FIG4610D34">Figure 34 in topic 2.6.2</a>. The script command:
<p>
<samp>copy</samp> <samp>table</samp> <samp>"Summary</samp> <samp>of</samp> <samp>Sales"</samp> <samp>to</samp> <samp>Totals</samp>
<p>
describes the object's table and totals in a very general semantic way.
For further explanation see also<a href="2.6.2#HDR4610DS2"> " Standard Events" in topic 2.6.2</a>. OSA
provides a set of common event suites the components collaborating can
agree on. The scripting component provides human-language equivalents to
OSA event codes. OSA allows users to record their actions in the form of
a script when using a scripting component that supports recording. The
recording is not supported in the current release by REXX. OSA allows
provides the infrastructure to manipulate and execute scripts via a script
editor. These OSA events can be generated by scripting components as REXX
or sent directly by applications. The most important requirement for
high-level communication among all applications is a common vocabulary of
events. High-level events that conform to this protocol are called OSA
events.
<p>
<p>Subtopics:
<ul>
<li> <a href="2.6.1"> 2.6.1 OSA Events</a>
<li> <a href="2.6.2"> 2.6.2 Standard Events</a>
<li> <a href="2.6.3"> 2.6.3 Event Objects</a>
<li> <a href="2.6.4"> 2.6.4 Script</a>
</pre>
</ul>
<hr>
<br><a href="2.5.2.3"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="2.6.1"><img src="/bookmgr/next.gif" border=0 alt="[Next Topic]"></a>
<cite> ⌐ Copyright IBM Corp. 1996</cite>
<HR><p><h6><a href="/cgi-bin/bookmgr/library">IBM BookManager« BookServer</a> Copyright 1989, 1999<a href="http://www.ibm.com/"> IBM</a> Corporation. All rights reserved.</h6><p>
</BODY></HTML>