home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
opendc12.zip
/
SG244883.ZIP
/
2_3_2.1
< prev
next >
Wrap
Text File
|
2001-01-27
|
7KB
|
150 lines
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<HTML>
<HEAD>
<base href="http://publib.boulder.ibm.com:80/cgi-bin/bookmgr/BOOKS/EZ30OZ00/2.3.2.1">
<title>
2.3.2.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#2.3.2.1"><img src="/bookmgr/contents.gif" border=0 alt="[Contents]"></a>
<img src="/bookmgr/drevs.gif" border=0 alt="[Revisions]">
<a href="2.3.2"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="2.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>
<a name="HDR4610DFF"><H4> 2.3.2.1 Frames and Facets</H4></a>
</banner>
<pre width="80">
<p>
The logical structure of a document, which underlies its graphical
presentation, consists of the embedding relationships among its parts and
their frames as shown in<a href="#FIG4610D46"> Figure 11</a>.
<p>
A frame is an area of the display screen that represents a component.
Frames are normally rectangular, but they need not be.
<p>
Like icons, frames can do the following:
<p>
░ Provide a handle onto parts, allowing parts to be manipulated as a
whole
<p>
░ Be dragged on the desktop and between windows
<p>
░ Be the target for drops during drag operations
<p>
░ Be opened into windows and closed back into frames
<p>
░ Be closed into icons and reopened back into frames
<p>
<p>
Unlike an icon, however, a frame allows a part's contents to be seen and
edited.
<p>
Frames show how a document is composed of embedded parts.
<p>
Frames allow a part's content to be edited in place, without requiring the
user to open separate windows. In addition, there may be many frames
showing the content of a single part.
<p>
For example, when editing a 3D drawing, the user may wish to see a top
view, side view, face-on view, and wire-frame view. Or, a part might
provide a graphical and tabular view of its contents. Or, the header on a
page layout part might be showing the same part on each page of a
document. Any change the user makes in one frame is immediately reflected
in all other visible frames on the same part. Because different kinds of
parts have different requirements for passing changes to all frames,
OpenDoc provides the capability but does not specify the interface.
<p>
Frames (like icons) can be opened into windows. Such windows are
transitory views; that means they are not permanent representations of
components, while frames are persistent. When a frame is opened into a
window, the frame remains visible in its place. Because frames already
show the contents of parts, one might ask why one would open a frame into
a window. The answer is that some parts contain more content than can be
displayed in their frames. For example, a spreadsheet part may be quite
large, with only a portion of it appearing in a particular frame. Opening
it into a window allows the entire spreadsheet to be seen and edited and
allows the user to adjust which portion will appear in the frame.
<p>
The preferred representation of contained parts is a property of the
container. Some parts, such as folders, prefer to show embedded parts as
icons. Others, such as text documents, prefer to show them as frames.
When a part is copied from a Desktop folder to an OpenDoc document, the
copied part changes its representation from an icon to a frame. On the
other hand, when a part is copied from an OpenDoc document to a desktop
folder, the copied part changes its representation from a frame to an
icon. In either case, the contents or properties of the copied part do
not change, but once inside a container, a part's representations may be
specified on a part-by-part basis.
<p>
The containing part tracks all frames directly embedded within it. An
embedded part is logically contained in its containing part, just as its
frame is visually embedded in the containing part's frame. A containing
part treats its embedded frames as regular elements of its own content.
It can move, select, delete, or otherwise manipulate them, without regard
to what they display and what data kind they are. The embedded part
itself, however, takes care of drawing its contents and event handling
within an embedded frame.
<p>
The components must render themselves within their frame shape.
<p>
Those frames may have any shape, for example, square, uneven linear or any
other shape. The frames may even overlay each other. The actual
rendering is done by using facets. The facets represent the actual
drawing surface associated with a components frame. They simplify the
determination of the drawing location and the event dispatching. Facets
are only needed when a frame becomes visible.
<p>
<a name="FIG4610D46"><hr>
</a>
<p>
<p>
<a href="picture-11?mode=zoom"><img src="/bookmgr/pictures/EZ30OZ00.P11.GIF" alt="PICTURE 11"></a>
<p>
<p>
<hr>
Figure 11. OpenDoc Frames and Facets
<p>
<p>
<p>
If a part is dragged into another part, frame negotiations take place as
shown in <a href="#FIG4610D29">Figure 12</a>. The embedded component in this example is indicated by
the black solid pattern. The required space of the dragged part may
exceed the page limit or may be in conflict with the layout of the
containing part, so both have to agree on a common layout. The containing
component has the last decision. OpenDoc enables these negotiations by
providing a common interface.
<p>
<p>
<a name="FIG4610D29"><hr>
</a>
<p>
<p>
<a href="picture-12?mode=zoom"><img src="/bookmgr/pictures/EZ30OZ00.P12.GIF" alt="PICTURE 12"></a>
<p>
<p>
<hr>
Figure 12. OpenDoc Frame Negotiation
</pre>
</pre>
<hr>
<br><a href="2.3.2"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="2.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>