Adobe FRAMEMAKER 10 User Manual page 262

facet_data
&
...
facet_name
=
& data_type
facet_data
&
...
=EndInset
>
A MIF ImportObEditor statement names the main editor for application-specific facets in the
graphic inset file.
A MIF
ImportObFileDI
information on device-independent pathnames, see the section
Internal graphic insets
An internal graphic inset is entirely contained within FrameMaker document file. Once the link is established, the
graphic inset data exists only in FrameMaker document.
Users can access the graphic only through FrameMaker. To edit an internal graphic inset, users must open
FrameMaker document, select the graphic inset, and choose the Graphic Inset command from the Special menu.
FrameMaker writes the graphic inset to a temporary file and instructs your application to edit it.
Your graphic
application
Internal graphic insets are best suited for environments in which portability of FrameMaker document across
different types of systems is most important.
When FrameMaker creates temporary files for internal graphic insets, the temporary files have the following format:
<MIFFile 8.00>
<ImportObject
inset_editor_name
<ImportObEditor
<ImportObFile `2.0 internal inset'>
= facet_name
data_type
&
& facet_data
...
= facet_name
data_type
&
& facet_data
...
=EndInset
>
Because the graphic inset is stored in FrameMaker document, the file does not have an
ImportObFileDI statement.
statement specifies the device-independent pathname for the graphic inset file. For more
>
"Device-independent pathnames" on page
FrameMaker document with internal
graphic inset
ADOBE FRAMEMAKER 10 257
MIF Reference
7.