Adobe Acrobat SDK
Understanding Plug-ins
Developing Plug-ins and Applications
Modifying the Acrobat or Adobe Reader user interface 33
Private data prefixes
When adding private data to keys defined in a Cos dictionary, the data must be added to the PDF file with
a key name that uses the following syntax:
Prefix_PrivDataName
. When adding additional keys that
are directly referenced from private keys, it is not necessary to use the developer prefix.
In the following example, the keys named
First
and
Second
cannot be referenced from any object in
the PDF file except the private key that uses an appropriate prefix, so there is no need to use a prefix for the
latter two keys.
/Prefix_PrivDataName << /First 2 /Second << /Third [ 2 3 ] >> >>
Please contact Acrobat Developer Support if you add private data to your plug-in that you believe is useful
to other plug-ins. Developer Support would like to know what types of private data plug-ins save in PDF
files so that similar data can be standardized with the same name and data format. In this way, developers
of different plug-ins using similar data can be assured that their plug-ins can exchange data. For more
information regarding private data in PDF files, see the
PDF Reference
.
Note:
For information about Cos dictionaries, such as the one shown in the previous example, see
“Working with Cos dictionaries” on page 186
.
Action prefixes
Actions must use the following syntax:
Prefix_ActionName
.
AVAppRegisterActionHandler(&BkmkHandler, NULL, "ADBE_HWAction", "HWAct");
Annotation prefixes
Annotation prefixes must use the following syntax:
Prefix_AnnotType
.
return(ASAtomFromString(“ADBE_MarkUpAnnot”);
HFT prefixes
When your plug-in exposes any HFTs of its own, it must use an HFT name that conforms to the following
syntax:
Prefix_HFTName
.
gDebuggWinHFTServer =
HFTServerNew("ADBE_DebugWin",provideDebugWinHFTCallback, NULL, NULL);
For information about HFTs, see
“Working with Host Function Tables” on page 164
.
Modifying the Acrobat or Adobe Reader user interface
This section describes typical operations that a plug-in can perform to modify the Acrobat or Adobe
Reader user interface. To modify the user interface, you must invoke methods that belong to the Acrobat
Viewer Layer. As a result, you cannot modify the Acrobat or Adobe user interface by using the PDF Library
API. For information, see
“Acrobat Viewer layer” on page 17
.
