This chapter includes:
The Addon Interfaces Library Reference is intended for users who want to use the library to create addons that dynamically add functionality to applications. You can use addons to add functionality to your application without requiring redeployment of the entire application.
The new Multimedia Library uses the Addon Interfaces Library to build its interfaces. For more information about the Multimedia Library, and to see examples of interfaces implemented with the Addon Interfaces Library, see the Multimedia Developer's Guide.
This table may help you find what you need in the Addon Interfaces Library Reference:
|When you want to:||Go to:|
|Read an overview of the Addon Interfaces Library, including a step-by-step example of how to write your own interface||Overview|
|See the list of basic API (structures and functions) that make up the Addon Interface Library, and a list of auxilliary interface-specific functions||Addon Interfaces Library Reference|
|See a list of existing interfaces that have been designed for use with the Addon Interfaces Library, which you can use in your applications||Appendix A: Existing Interfaces|
|Read about accessing data (resources) in an addon using the AOResourceAcces interface||Appendix B: Using Addon Resources|
|See the list of existing structures that have been designed for use with the Addon Interfaces Library, which you can use in your applications||Appendix C: Defined Structures|
Throughout this manual, we use certain typographical conventions to distinguish technical terms. In general, the conventions we use conform to those found in IEEE POSIX publications. The following table summarizes our conventions:
|Code examples||if( stream == NULL )|
|File and pathnames||/dev/null|
|Keyboard input||something you type|
|Programming data types||unsigned short|
|Programming literals||0xFF, "message string"|
We use an arrow (→) in directions for accessing menu items, like this:
You'll find the Other... menu item under.
We use notes, cautions, and warnings to highlight important messages:
|Notes point out something important or useful.|
|Cautions tell you about commands or procedures that may have unwanted or undesirable side effects.|
|Warnings tell you about commands or procedures that could be dangerous to your files, your hardware, or even yourself.|
In our documentation, we use a forward slash (/) as a delimiter in all pathnames, including those pointing to Windows files.
We also generally follow POSIX/UNIX filesystem conventions.
To obtain technical support for any QNX product, visit the Support area on our website (www.qnx.com). You'll find a wide range of support options, including community forums.
Copyright © 2004–2018, QNX Software Systems Limited, a subsidiary of BlackBerry Limited. All rights reserved.