home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
opendc12.zip
/
SG244883.ZIP
/
2_6.2
< prev
next >
Wrap
Text File
|
2001-01-27
|
6KB
|
128 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.2">
<title>
2.6.2 "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.2"><img src="/bookmgr/contents.gif" border=0 alt="[Contents]"></a>
<img src="/bookmgr/drevs.gif" border=0 alt="[Revisions]">
<a href="2.6.1"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="2.6.3"><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="HDR4610DS2"><H3> 2.6.2 Standard Events</H3></a>
</banner>
<pre width="80">
The current edition of OSA Event Registry: Standard Suites defines the
standard suites of OSA events, which are groups of related events that are
usually implemented together. The OSA Event Registry maintains the OSA
Event Registry: Standard Suites and other information about the ongoing
development of OSA event suites.
<p>
The standard suites include the following:
<p>
1. The required suite consists of four OSA events. These events are Open
Application, Open Documents, Print Documents, and Quit Application.
An application or component supporting OSA must support the OSA events
as described in the required suite.
<p>
2. The core suite consists of the basic OSA events, including Get Data,
Set Data, Move, Delete, and Save, that nearly all applications use to
communicate.
<p>
3. A functional-area suite consists of a group of OSA events that support
a related functional area. Functional-area suites include the text
suite and the database suite. You can decide which functional-area
suites to support according to which features your application
provides. For example, most word-processing applications should
support the text suite, and most database applications should support
the database suite.
<p>
<p>
These functional-area suites provide greater portability of OpenDoc
documents by ensuring that other part handlers compliant to the text suite
can be used on another machine for the same document, still providing the
same set of functions, defined by the text event suite. CI Labs is
maintaining the event suites.
<p>
A part handler has to register the suites it is supporting at run-time
with OpenDoc thus exposing its interface to the outside world. The suites
beyond the required suite are called <I>extensions</I>. These extensions can be
modified or extended by the part supporting a suite. A client component
or program can ask a component it wants to collaborate with, whether it is
supporting a certain extension or not. If it is supported, the client can
request access to to the interface and invoke functions provided by the
interface. (This is quite similar to what OLE offers with its IUnknown
interface, which can be asked whether an interface is supported or not.)
<p>
An OSA Event consists of the following four parts:
<p>
1. Events (for example, Open, Close, Get, Set, etc.)
2. Event objects (for example, document, word, paragraph, etc.)
3. Descriptors (for example, last, first, third )
4. Parameters (for example, bold, blue)
<p>
<B>Script</B> <B>sample</B>
<p>
<I>Put</I> <I>the</I> <I>color</I> <I>attribute</I> <I>to</I> <I>blue</I> <I>for</I> <I>all</I> <I>words</I> <I>containing</I> <I>the</I> <I>string</I> <I>"IBM"</I>
<I>in</I> <I>chapter</I> <I>5</I> <I>through</I> <I>7</I> <I>of</I> <I>document</I> <I>"Foo"</I> .
<p>
<B>Event</B> Put
<B>Event</B> <B>objects</B> Color attribute, word, string, paragraph, chapter, document
<B>Descriptors</B> All, 5 through 7, containing the string IBM
<B>Parameter</B> Blue
<p>
The scripting component maps the script commands to OSA events and sends
it to the Event Manager who figures out who the addressed application for
this event is. As shown in <a href="#FIG4610D34">Figure 34</a>, the Event Manager prepares a reply
object to give the results back to the scripting component, which can be
used as a parameter for the next event.
<p>
<a name="FIG4610D34"><hr>
</a>
<p>
<p>
<a href="picture-34?mode=zoom"><img src="/bookmgr/pictures/EZ30OZ00.P34.GIF" alt="PICTURE 34"></a>
<p>
<p>
<hr>
Figure 34. OpenDoc Description
<p>
As shown in <a href="#FIG4610D33">Figure 35</a>, the application addressed by the event must have an
event handler able to handle the request.
<p>
<p>
<a name="FIG4610D33"><hr>
</a>
<p>
<p>
<a href="picture-35?mode=zoom"><img src="/bookmgr/pictures/EZ30OZ00.P35.GIF" alt="PICTURE 35"></a>
<p>
<p>
<hr>
Figure 35. Interapplication Communication
</pre>
</pre>
<hr>
<br><a href="2.6.1"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="2.6.3"><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>