home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
opendc12.zip
/
SG244883.ZIP
/
2.0
< prev
next >
Wrap
Text File
|
2001-01-27
|
7KB
|
122 lines
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<HTML>
<HEAD>
<base href="http://publib.boulder.ibm.com:80/cgi-bin/bookmgr/BOOKS/EZ30OZ00/2.0">
<title>
2.0 "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.0"><img src="/bookmgr/contents.gif" border=0 alt="[Contents]"></a>
<img src="/bookmgr/drevs.gif" border=0 alt="[Revisions]">
<a href="1.5.2"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="2.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="HDR4610DDS"><H1> 2.0 Chapter 2. OpenDoc Description</H1></a>
</banner>
<pre width="80">
This chapter describes the basic architecture of OpenDoc and the
fundamental technology components involved with OpenDoc.
<p>
<cite>A</cite> <cite>component</cite> <cite>is</cite> <cite>a</cite> <cite>piece</cite> <cite>of</cite> <cite>software</cite> <cite>small</cite> <cite>enough</cite> <cite>to</cite> <cite>create</cite> <cite>and</cite> <cite>maintain,</cite>
<cite>big</cite> <cite>enough</cite> <cite>to</cite> <cite>deploy</cite> <cite>and</cite> <cite>support,</cite> <cite>and</cite> <cite>with</cite> <cite>standard</cite> <cite>interfaces</cite> <cite>for</cite>
<cite>interoperability.</cite> Jed Harris, President CI Labs(January 1995)
<p>
OpenDoc is the architecture that allows the creation of compound
documents. It is used in OS/2 Warp Version 3, OS/2 Warp with WIN-OS/2 or
OS/2 Warp Connect using a set of DLLs. OpenDoc was designed to facilitate
the easy construction of compound, customable, collaborative, and
cross-platform documents. By doing this, OpenDoc replaces today's
application-centric user model with a document-centric one.
<p>
If you create a compound document in an application-centric user model,
you have to use a monolithic application with lots of functions. The data
types you can use (for example, text, graphics, sound, movie) depend on
what kind of data the application can handle.
<p>
On the other hand, in a document-centric user model, the monolithic
application is replaced by many small pieces of data and functions called
components or components. Both terms are used in a synonymous way.
<p>
Components are objects that have a data part with a related behavior to
manipulate the data. This is called a part handler. You can place any
kind of component in a OpenDoc document without worrying about the data
type the component is using.
<p>
The document-centric model supports data used in documents such as text,
graphics, and spreadsheet. It also supports movies, sounds, animation and
database information, such as calendars shared over the network. Because
it has standard interfaces of interoperability, it is open to new data
types and technologies developed in the future. Because of the
standardized way of interoperability, components can be developed from
different vendors without knowing each other.
<p>
OpenDoc is the implementation of such a document-centric model. OpenDoc
fundamentally changes the conventional meaning of the term document. In
today's computing environment, a document is tied to the application that
will let the user view, edit and print its content.
<p>
An OpenDoc document differs from traditional documents in that it consists
of objects. These objects may be text objects, graphics objects,
spreadsheet objects, movie objects, sound objects, animation, image
objects and even a push button. Those objects are handled (created,
modified) by their specific programs called <I>part</I> <I>handlers</I>, but are stored
in one data file. Part handlers are programs that allow you to view,
create or modify part's contents.
<p>
In addition, OpenDoc is the ideal architecture for multimedia documents.
In OpenDoc, each new medium that is or will be developed (for example,
video, sound, animation, and simulation) can be embedded as a component in
any OpenDoc document.
<p>
Although OpenDoc lends itself directly to a complex and sophisticated
layout, its usefulness is by no means restricted to page-layout kinds of
applications or even compound documents.
<p>
Components are pieces of software developed independently from each other
that are able to interoperate. These components are to be bought from the
shelves to be plugged together from experienced users or system
integrators. The parts can be updated, replaced by other components
without interfering the parts they are working with.
<p>
It is very similar to the plug and play philosophy we see on the hardware
side. If you plug in a new card, the appropriate drivers should be loaded
dynamically and other software can interoperate immediately with this card
without being newly configured.
<p>
To enable this plug and play behavior of components, it is obvious that an
architecture must standardize the interfaces. These interfaces are
addressed by OpenDoc.
<p>
<p>Subtopics:
<ul>
<li> <a href="2.1"> 2.1 Architectural Overview</a>
<li> <a href="2.2"> 2.2 Component Services</a>
<li> <a href="2.3"> 2.3 All About Parts</a>
<li> <a href="2.4"> 2.4 Compound Document Services</a>
<li> <a href="2.5"> 2.5 OpenDoc Storage</a>
<li> <a href="2.6"> 2.6 Open Scripting Architecture</a>
<li> <a href="2.7"> 2.7 OpenDoc Object Model</a>
<li> <a href="2.8"> 2.8 Interoperability Layer</a>
<li> <a href="2.9"> 2.9 OpenDoc Tools for Creating Components</a>
</pre>
</ul>
<hr>
<br><a href="1.5.2"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="2.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>