home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
opendc12.zip
/
SG244883.ZIP
/
1_3.2
< prev
next >
Wrap
Text File
|
2001-01-27
|
4KB
|
77 lines
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<HTML>
<HEAD>
<base href="http://publib.boulder.ibm.com:80/cgi-bin/bookmgr/BOOKS/EZ30OZ00/1.3.2">
<title>
1.3.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#1.3.2"><img src="/bookmgr/contents.gif" border=0 alt="[Contents]"></a>
<img src="/bookmgr/drevs.gif" border=0 alt="[Revisions]">
<a href="1.3.1"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="1.3.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>
<H3> 1.3.2 Compound Documents</H3>
</banner>
<pre width="80">
<p>
A fundamental concept of a compound document is that it can hold different
types of data called <I>document</I> <I>parts</I>. Each document part is handled by an
independent application called part handler. Each part handler
understands its own intrinsic content, and even though other kinds of
parts can be embedded into it, it need not know anything about the
intrinsic content of that embedded part.
<p>
The integration and cooperation of the parts are handled by the
architecture, policies, and protocols of the compound document system.
Other differences diverge a document consisting of parts from a document
created by a conventional application. The following are some of the
differences between conventional and OpenDoc documents:
<p>
<p>
<p>
<B>Content</B> <B>is</B> <B>not</B> <B>limited.</B> Users are not limited to the kind of content, such
as text, that can be put into a document. The only practical
limitation is the availability of a part handler, an editor or
viewer. As new part editors become available, they can be used
immediately.
<p>
<B>Content</B> <B>is</B> <B>assembled</B> <B>differently.</B> The user will rely more heavily on the
clipboard and drag-and-drop mechanisms.
<p>
<B>Part</B> <B>handlers</B> <B>can</B> <B>be</B> <B>exchanged.</B> Users can replace part handlers to fit
their needs. This can be done independently of existing
documents (which do not depend on a specific part editor).
<p>
<B>Pervasive</B> <B>use</B> <B>of</B> <B>links</B> <B>for</B> <B>data</B> <B>transfer</B> <B>and</B> <B>navigation.</B> These links can
be both internal to the document, such as hypertext type links,
and external to the document for data transfer and navigation,
for example, spreadsheet data in a text document that will
change dynamically when you change the spreadsheet, either in
the document or in a spreadsheet.
<p>
<p>
Compound document creation has undergone major changes during the last 25
years. We will now be looking in more detail at the OpenDoc technology.
</pre>
</pre>
<hr>
<br><a href="1.3.1"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="1.3.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>