home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
opendc12.zip
/
SG244883.ZIP
/
2_3.2
< prev
next >
Wrap
Text File
|
2001-01-27
|
3KB
|
61 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">
<title>
2.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#2.3.2"><img src="/bookmgr/contents.gif" border=0 alt="[Contents]"></a>
<img src="/bookmgr/drevs.gif" border=0 alt="[Revisions]">
<a href="2.3.1"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="2.3.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="HDR4610DII"><H3> 2.3.2 Intrinsic and Embedded Part Contents</H3></a>
</banner>
<pre width="80">
<p>
Every part has some kind of intrinsic content, as defined by the part
developer. This is the content that's natural to the part, such as
characters and paragraphs in a text part, or lines, circles, rectangles,
and so on in a graphics part. In addition to its intrinsic content, a
part may contain embedded parts that have their own intrinsic content.
<p>
There's no requirement that a part be able to contain embedded parts,
although it's usually desirable. Some parts have content models in which
embedding doesn't make sense, for example, sound parts or parts that
display information, such as clocks or stock ticker tapes. As a
developer, you must decide whether it's desirable for parts you create to
allow other parts to be embedded. But, a key characteristic of OpenDoc is
that if a part can contain one kind of part, it can contain all kinds of
parts. This is in contrast to traditional documents, which can contain
only certain standard data types, such as text, PICT, and TIFF, in
addition to their intrinsic content. To a part, any parts embedded within
it are <I>black</I> <I>boxes</I>. A part does not need to know about the internal
structure or semantics of embedded parts.
<p>
<p>Subtopics:
<ul>
<li> <a href="2.3.2.1"> 2.3.2.1 Frames and Facets</a>
</pre>
</ul>
<hr>
<br><a href="2.3.1"><img src="/bookmgr/prev.gif" border=0 alt="[Prev Topic]"></a>
<a href="2.3.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>