28
4
Plug-ins
The Acrobat core and extended APIs enable you to write plug-ins that integrate with Adobe Reader. For
detailed information on the API architecture, methods, and usage, see
Developing Plug-ins and Applications
and the
Acrobat and PDF Library API Reference
.
Any plug-ins written for Adobe Reader must be Reader-enabled, which means that you will need to obtain
permission and licensing from Adobe Systems. When developing a Reader-enabled plug-in, follow the
steps described in
Developing Plug-ins and Applications
to make specific changes to your plug-in code in
order for Adobe Reader to recognize and load it. For information on what you can and cannot do with
Reader-enabled plug-ins, see the Reader Integration Key License Program.
A Reader-enabled plug-in is a dynamically linked extension to Adobe Reader created using C/C++ APIs,
and can be developed for any supported platform:
●
DLLs on Windows (using the extension
.api
)
●
Shared libraries (code fragments) on Mac OS X
●
Shared libraries on Linux or UNIX platforms
As you learned in
“Technologies available within the Acrobat SDK” on page 8
, additional usage rights may
be applied to a PDF document using LiveCycle Reader Extensions. For information on checking
permissions associated with a given PDF document, see
Developing Plug-ins and Applications
.
Note:
With LiveCycle Reader Extensions, it is not necessary to distribute any plug-ins or other special
software to implement the additional usage rights available within the PDF document.