home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
opendc12.zip
/
SG244883.ZIP
/
1_3.1
< prev
next >
Wrap
Text File
|
2001-01-27
|
6KB
|
119 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.1">
<title>
1.3.1 "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.1"><img src="/bookmgr/contents.gif" border=0 alt="[Contents]"></a>
<img src="/bookmgr/drevs.gif" border=0 alt="[Revisions]">
<a href="1.3"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="1.3.2"><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.1 Document-Centric Computing</H3>
</banner>
<pre width="80">
<p>
With the advent of OpenDoc and other compound document architectures, such
as Object Linking and Embedding (OLE) and the document framework in
Taligent, focus has switched from application-centric to document-centric.
<p>
If you have to load a document, such as a spreadsheet, think about the
steps that you go through. If you are still working in an
application-centric approach, you would open the application that you use
to work on the spreadsheet. Then you would load the spreadsheet from the
application. This means that you have to go first to the folder that
contains the application icon. Then you open the application, and then
you have to remember where you saved the data file with the full path name
and name of the spreadsheet.
<p>
In a document-centric approach you are working differently. The documents
could all be stored in a single folder, for example, the word processor,
spreadsheets and database data files could all be in a My Documents
folder. When you want to work on one of these document, for example, a
spreadsheet, you would click on the spreadsheet icon. This will load the
application into memory and then load the spreadsheet that you have
selected into the spreadsheet program. This will apply for example, word
processor files and database files. The difference is that you will not
have to remember which application is used for which data file. The
environment in which you work will have that information. You can do this
in OS/2. You can have all your data files in one folder and OS/2 knows
what type of file it is, for example, plain text or icon file, and when
you double-click on the data file, it loads it into the appropriate
application, such as the Icon Editor.
<p>
With OpenDoc we go one step further. There is no application icon for
OpenDoc documents. You load the documents by clicking on the documents as
there is no application that you can start to load the document into.
Inside the document, you have different components, and when you click on
those components, OpenDoc loads the application to work with that specific
component.
<p>
In a document-centric computing model, users can focus on the documents
they want to create rather than the applications ability to produce the
document required. Users can see a document that has several components
or applications embedded and integrated into a single document.
<p>
<a name="FIG4610WPF"><hr>
</a>
<p>
<p>
<a href="picture-3?mode=zoom"><img src="/bookmgr/pictures/EZ30OZ00.P3.GIF" alt="PICTURE 3"></a>
<p>
<p>
<hr>
Figure 3. An OpenDoc Document with Text, Graphics and Video Components
<p>
These components are called parts that can now be included, and are
dependent only on the availability of a part handler (editor and viewer).
Some parts and features that you will first see in these documents include
the following:
<p>
░ Formatted text
<p>
░ 2-D and 3-D graphics
<p>
░ Images
<p>
░ Audio
<p>
░ Video
<p>
░ Ticker Tapes
<p>
░ Structured data, such as appointments and calendars
<p>
░ User interface control structures
<p>
░ Inter- and intra-document links
<p>
░ Document draft control
<p>
<p>
<a href="#FIG4610WPF">Figure 3</a> is an example of an OpenDoc document that contains a number of
parts or components. These include text, graphics and video. Notice that
the graphics component is the active component.
</pre>
</pre>
<hr>
<br><a href="1.3"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="1.3.2"><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>