home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
opendc12.zip
/
SG244883.ZIP
/
1_4.3
< prev
next >
Wrap
Text File
|
2001-01-27
|
9KB
|
156 lines
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<HTML>
<HEAD>
<base href="http://publib.boulder.ibm.com:80/cgi-bin/bookmgr/BOOKS/EZ30OZ00/1.4.3">
<title>
1.4.3 "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.4.3"><img src="/bookmgr/contents.gif" border=0 alt="[Contents]"></a>
<img src="/bookmgr/drevs.gif" border=0 alt="[Revisions]">
<a href="1.4.2"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="1.4.4"><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.4.3 Benefiting the User</H3>
</banner>
<pre width="80">
<p>
Users want ways to create content-rich collaborative documents. They need
to work quickly and efficiently, and have the flexibility to choose
applications. OpenDoc will allow users to seamlessly integrate text,
graphics, tables, multimedia, scripts and other forms of content into a
single working document. Instead of having to maneuver among
applications, users will easily access any tool or editor to embed
different types of content into a compound document. This means that the
user will focus more naturally on the task at hand. OpenDoc will ease the
computing experience, while ensuring a greater level of customizability
and flexibility.
<p>
<a name="FIG4610WPA"><hr>
</a>
<p>
<p>
<a href="picture-4?mode=zoom"><img src="/bookmgr/pictures/EZ30OZ00.P4.GIF" alt="PICTURE 4"></a>
<p>
<p>
<hr>
Figure 4. Text and Graphics Editing
<p>
For example,<a href="#FIG4610WPA"> Figure 4</a> shows you how text and graphics are used in the same
document but the document contains two different components. The text
component, on the left, is supported by a text editor, and the graphics
component, on the right, is supported by a separate graphics editor. We
now have a full text editor, in other words a word processor, and a
graphics editor, or a paintshop, in the same application.
<p>
The base menu options stay the same for each component and each component
adds one additional menu item. This menu item will change depending on
which component is active, for example, the text component has the Options
menu item, and the graphics component has the Select menu item. Each
component has its own pop-up menus and <a href="2.3.4.1#FIG4610D60">Figure 14 in topic 2.3.4.1 </a>shows
the pop-up menu for the text component. You would not have to learn the
different commands, menus, or setup for either the graphics, or the text
program. This is not limited to only the test and graphics components but
applies to all OpenDoc components.
<p>
OpenDoc's most obvious benefit to end users is enhanced usability.
OpenDoc provides users with a more natural and flexible way to create
compound documents combining information of various types. In OpenDoc,
the term document includes virtually all applications and almost anything
that a computer can output. OpenDoc documents can be alive, not static.
Such things as animation, background music and a dynamically changing
content can all be part of an OpenDoc document.
<p>
OpenDoc components or parts will not be delivered to end users as
traditional applications. Instead, users will be given templates
(graphically represented by Templates on the desktop) that can be used to
assemble documents. To add text, graphic, audio, video and chart parts to
a document, the user simply has to drag the corresponding template for
that type of part into the document types you need.
<p>
Parts can also be complex, such as a part for a monthly report that
combines smaller text, spreadsheet, and chart parts. Unlike most OLE
objects, OpenDoc components can contain other components or be put in
other components, giving the user the unlimited ability to customize the
document to suit the user's changing needs. Changes to parts, such as
editing text or changing a graph can be made in place, without leaving the
document and without having to stop and think about which application
created the original. This technique of creating documents puts the
user's focus back on the content and layout of the document, and away from
the intricacies of using a particular application.
<p>
Another benefit of this approach is that users can purchase only the
OpenDoc "parts" they need. Today's software market is dominated by
pre-packaged, shrink wrapped, full-featured applications from a handful of
software vendors. End users pay for functions they will never use, while
being limited by the capabilities built into the application. On the
other hand, users who purchase OpenDoc component software pay only for
those functions they want because the components perform very specific
functions. Users can assemble those small components in creative ways to
solve their unique problems, instead of relying on huge, inflexible,
one-size-fits-all programs. Users can also mix-and-match components from
different vendors without any concerns about compatibility.
<p>
OpenDoc components are re-usable and scriptable, which will encourage
developers to create specialized solutions to very specific problems
quickly with minimal incremental development costs. For example, an
invoice generation package can be custom tailored for the mail order
industry, and further tailored for mail order clothing companies, mail
order software companies and so on.
<p>
OpenDoc also eliminates the need to replace an application in order to
upgrade its functions. New or improved functions can be added by
installing focused parts. This can prevent the premature obsolescence of
software and relieve the headaches and spiraling costs associated with
software upgrades.
<p>
More sophisticated users will enjoy the flexibility OpenDoc's powerful OSA
architecture gives them. OSA allows you to tie together functions using
macro-like scripts. If you are used to using spreadsheet or word
processing macros today, then you'll appreciate OpenDoc's record-playback
facility which gives you the ability to automate repetitive tasks. For
instance, if you need to complete a form at the end of every business day
using information from a wide variety of sources and media, OSA allows you
to record that operation once, name it, and run it again whenever you
like. If other users in your organization need to perform similar tedious
tasks, they can simply edit the script for the function that you've
written to adapt it to their tasks. The functions that you can write
resembles a language close to plain English.
<p>
OpenDoc can be used on different platforms on heterogeneous networks
making it much easier for large organizations to integrate OpenDoc
components throughout their organization. OpenDoc will make it easier for
workgroups and individuals on a network to collaborate all kinds of
information and documents will be able to flow freely to all users within
the enterprise environment.
<p>
OpenDoc provides greater flexibility by allowing you to choose the
functions you want from software components, and adapting components to
suit your specific needs. OpenDoc can assist you to work more
productively by providing an intuitive interface that allows you to focus
your attention on your work and not the software. Finally, OpenDoc can
empower you to be more creative and do things you can't do with today's
software applications.
</pre>
</pre>
<hr>
<br><a href="1.4.2"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="1.4.4"><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>